One internal reference. One customer’s requirement.
The sample order contains the internal product code INT-00017. A saved mapping for that customer and product resolves the customer code AC-00017.
The Acme label uses that resolved code alongside purchase order PO-00981 and batch B-0925, on a 100 × 150 mm layout at 203 dpi. The order data is fictional; the label at the top of this page is LabelRules’ own preview of it.
- Works order: WO-12345
- Customer: Acme Example
- Internal product code: INT-00017
- Customer product code: AC-00017
- Quantity: 3 labels
Hold the label. Make the reason clear.
The Acme profile requires a customer product code. If the mapping cannot supply it, or the job has no approved customer layout, the label is blocked at the station and the reason is shown.
It does not silently substitute the internal code. That difference matters when a customer expects their reference on every item. The operator passes the job to the office instead of choosing a lookalike label.
Keep the decisions with the workflow.
Start with the customer’s label example and explain the conditions in plain English. Check the resulting labels and approve the rules. Future matching jobs automatically use the right layout, customer mapping and required-field checks.
- Identify the customer and product: the saved lookup uses customer and product identifiers. Names and spreadsheet row positions are not the matching key.
- Preserve the supplied code: product references are text. Meaningful leading zeros must survive the journey from source data to label.
- Inspect the actual output: review the selected layout, resolved values and barcode. A readable preview is one check; the physical label still needs checking on your printer.
How is a customer rule tested?
Each rule is checked against examples written from the customer’s requirement, not from whatever the rule happens to produce: a match, a non-match, missing data, a quantity boundary and an unrelated workflow.
Inspect every case before publication
Before publication, the label proof of every allowed case is inspected, and each case that must be refused is checked to stop.
Common questions
Can we add any customer layout ourselves?
Yes. An author starts a template draft from an existing template, saves each revision and checks its proof, and a reviewer publishes the release to a qualified PrintStation station. Customer rules are written in plain English and checked against worked examples before review. Layouts are 100 × 150 mm with text and Code 128 barcodes, so bring other sizes and barcode types into the first conversation.
What label format is supported?
The production profile is 100 × 150 mm with text and Code 128. Bring any other sizes, barcode types or customer approval requirements into the initial conversation.
Can these customer rules use SAP data?
Yes, through a paid integration that SmartFACT scopes with you and builds through data.smartfact.ai. The SAP data then uses the same customer lookups, layout rules and required-field checks. Once the source fields are mapped, routine label-rule changes stay in SmartFACT.
What should we provide for an assessment?
A representative label or artwork, an anonymised order export, the corresponding customer product code, and an example that should be held rather than printed. Include the printer and label stock you intend to use.
Related pages
Start free at one station and pay when you grow. While SmartFACT is in early access, we set your first workflow up with you.
