Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: SmartFACT Data

Prepare a LabelRules customer-product import

Export supported exact customer-product codes from one saved table version with its evidence.

Review edition · 25 October 2026 · For Owner, Operator, Viewer

On this page

Use Prepare a LabelRules import on a table with the supported customer-product schema. The export creates a file from a saved version and explicit settings. It does not update LabelRules, print a label or prove that another application accepted the file.

Check the saved source

Open the intended reference table and confirm the customer and product assignments. Review exact codes, leading zeros and customer SKU values. The table needs a first saved version before export is available. Unsaved grid edits are not the export source.

Choose Saved version deliberately. If a recent correction should be included, save and confirm that version first. A table with a similar display name does not establish that it has the supported schema or the correct assignments.

Set and inspect the export

Read the settings offered, including any effective dates. Choose Prepare LabelRules CSV. The prepared result records the saved source version and those settings. Inspect the confirmation before downloading.

The browser checks the prepared file against its evidence. If it cannot verify the file, follow the displayed instruction to use a secure HTTPS connection and prepare the import again. Do not bypass the warning by presenting an unverified file as confirmed output.

Download LabelRules CSV and retain its companion evidence where your process requires traceability. Preserve exact text values when another system opens the file. A spreadsheet can reinterpret numeric-looking codes, so compare the imported identities rather than trusting their visible formatting.

Complete the receiving workflow

Use LabelRules' own supported import and review path. Data's file preparation is evidence of what was exported, not permission to activate a receiving configuration or print production labels.

If the receiving system reports an error, retain the saved table version, export settings and precise refused row or code. Correct the source through a reviewed new version, then prepare a fresh export as appropriate. Do not edit a retained generated file silently and continue to cite the old evidence.