A table version should describe one deliberate, reviewed change to owned reference data. Begin with the intended table and saved version. Preserve row identities and typed values so the next person can understand which facts changed.
Check the table and your role
Owner OR Operator can preview and save ordinary custom or customer-product reference tables. The WooCommerce SKU mapping template requires Author instead. Reviewer or Supervisor alone does not acquire either editing permission. Check the selected template before handing work to another person.
Edit or paste from a checked source
Use the grid for individual values or Paste data, including the header row for a larger change. Select Tab-separated or Comma-separated CSV as appropriate. Choose Merge by row_id, retain other rows when unchanged rows should remain, or Replace all rows, review any removals when the new complete set is intentional.
Pasted data is applied against the saved version, not unsaved grid edits. Read the screen's instruction before switching between modes. Preserve exact text codes. Empty pasted fields in nullable columns become null; use the grid when empty text itself must be stored.
Inspect the proposed difference
Preview the change and read Review changes, counts and rows. Inspect additions, changed values and removals. Use all pages when the change is larger than the visible grid. A correct total row count does not prove the identities or values are right.
Enter Reason for this version, describing the source and purpose. Confirm I have checked the proposed rows and changes. Where rows are removed, also confirm that you reviewed those removals. Do not replace a table merely to hide an unexplained duplicate or missing row.
Save and verify
Choose Save new version and inspect the confirmed saved revision. An uncertain answer retains the original save request and can offer Retry the same save request. Use the retained request rather than constructing another change with the same intended effect.
Worked handover: preserve an exact customer assignment
This is an illustrative data handover, not a record of a live import or printed label. Sarah Hughes, acting as Owner at Brighouse works, creates a customer/product table. The template stores these columns as required text. Its row identity is row_id; its matching key is customer_code together with product_code. Assume the saved table contains exactly these two rows:
| row_id | customer_code | product_code | kit_sku | customer_sku |
|---|---|---|---|---|
| hp-001 | 00127 | P-104 | CONTROL_BOX | HP-00024 |
| hp-002 | 00128 | P-108 | CONTROL_BOX | HP-00048 |
The checked assignment changes customer_sku in hp-001 to HP-00025. Sam Ashworth has Operator authority for this ordinary table. He selects the exact saved table revision and pastes the header and the complete changed hp-001 row using Merge by row_id, retain other rows. The intended result is one changed row, no additions and no removals. hp-002 remains exactly as shown, including its row_id and leading zeros.
Sam reads Review changes and confirms that exact result. If he accidentally selects Replace all rows, review any removals with only hp-001 in the paste, the proposed removal of hp-002 is material. He returns to the intended merge and previews again. He does not accept the removal merely because the first row looks right. Pasting is based on the saved version, so he also checks that no unsaved grid edits have been discarded inadvertently.
He enters a reason identifying the checked assignment, confirms the proposed rows and changes, then chooses Save new version. He hands Sarah the table identity, confirmed new version, reason and expected surviving rows. An uncertain response is resolved using Retry the same save request where offered. It is not a reason to make a second independent edit. This ordinary save has no separate Reviewer approval step; the role and preview checks are its own controls.
For a later LabelRules export, Sarah or Sam selects this confirmed version and checks the receiving date window. The export projects row_id, customer code, product code and customer SKU into the receiving customer-product fields; kit_sku is not part of that projection. Their evidence names the saved source version and file. The person using LabelRules must still review and accept its own import. No receiving import, activation or print has occurred in this illustrative handover.