Module
GS1 Labels & Scan
One barcode per pallet, one per carton, in the standard every customer's warehouse already reads.
Watch demo
The customer's warehouse scans the pallet once. Will the scan resolve to your record?
The running product, filmed as it works — every number on screen was computed live while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.
What it produces
- SSCC per pallet, allocated under your GS1 Company Prefix and never reused
- GS1 Logistics Labels and carton labels as SVG for any printer and ZPL for Zebra printers
- GS1-128 and GS1 DataMatrix carrying GTIN, batch, expiry, count and net weight as Application Identifiers
- Pallets labelled straight from a kept stuffing plan, contents from the material master
- A scan endpoint for handhelds that resolves an SSCC to everything on the pallet, and records every scan
A worked example
SSCC (00) 3 0614141 000000001 3 — pallet 4 of SO-2041
(02)14006381333938 (37)64 (10)B2609 (17)280930 — 64 cartons of SUB-1452, batch B2609
GTIN-14 derived from the unit GTIN with indicator 1; the label says so
scan ]C100306141410000000013 → pallet 4, 64 cartons, 768 PCS, status LABELLED
no Company Prefix on file → nothing is allocated, and the page names the GS1 India step
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
A pallet that arrives at a customer's warehouse is scanned once. If that one scan resolves to every carton, batch and count on it, the receiving clerk moves on; if it does not, somebody counts by hand and your invoice waits. GS1 is the standard every such warehouse already reads. This allocates the identifiers under the prefix you hold, prints the labels the way the standard lays them out, and answers a scan from your own master data.
Opened by the logistics manager, the supply chain manager and the planner — what each of them sees first.
Said before you ask
What we don’t do.
SIAARU decides from your records and nothing else. It carries no copy of the world’s data, states no number your systems have not, and acts in nobody’s name. Where your data does not support an answer, it says so by name rather than producing a confident one — which is the whole reason a decision taken on it holds up later.
The identifier arithmetic, the Application Identifier encoder and parser, the label composers and the scan resolver are built and tested, with GS1’s own published check-digit examples among the tests. Three things are true by design. SIAARU allocates nothing without the GS1 Company Prefix you obtained from GS1 India, because a number issued to you is not a number anyone else can mint. GTINs come from your material master, and a material without one gets the step that fixes it rather than a label under an invented number. And the ZPL is written to Zebra’s ZPL II guide; the first physical print is a step you take on your own printer.
Where this sits
One of 36 modules, on one engine.
GS1 Labels & Scan reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 35 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.