How to Design and Print Product Labels

Why ad-hoc label printing causes scanning and recall problems

Many small operations print labels from a word processor or a one-off design tool that has no link to the item record. The barcode is pasted in by hand, the weight is typed from memory, and the GTIN is whatever someone copied last quarter. When a label scans wrong at a retailer's dock — or doesn't scan at all — the pallet is rejected and the chargeback lands on you.

The problem compounds across product and carton labels. A product label needs a retail barcode and net weight; a shipping carton needs a GS1-128 with the GTIN-14, batch, and quantity. Maintaining two unrelated templates by hand means they drift, and nobody can prove which label version actually went out the door.

A label engine tied to your item and packaging data removes the retyping and keeps barcodes valid, while an audit trail records exactly what was printed and when.

Why this happens

• Labels are designed in tools with no connection to the item, spec, or batch record.
• Barcodes are pasted as images instead of generated from the correct value and symbology.
• Different label sizes (product vs carton vs shipping) are maintained separately and drift apart.
• There is no record of which template, copies, or values were printed for a given order.

Biznsbook addresses this with a template-driven label designer, generated Code 128 / EAN-13 / GS1-128 / QR barcodes, default templates per type, and an append-only print-job audit trail when the Packaging module is enabled for your tenant.

Step-by-step: Design and Print Product Labels

This workflow suits operations leads, warehouse staff, and quality owners who want consistent, scannable labels without retyping data.

1. Decide the label type and size. Choose Product, Carton, Shipping, or Custom and set the width, height, and margin in millimetres (for example a 50 × 30 mm product label or a 100 × 150 mm carton label).
2. Create a label template. Open Label Templates → Create in Biznsbook and add an ordered set of fields. Each field is text, a token, a barcode, or a horizontal rule, with its own font size, bold, and alignment.
3. Add tokens and barcodes. Drop in tokens such as item name, net or gross weight, country of origin, GTIN-14, batch number, and expiry. Add a barcode field and pick the symbology — Code 128 for item/batch, EAN-13 for retail, GS1-128 for case data, or QR.
4. Validate and save. Biznsbook validates the template — flagging unknown tokens, invalid barcode dimensions, and a non-positive label size — and re-shows the form with warnings if anything needs fixing before it serialises the fields.
5. Set the default per type. Use Set Default so one template becomes the company default for its type; the previous default for that type is cleared automatically.
6. Preview, then print. Use Preview to render the template with sample data, then print from a packaging specification, an item, or a confirmed cartonization result, choosing the number of copies.
7. Review Print History. Open Label Templates → Print History to confirm each print appended a job row with the template name, reference, copies, and success or failure status.

Screen-level navigation lives in the Help Center. This guide focuses on the labelling process; help articles cover click-by-click steps.

Common mistakes to avoid

• Mistake 1: Pasting a barcode image instead of generating it from the item value, so the symbology or check digit is wrong and the scan fails.
• Mistake 2: Leaving tokens such as net weight or GTIN-14 blank on the item or spec, so the label prints with empty fields.
• Mistake 3: Trying to edit a seeded system template instead of cloning it into a company template you can change.
• Mistake 4: Never setting a default per type, so staff hunt for the right template on every print.

Most label failures are repeat offenses. Tie each rejected scan back to a missing token or wrong symbology and fix the template once.

Best practices that hold up as you scale

• Use tokens, not typed values — let the item, spec, and batch data fill the label so it is always current.
• Keep one default template per type (Product, Carton, Shipping) so output is predictable.
• Preview with sample data before rolling a new template out to the floor.
• Reserve GS1-128 for case and carton labels where you need GTIN-14, batch, expiry, and quantity together.
• Review Print History after a busy shift to catch any failed prints before they ship.

Consistency beats cleverness: a plain template that always scans is worth more than an ornate one that occasionally fails QC at a retailer.

How Biznsbook supports this workflow

The label template designer stores an ordered list of fields (text, token, barcode, line) with per-field font, alignment, and sizing, and renders them to PDF at any label size. When a template has no fields — or none is configured — Biznsbook falls back to its built-in product label, so printing never stops.

Barcode generation uses ZXing.Net to produce Code 128, EAN-13 (with an auto-calculated GS1 check digit), GS1-128 (encoding GTIN-14, batch, expiry, and quantity application identifiers), and QR codes, rendered directly into the label.

Default templates and seeding let you pick one default per type per company; three system templates (Product 50 × 30 mm, Carton 100 × 150 mm, Shipping 100 × 150 mm) are seeded at startup and can be re-seeded by a site administrator. System templates are protected — they can be cloned or chosen as the default, but not edited or deactivated.

The print-job audit trail appends a row for every print — template name, reference type, copies, and success/failure — so you always have an after-the-fact record of what went out.

Manual / design-tool labels vs Biznsbook

Frequently asked questions

How this differs by industry