Routes, returns and tracking Answer 5 of 6 in this tray
Barcode vs. RFID Tracking for Reusable Bakery Trays
Updated November 13, 2026
Barcode and RFID are two ways of capturing a tray’s identity at a handoff. A barcode is read optically, so a reader needs a clear view of an intact, readable mark; capture can be handheld or automated, and whether several visible marks can be read in one pass depends on the imaging setup and how the trays are arranged. RFID reads a tag by radio, so in suitable conditions it can capture a tag without a direct view and can read several tags in one pass, but the result depends on the tag type, where it sits on the tray, the readers and antennas, nearby metal and other materials, and how the system is set up. Neither one fixes tray loss by itself; both only produce records, and the records are as good as the process that uses them.
Identify What You Are Tracking
Decide this before comparing technologies:
- Asset type or individual tray? A code can identify “tray model X owned by company Y,” or it can identify “tray number 004517.” Type-level codes support counts by category. Individual codes support custody history for each tray.
- Physical ID or inventory count? A marked tray is a physical ID. A count of trays in a ledger is an inventory figure. Tracking connects the two through scan events.
GS1, the organization that maintains the GS1 identification standards, says the Global Returnable Asset Identifier (GRAI) “is used to identify returnable assets such as re-usable transport equipment like trays, crates, pallets or beer kegs that are used and then returned to be used again” (GS1 support: main use of GRAI). GS1 Australia adds that it “can identify these returnable assets by type and if needed also individually for tracking and sorting purposes” (GS1 Australia: GRAI).
How Barcode Capture Works
- Marking. A label, an in-mold label, or a direct mark on the tray carries the code. The method must survive washing, abrasion, and stacking.
- Readability. The mark has to stay clean, undamaged, and visible from where the scanner will be.
- Scan event. A person or fixed scanner reads the code at a defined point.
- Data field. The scan records the code plus where and when, and the scanning device or person if your process tracks that.
- Point of transfer. Scans are tied to handoffs (dispatch, delivery, pickup, receipt) so that each tray’s custody changes are recorded.
Stacked or nested trays can hide each other’s marks, so marking position and the scanning step have to be designed together.
How RFID Capture Works
- Passive versus active tags. Wikipedia’s RFID entry explains that “Passive tags are powered by energy from the RFID reader’s interrogating radio waves.” Active tags carry their own power source and are a different cost and maintenance category.
- Reader infrastructure. Fixed readers at dock doors or portals, or handheld readers, plus antennas and software.
- Tag placement. Where the tag sits on or in the tray affects how well it reads and whether it survives washing and impacts.
- Read zones. A portal reads tags passing through a defined space. Tags outside the zone, or shielded, may be missed; tags near the zone may be read when they should not be.
- Interference. The same Wikipedia entry notes that UHF tags “are difficult to read when placed within a few millimetres of a metal surface.” Metal dollies, racks, and truck walls are part of a bakery’s reading environment, and so are water and wet product.
GS1 Identifiers for Returnables
GS1 lists separate identification keys for different purposes, including GTIN (Global Trade Item Number), SSCC (Serial Shipping Container Code), and GRAI (Global Returnable Asset Identifier) (GS1 support: identification keys in transport and logistics).
- A GTIN identifies a trade item: the loaf of bread or the case of buns that is sold.
- A GRAI identifies the reusable asset: the tray that carries the bread and comes back.
Putting a product GTIN on a tray, or treating a tray code as if it identified the product in it, mixes two different records. The tray’s identity follows the tray for its whole service life; the product’s identity leaves with the product.
Operational Comparison
| Factor | Barcode | RFID |
|---|---|---|
| Reading distance | Short; scanner aimed at the mark | Longer in suitable conditions; depends on tag, reader, and environment |
| Line of sight | Needed | Not always needed; shielding and metal still matter |
| Manual labor at handoff | Handheld scanning presents trays one by one; fixed cameras can capture visible marks as trays pass | Can read many tags in one pass where the setup supports it; read rates are not guaranteed |
| Mark or tag durability | Label or mark must survive washing and abrasion | Tag and its mounting must survive washing and impact |
| Exception handling | Unreadable marks found during scanning | Missed reads may go unnoticed without reconciliation checks |
| Cost categories | Marking, scanners, software, labor per scan | Tags, readers, antennas, installation, software, tuning |
| Data integration | Scan events into the asset ledger | Read events into the asset ledger, plus filtering of stray reads |
No dollar figures or read rates appear here because they depend on the equipment, the trays, and the site, and a vendor figure from another setting does not transfer.
Simple Event Schema
Whichever technology you pick, each capture should produce a record like this:
Read event (illustrative only):
| Field | Example |
|---|---|
| <!–INLINECODE0–> | E-000481 |
| <!–INLINECODE1–> / <!–INLINECODE2–> | <!–INLINECODE3–> / GRAI with serial, or <!–INLINECODE4–> / GRAI without serial |
| <!–INLINECODE5–> | 1 for a serial ID; the counted quantity for a type-level read |
| <!–INLINECODE6–> | Store 112 back door |
| <!–INLINECODE7–> | <!–INLINECODE8–> (ISO 8601 with offset) |
| <!–INLINECODE9–> | Portal 2 or handheld 14 |
| <!–INLINECODE10–> | The handoff or pass the read belongs to |
| <!–INLINECODE11–> | <!–INLINECODE12–> / <!–INLINECODE13–> / <!–INLINECODE14–> / <!–INLINECODE15–> |
| <!–INLINECODE16–> | <!–INLINECODE17–> / <!–INLINECODE18–> / <!–INLINECODE19–> / <!–INLINECODE20–> |
Custody transfer (illustrative only):
| Field | Example |
|---|---|
| <!–INLINECODE21–> | Pickup document 2291 |
| <!–INLINECODE22–> / <!–INLINECODE23–> | Store 112 receiver / Driver 7 |
| <!–INLINECODE24–> and IDs or type | Serial list, or tray type |
| <!–INLINECODE25–> | 120 |
| <!–INLINECODE26–> | <!–INLINECODE27–> |
| <!–INLINECODE28–> | Signature, PIN, or other agreed method |
| <!–INLINECODE29–> | <!–INLINECODE30–> / <!–INLINECODE31–> / <!–INLINECODE32–> |
A read event shows that an ID was seen at a place and time; a custody transfer shows that the receiving party accepted the trays. A reader seeing a tag is not the other party’s acceptance. If you use a type-level GRAI without a serial, the records track quantities of a type, not individual trays. Where scan events enter a real return process, they sit at the count and handoff steps described in how to organize empty tray returns from retail stores.
Pilot and Verification
Test a technology on a bounded lane before committing:
- Pick one lane: a dock door, one store’s back door, or one route.
- Use a known tray count that is checked by hand.
- Measure read accuracy, by ID type:
- Individually serialized trays: list the serial IDs expected in each defined handoff and compare them with the IDs captured in that handoff. Merge repeated reads of one ID only within the same handoff and time window; a tray seen again in a later delivery is a new event.
- Type-level codes only: many trays carry the same code, so merging repeated reads of that code cannot show how many trays were read. Use a validated item-counting process, or temporary individual identifiers for the pilot, if you need tray-level read accuracy.
4. Count false positives (IDs read that were not in the handoff) and misses (trays present but not read) separately, along with the difference from the hand count.
- Run reconciliation: do the pilot’s events match the manual counts at each handoff?
- Include worst-case conditions: wet trays, full stacks, metal dollies, nested empties.
- Record exceptions and the time staff spent handling them.
The pilot’s own numbers, not a brochure figure, are the evidence for a decision. If discrepancies point to causes other than capture, such as skipped pickups or ownership disputes, see why reusable trays get lost between bakeries and retailers.
Which Method Merits a Pilot
Pilot barcode first when trays can be presented one at a time at each handoff and the main gap is missing records; pilot RFID when handoffs move many trays at once and you can control read zones around metal and water. In both cases, the pilot has to produce read accuracy, false positives, misses, and reconciliation results from your own lane before the method is chosen.
Add a note on this tray answer
You must be logged in to post a comment.