GenFrontier homeScope a project
Menu
Filed under
Deliver toWarehouse, receiving and shipping leads, and IT teams that look after devices

Barcode scanning, RFID and GS1 labeling

Scan workflows designed step by step, labels your trading partners can read, and data captured at the dock in the form your systems and partners expect.

Scope a project
services / barcode-rfid-labeling
A tuning fork stands beside a small cardboard box while halftone sound waves ripple out from it toward a red tag tied to the box

A scan is the moment a system learns something. If the label is missing, unreadable or wrong, every report downstream inherits the mistake, and the person at the dock types the number in by hand. We design the scans, the labels and the device setup together, around GS1 identifiers, so the data captured on the floor is the data your systems and trading partners expect.

Scanning workflows

We specify each scan as a step: what is scanned, in what order, what the screen shows next, and what happens on a wrong or failed scan. A few that appear in most warehouses:

  • Receiving. Scan the pallet’s SSCC, and the expected contents from the supplier’s ship notice appear. Confirm or record a difference.
  • Put-away. Scan the pallet, then the location label. A location check digit stops a driver confirming the wrong bin.
  • Picking. Scan the location, then the item, then confirm the quantity.
  • Loading. Scan each carton or pallet to the trailer, so the shipment record matches what left the dock.

The exception paths matter as much as the happy path: no label, a damaged label, an item the system does not know, a pallet that belongs to another order. Each gets a defined screen and a defined owner. A rule we apply everywhere: if a barcode exists, scan it rather than type it.

GS1 identifiers and labels

GS1 identifiers give each thing on a label a number your partners already understand.

Identifier What it identifies Where it appears
GTIN (Global Trade Item Number) A trade item at a given packaging level Product and case barcodes, the item master
SSCC (Serial Shipping Container Code) A logistic unit such as a pallet or carton Pallet and carton labels, the X12 856 Ship Notice/Manifest
GLN (Global Location Number) A location or a party Ship-from and ship-to on documents, site and dock IDs

Batch or lot numbers, serial numbers and expiry dates travel alongside these identifiers as GS1 Application Identifiers. We map each label field to the record it comes from, so the label, the ship notice and the inventory record all say the same thing. The numbers are assigned by your company under its GS1 Company Prefix. We design around them; we do not issue them.

2D barcodes and Sunrise 2027

GS1 US describes Sunrise 2027 as “a global transition from 1D UPC barcodes to 2D barcodes, like QR codes”, intended to help retailers “ensure their point-of-sale (POS) systems can read and process these next-generation data-packed codes.” For brands, GS1 US advises that they “ensure any existing QR codes are updated with GS1 Digital Link standards and include your Global Trade Item Number (GTIN).”

GS1 Digital Link is the standard way to encode identifiers such as GTINs, GLNs and SSCCs, along with batch numbers, serial numbers and expiry dates, so that one code can be read offline and also connected to online information. GS1 notes that healthcare uses GS1 DataMatrix for 2D barcodes rather than Digital Link.

For a warehouse or distributor, readiness is mostly a data and device question:

  • Can your scanners read 2D symbols, and does your software parse the Application Identifiers inside them?
  • Does your item master have fields for lot, expiry and serial where the code will carry them?
  • Can your label templates print a 2D code next to the linear barcode, at a size your partners can scan?
  • Have you tested real labels on real devices before a partner asks?

If your partners exchange event data, the same scans can be recorded as EPCIS events. GS1’s EPCIS and CBV 2.0 standard adds “JSON / JSON-LD syntax” and a “REST API for capture and query of event data.”

RFID: where it pays and where it does not

Our judgement, not a study. RFID tends to earn its cost where many items must be read without line of sight, where the same tagged asset comes back again and again (returnable containers, totes, tools), or where a customer requires it. It tends not to pay where barcode scanning already works and the real problem is process discipline, where tags would cost a large share of a low item value, or where metal and liquids make reads unreliable. Our advice is to pilot in one zone, measure read rates against a barcode count of the same items, and decide from that.

Devices and printers

We write the device specification from the workflows: handhelds, ring scanners or fixed scanners per station; scan range for high racking; cold-room and glove use; battery life across a full shift. For printers we specify thermal transfer where labels must last and direct thermal where they are short-lived, the label stock, and where printers sit so a label is printed where it is applied. Wi-Fi coverage at dock doors and in the far aisles is checked before go-live, not after. Because GenFrontier has no vendor partnerships, the specification states requirements first and models second.

Testing labels with trading partners

Large customers often publish label and ship notice requirements in a routing guide or supplier manual, and may charge back for labels that fail. We print sample labels from production templates, scan them on several devices, and send them with test 856s to each partner that asks for samples. The test log records what was sent, when and what the partner said.

Example (fictional). A supplier rebuilds a damaged pallet of item EX-20118 after its label is printed. The new pallet gets a fresh label, but the ship notice still lists the old SSCC, so the customer’s receiving scan fails. The fix is a written rule in the workflow: rebuilding a pallet voids its SSCC, prints a new label and updates the ship notice line before the trailer closes.

What you receive

  • A scan workflow specification for each process in scope.
  • Label templates with a field-by-field data map.
  • A device and printer specification, and a Wi-Fi check of scanning areas.
  • A partner label test log.
  • Source code and configuration, delivered at handover. Ownership and licensing terms are set out in each statement of work.

Scope your project.

Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.