Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: LabelRules

How to print a customer's own product code

Use a starter rule to print a customer's own product code in place of your part number, then check and release it.

Review edition · 13 November 2026 · For Author

On this page

A customer who orders by its own product codes expects to see them on the label. The starter rule Print a customer's own product code adds one rule that prints the customer's code from your job data in place of your own part number, for one customer.

Use the starter rule

You need the Author role. The rule is added to a draft: production keeps using its active release until a Reviewer publishes a new one.

  1. Open Rules. The page opens on Starter rules.
  2. Find Print a customer's own product code. It is in Recommended and in Label content; you can also type a word such as "product code" in Search starter rules and Help.
  3. Fill in the blanks in the card's sentence, "For customer …, print their own product code in place of ours.":
    • Customer code: the customer's code exactly as it arrives in your job data, for example ELLAND. It is matched exactly as typed, including capitals, so a code with a space before or after it is refused.
  4. Choose Use this rule. The button waits until every blank has a value, and a value the card cannot accept is refused on the card with what the blank accepts.

LabelRules opens an ordinary rule draft, named with the sentence you completed. Its page says Began from a starter rule, names the rule that was added (for example product-code-elland) and names the rule of yours the draft is anchored on, which is unchanged. No model is asked and nothing is approved.

What the rule does

The rule belongs to the decision what the label says. It matches when the job's customer code equals the code you entered, and it takes the product code your layouts print from the line's customer product code, for example ETS-07711. It is given a priority one step above every other rule that sets that code, so it wins wherever it matches.

A line for that customer with no customer product code is held at the station with the reason shown. LabelRules never puts your own part number in its place. To hold such a line with your own message, add Hold a label when the customer's product code is missing as well.

The codes themselves come from your job data or your saved data mapping. The rule only chooses which code prints.

Check the examples

Open Review the examples for this rule. The starter rule prepares five examples for the values you chose, one in each category, and the page says so under Examples prepared by the starter rule. They are not saved until you save them.

  • Positive: a line for your customer prints the customer's own product code.
  • No match / default: another customer's line prints the code its own rules choose.
  • Missing data: a line for your customer with no customer product code is held, and your own part number does not print in its place.
  • Boundary: a single-unit line for your customer prints their code, not yours.
  • Unrelated: an export line for another customer keeps your own part number.

Check each example before you save it:

  • Example input holds the values the example runs with. Change any that do not suit your data.
  • Independently expected result is what you expect to happen. The starter rule fills in the part its own rule decides. The rest is LabelRules' ordinary synthetic example, so correct anything your own rules decide differently.
  • Expected matched rule identities, in execution order lists every rule you expect to match. The starter rule states only its own rule. Add the others from the list of available rules, in order.

Tick the review box, write a note saying where the expected results come from and choose Save reviewed examples. Then choose Verify saved examples and inspect the proofs and refusals. A failed check tells you which expectation and which result disagree: decide which of the two is wrong before changing either.

Release it

When the saved examples pass, freeze the draft with Freeze rule candidate and hand the candidate to a Reviewer. Examples and releases describes the review and publication. Where the site requires a second approver, a rule from a starter rule needs one like any other.

If the card is refused

  • This starter rule changed. LabelRules has a newer version of the starter rule than the page you have open. Reload the page and fill the card in again.
  • The active release changed. A release was published while the page was open. Reload the page: the cards are built for the release in use.
  • Remove the spaces around the customer code. The code is matched exactly as typed.
  • A site holds up to 100 rule drafts and a ruleset up to 50 rules. At either limit, finish or publish existing work first.