Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: LabelRules

How to print extra labels for a customer

Use a starter rule to print more than one label for each unit on one customer's lines, then check and release it.

Review edition · 13 November 2026 · For Author

On this page

A customer may need two labels for every unit: one on the product and one on its carton. The starter rule Print extra labels for a customer adds one rule that sets how many labels print for each unit of that customer's lines. Other customers keep the quantity your existing rules give them.

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 extra labels for a customer. It is in Recommended and in Quantities; you can also type a word such as "extra" in Search starter rules and Help.
  3. Fill in the blanks in the card's sentence, "For customer …, print … labels for every unit.":
    • Customer code: the customer's code exactly as it arrives in your job data, for example HARGREAVES. It is matched exactly as typed, including capitals, so a code with a space before or after it is refused.
    • Labels for each unit: a whole number from 1 to 10. The card starts at 2.
  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 copies-hargreaves) 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 how many labels print. It matches when the job's customer code equals the code you entered. It takes the number of units from the line's quantity and prints your number of labels for each of them: with 2, a three-unit line gets six labels and a single unit still gets two.

It is given a priority one step above every other quantity rule in the release, so it wins wherever it matches. A run of more than 1,000 units, or of more than 10,000 labels in all, is held rather than cut short.

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 three-unit line for your customer gets your number of labels for each unit.
  • No match / default: another customer keeps one label for each unit.
  • Missing data: a line for your customer that is already held for missing data stays held and prints nothing.
  • Boundary: a single unit for your customer still gets your number of labels.
  • Unrelated: an export line for another customer is unchanged.

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.