UHF Source-Tagging at 11M Tags/Year

Why source-tagging at the factory (not the DC)

Tagging in the retailer's DC (distribution centre) was the option this customer used during pilot. It worked but added a $0.04 / unit DC labour cost and a 4-day DC dwell time. Source-tagging — encoding at the apparel supplier's factory in Vietnam / Bangladesh / Indonesia — eliminated both costs and shifted the responsibility for chip presence to the goods receipt audit.

• DC tagging — $0.04 / unit DC labour + 4-day DC dwell. Convenient for pilot, not scalable to 11 M units / year.
• Source tagging at supplier factory — $0.00 incremental DC labour, 0-day DC dwell. Tag is part of the hang-tag artwork SKU.
• Trade-off — retailer needs an EPC encoding standard the suppliers can follow. Customer adopted GS1 SGTIN-96 with the retailer's GS1 prefix.
• Receipt audit — retailer's DC reads a 5% sample of every inbound carton through a portal reader to verify chip presence and EPC correctness.

Why Monza R6-P (and not UCODE 9 / Higgs 9)

Monza R6-P, UCODE 9 and Alien Higgs-9 are all viable for apparel source-tagging. The customer chose Monza R6-P for three reasons:

• Autotune — Monza R6-P automatically detunes the antenna based on the underlying substrate. Apparel substrate varies (jeans denim is wet-looking dielectric, lingerie is air-coupled, jackets have metal zipper interference). Autotune normalises read rate across these substrates without per-SKU antenna design.
• Read-rate consistency — the customer's existing reader fleet (Zebra FX9600 portals + MC9300 handhelds) was already tuned for Monza chips from a prior pilot. Switching chip family would have required re-tuning across 340 stores.
• GS1 compatibility — Monza R6-P supports the GS1 EPC Tag Data Standard 2.0 SGTIN-96 encoding natively, which is the customer's mandated standard.
• Cost — at the customer's annual volume the chip-cost delta vs UCODE 9 was less than $0.002 / unit, immaterial vs the Autotune benefit.

GS1 SGTIN-96 encoding at the supplier factory

Each tag carries a unique GS1 SGTIN-96 EPC = retailer's GS1 company prefix + item reference (SKU) + serial number. The retailer provides each supplier with a serial-number block, the supplier's encoder writes the EPC at the printing-and-attaching step, and a per-carton EPC manifest is uploaded to the retailer's WMS before the carton ships.

• EPC field — GS1 SGTIN-96 = 8-bit header (00110000) + 3-bit filter + 3-bit partition + 24-bit GS1 prefix + 20-bit item reference + 38-bit serial.
• Per-supplier serial-number block — retailer pre-allocates serial-number ranges to each supplier to guarantee uniqueness without supplier-to-supplier coordination.
• Carton manifest — supplier's encoder generates an EPCIS-compatible XML manifest per carton, uploaded to retailer's WMS before despatch.
• DC verification — retailer's DC reads each carton's EPCs at receipt and reconciles against the manifest. Mismatch triggers a chargeback to the supplier.

In-store handheld scans drive the inventory accuracy lift

• 98%Store inventory accuracy after RFID (vs 67% pre-RFID)
• -26%Size-level out-of-stock at full-price SKUs
• -22%Shrink (theft + admin error) YoY chain-level
• 11 MUnits tagged per year across 340 stores

Each store performs a full-floor RFID scan once every 7 days using a Zebra MC9300 handheld. A 100,000-unit store completes the scan in 35–45 minutes, vs the 8 hours a visual cycle count used to take. The inventory delta from the scan is reconciled into the WMS overnight and feeds the size-level replenishment recommendation. The 26% out-of-stock reduction is the operations team's primary KPI for the programme — replenishment recommendations only work if the underlying inventory data is trustworthy.

FAQ