Use this reference for the Reference tables screen, pasted data and the bounded LabelRules export. Owner creates ordinary tables; Owner OR Operator maintains their rows. The specific WooCommerce SKU template instead requires Author. The visible table template and current saved version determine which rules apply. See Roles and actions before transferring the task.
Define an ordinary table deliberately
| Field or control | What to enter | Checks and limits | If it is refused |
|---|---|---|---|
| Table name | A meaningful name for the owned data. | Required, no more than 200 characters. An all-space name is invalid. | Use a specific name; inspect the recorded table before repeating an unconfirmed creation. |
| Column name | Lower-case letters, digits and underscores, beginning with a letter. | From 1 to 64 characters; names must be unique. A table has 1 to 20 columns. The row_id column is retained as required text. | Correct the schema before creation; do not rename codes in the data merely to imitate column syntax. |
| Type | Choose Text, Whole number or True or false. | Decimal values and exact codes belong in Text. Text preserves leading zeros; Whole number does not. | Check the field's meaning rather than converting an identifier into a number. |
| Allow null | Permit an absent value only where intended. | Row identity and matching-key columns must not be nullable. Empty text and null are different. | Choose the intended source meaning before creation. |
| Matching key | Select the columns that together identify one business record. | At least one unique key column is required; key values and row_id must be present and non-empty. Distinct row_ids do not excuse duplicate business keys. | Resolve the actual duplicate or schema choice before saving. |
The ordinary row grid does not redefine its schema. Controlled definition changes follow their separate reviewed workflow. See Create a typed table.
Enter and preview exact rows
| Field or control | What to enter | Checks and limits | If it is refused |
|---|---|---|---|
| Text cell | Preserve the exact code or value. | Maximum 4,096 UTF-8 bytes per cell, including text that looks numeric. The grid's character allowance can be reached later than the byte limit. | Check the complete value and source; do not silently cut off a code or leading zeros. |
| Whole number cell or pasted whole number | An integer without decimals or leading zeros, apart from zero itself. | Pasted values use ordinary signed integer notation, not exponent notation, plus signs or separators, and must be from -9007199254740991 to 9007199254740991 inclusive. | Use Text for a large identifier or decimal; do not round or reinterpret it. |
| True or false cell | Use its selection in the grid; in pasted data use exactly true or false. | Yes, No, 1 and 0 are not substitutes in a pasted boolean column. | Correct the source representation for this declared type. |
| Paste data, including the header row | Paste every table column exactly once in the header, followed by complete rows. | Choose Tab-separated or Comma-separated CSV. No extra, missing or repeated headers. Empty pasted fields become null in nullable columns; use the grid for intentional empty text. | Check delimiter, header spelling, quoting and row widths before previewing again. |
| How to apply pasted rows | Choose Merge by row_id, retain other rows, or Replace all rows, review any removals. | The paste is applied to the saved version. Replace can remove rows not included; merge preserves other rows. | Inspect removals and any unsaved grid work before continuing. |
| Proposed table size | Keep the complete retained table within its template limit. | Ordinary tables: at most 500 rows and 512 KiB table data. WooCommerce SKU tables: at most 10,000 rows and 2 MiB table data. Both retain the 20-column and cell-size ceilings. | Use an appropriately bounded table and inspect the reported size/row problem; do not omit required rows to disguise a complete replacement. |
| Reason for this version | Explain the checked change for the next reader. | Between 10 and 2,000 characters; the minimum is checked after trimming surrounding whitespace. | Give the source and purpose, then check the proposed additions, changes and removals. |
| I have checked the proposed rows and changes | Confirm the actual preview; explicitly confirm removals when present. | Saving rechecks the exact preview and saved revision. Changing the proposal requires another preview. | Review again after a stale or changed-preview refusal. An uncertain save uses the retained original save request. |
The SKU template additionally keeps shop_sku and item_code exact, from 1 to 80 characters when present. Its base_quantity_per_unit is positive decimal text with at most six fractional digits when item_code is set; both item_code and conversion must be null together when unmapped. Saving this table does not activate its shop mapping. Follow Edit and save a table and Shop mappings.
Check export dates and receiving identities
For Prepare LabelRules CSV, select a saved version and supply LabelRules effective from. LabelRules effective to (optional) can be blank, or must be a valid later calendar date. Dates are YYYY-MM-DD and apply to that receiving import only. The supported export needs non-blank text row_id, customer_code, product_code and customer_sku with unique row identities and customer/product pairs. Maximum lengths are 128, 128, 128 and 64 characters respectively. Unsupported schema, duplicate pairs, oversize rows or file limits need correction before export. Use LabelRules export; receiving review and acceptance remain separate.