Skip to content
Docs menu

Running a programme · For a brand's operations team

Generating a batch

A batch is a run of codes for one brand and one product. Generating it spends one credit per label (a Dual Code label, with its two codes, is one label), and everything that decides what the printed label does is frozen at that moment — because what is printed cannot be taken back.

Who generates. A partner generates batches for its brands. A brand generates its own when it runs its own account, or when its partner has switched self-serve on for it. Otherwise the brand's login has no product or batch pages at all, and the partner generates for it.

Three questions, in order #

  1. The batch — a name, a lot number and the quantity.
  2. The code — the programme and the kind of label inside it, which decide the line and the mode.
  3. The batch metadata — up to five per-run facts the buyer reads on the verdict page, such as an expiry date, a manufacturing date, an offer end date or a special price. A batch fact replaces the product's fact of the same name.

The five fact slots are the same in a spreadsheet upload, where the expiry date, the offer end date and the special price have columns of their own and take three of the slots, leaving two for facts you name.

The form states the cost before you click: one credit per label. If the balance cannot cover it, the button is disabled and the sentence says why. The server refuses the same overdraft atomically either way, so two batches generated at the same instant cannot overspend a balance.

The line and the mode #

The line is what a scan does. The mode is how many codes are on the label. Both belong to the batch, not the brand — a July run can be plain authenticity and the Diwali run can carry a reward.

  • informational

    Modes
    multi
    What a genuine scan does
    Shows the product and never claims. Repeat scans are expected.
  • authenticity

    Modes
    single, dual
    What a genuine scan does
    Verifies the unit; the first N verifications claim it.
  • rewards

    Modes
    dual
    What a genuine scan does
    The code the buyer had to reach carries a claim card.
  • warranty

    Modes
    single
    What a genuine scan does
    The buyer's scan registers the purchase.
  • certificate

    Modes
    single
    What a genuine scan does
    Shows a document's own fields at /c/<code>.

Only a rewards batch can carry a reward campaign; an authenticity batch cannot, single or dual. See running a rewards programme.

  • multi

    Codes per label
    1
    Behaviour
    Always shows genuine information; never claims.
  • single

    Codes per label
    1
    Behaviour
    The first N distinct verifications claim it (N defaults to 3).
  • dual

    Codes per label
    2
    Behaviour
    The visible shelf code checks freely; the hidden code claims the pair (N defaults to 1).

What is frozen, and why #

The line, the mode, the verification limit (scan_limit), the kind of second factor and the scratch-code recipe are written on the batch when it is generated and never change. A verification limit of 0 means no limit: every scan says GENUINE, which is how a certificate or a document meant to be shown to many people is printed.

If a setting is wrong, generate a new batch. Changing a frozen setting would change what labels already on a pallet mean.

Repeat orders #

A brand's products carry their photos, description and facts. A repeat batch for the same product is a quantity and a lot number, not a retyped form.

Last reviewed 19 Oct 2026 · Something wrong? connect@avrascan.com