FMCG distributors: your retailers will expect 2D-barcode despatch data by 2027

the despatch CSV is about to become part of the product

There is a transition working its way through retail right now that almost no FMCG distributor is watching, because on paper it has nothing to do with distributors. It's called GS1 Sunrise 2027, it concerns barcodes at retail point of sale, and the entire conversation around it is happening between brands, GS1, and retailers. Distributors aren't mentioned in the documentation. Which is exactly why the distributors who see what it implies a year early will take business from the ones who find out when a retailer's purchase manager starts bouncing their despatch files.

Here's the short version of the thing itself. Sunrise 2027 is a GS1-led, industry-wide transition with one target: by the end of 2027, retail point-of-sale systems should be capable of scanning 2D barcodes — QR codes carrying GS1 Digital Link, or GS1 DataMatrix — alongside the familiar 1D stripes. Be careful with the words, because the trade press isn't: it is a capability milestone, not a mandate. No law compels anyone. 1D barcodes remain perfectly valid during and after the transition; nobody's existing stock becomes unscannable. What's happening is coordination — brands are already printing 2D codes next to the old EAN (walk a modern trade aisle and you'll find dual-printed packs today), POS vendors are shipping 2D-capable scanners in the normal refresh cycle, and GS1 is herding everyone toward the same end-of-2027 readiness date. We've covered what Sunrise 2027 means at the retail shelf in detail; this post is about what it means one step up the chain, where you sit.

The difference between the old code and the new one is the whole story. A 1D EAN says one thing: which product this is. A GS1 2D code says which product — AI (01), the GTIN — and then keeps talking: batch or lot number in AI (10), expiry date in AI (17), a serial number in AI (21) if the brand wants one. When a retailer's billing counter scans 2D, the retailer doesn't just ring up a sale. They learn, automatically, which batch left the shelf and what its expiry was. Batch and expiry stop being warehouse trivia and become point-of-sale facts.

Now follow that capability upstream, because retail systems are greedy in a predictable direction.

retailers who can scan batch will start expecting batch

A retailer whose POS reads batch and expiry at the till will, very quickly, want batch and expiry at goods-in too — otherwise their inward stock and outward sales don't reconcile at the same level of detail, and half the value of the new scanners evaporates. Their software vendors know this, which is why modern retail and kirana-tech systems are already building batch-aware purchase entry. And a retailer doing batch-aware purchase entry has exactly two ways to populate it: type batch and expiry off every pack in every carton you deliver, or import it from a file you send.

Nobody is going to type it. The boy receiving stock at a busy kirana between customers is not transcribing forty batch numbers off your delivery, and the modern-trade back office would rather reject the delivery paperwork than key it. Which means the expectation lands on the despatch file. The retailer's system will want a despatch CSV — or an e-invoice attachment, or whatever the channel uses — with item code, quantity, batch number, and expiry date per line, importable without a phone call.

This is the shift worth internalising: the despatch data file is becoming part of the product. Not a courtesy, not an extra — part of what you deliver, judged the way fill rates and delivery timing are judged. The distributor whose file loads cleanly into the retailer's system in one click is offering a better product than the distributor whose file needs an hour of correction, at identical price and identical stock. And unlike price, this is a dimension where a mid-sized distributor can beat a bigger rival outright, because it's a matter of process, not capital.

The cynical reading is that none of this bites until your retailers actually upgrade, and plenty of them will be running their current billing setup well past 2027. True. But the expectation won't arrive uniformly — it will arrive retailer by retailer, starting with modern trade, chain pharmacies, and the better-organised supermarkets, which is to say, starting with your largest and least replaceable accounts. By the time the long tail catches up, the standard will already have been set by the accounts you couldn't afford to fumble.

the same data is your defence in the claims war

If the retailer-expectation argument feels speculative, here's the one that's already costing you money this quarter: expired-stock returns.

Every distributor knows the ritual. Stock comes back from the market near or past expiry, a claim goes up the chain, and the company's claims team goes looking for reasons to reject it. This batch wasn't billed to you. This was billed eighteen months ago, why is it surfacing now. This came from another distributor's territory. The dispute always turns on one question — which batches did you actually despatch, to whom, and when — and the distributor usually loses, because the despatch records say "Parle-G 800g x 12" with no batch, while the company's primary-billing records are batch-stamped to the carton. They have data; you have an argument. We've written about why claim rejections on expiry returns keep going against the distributor, and the pattern in nearly every rejected claim is the same: the distributor couldn't prove batch-level despatch.

Batch-and-expiry-stamped despatch data closes that gap from both sides. When a retailer returns expired stock, you can verify in seconds that the batch is one you actually supplied them — and refuse the ones that aren't, which is its own quiet saving, because territory-hopping returns are a real leak. And when you consolidate returns upward, your claim arrives with the chain intact: received this batch on this date, despatched it to these outlets on these dates, returned in these quantities. A claim with that spine is hard to reject on the usual grounds. The same records that make your files load cleanly in the retailer's system make your claims survive scrutiny at the company. One discipline, two payoffs.

And there's a third, quieter one: once despatches are batch-stamped, you finally know where your short-dated stock went. Secondary-sales visibility — knowing what's actually sitting in your retailers' shops rather than what left your godown — gets dramatically more useful when it's batch-aware, because you can push rotation on the specific outlets holding the specific batches that will otherwise come back to you as a claim in eight months.

what to actually do, starting now

None of this requires waiting for 2027, new hardware, or anyone's permission. It requires three unglamorous process decisions.

Get batch and expiry into the despatch file. Your billing software already holds batch data somewhere — it came in on the company's primary invoice. The work is making sure goods-in actually captures it (scanned off the carton's GS1 code where the brand prints one, imported from the company's invoice file where they send one, keyed as a last resort) and that your despatch output carries it per line. If your current software can't put a batch and expiry column on a despatch CSV, that is a harder constraint than it sounds, and worth escalating with the vendor now rather than during a retailer onboarding.

Worth saying plainly: the goods-in half of this is where most distributors will discover their actual gap. Despatch can only carry batch data that receiving captured, and receiving at a typical distributorship is built for speed — cartons counted against the invoice, stock racked, entry done from the paper copy that evening, batch column left blank or filled with whatever was legible. Fixing despatch without fixing receiving just moves the blank columns downstream. The good news is that the company's side of the chain is already structured: primary invoices increasingly arrive as files with batch and expiry per line, and dual-printed cartons increasingly carry scannable GS1 codes. The data is reaching your godown gate. The only question is whether it gets into your system or stays on the paper.

Standardise your SKU codes and stop freelancing. The silent killer of file-based commerce is the item master. The same biscuit is "PARLE G 800G", "Parle-G 800gm", and item code 4471 in three different systems, and every mismatch is a line the retailer's software can't import. Settle on the GTIN — the number under the barcode — as the canonical identifier wherever you can, keep your internal codes mapped to it, and stop letting despatch entries get created with improvised names. The retailer order arriving as a WhatsApp voice note is not going away soon; the answer is that your side of the ledger is clean enough that translating their chaos is a lookup, not a judgement call.

Treat data quality as a service level. Measure it the way you measure fill rate: what percentage of despatch lines this month carried a valid batch and expiry? Which retailers' imports needed manual fixing, and why? Put a name against the number. Distributors run on thin margins and win on service; this is simply the newest axis of service, and right now the bar is so low that "our files load without errors" is a genuine differentiator. It will not stay a differentiator. By 2028 it will be table stakes, and the distributors who built the habit in 2026 will be the ones who set the standard their competitors get measured against.

where ShelfLifePro fits

The receiving side of this is exactly what ShelfLifePro's supplier-file receiving was built for. The company's despatch CSV — whatever its column order, header names, or code scheme — goes in, and batch-and-expiry-stamped stock comes out. The system learns each supplier's file format and SKU code mappings the first time, so the second file from the same company maps itself; your item master stays clean without anyone maintaining a spreadsheet of cross-references. Where cartons carry GS1 2D codes, barcode scanning captures (01) GTIN, (10) batch, and (17) expiry straight off the pack at goods-in — the same codes your retailers' new POS scanners will be reading at the other end of the chain.

From batch-stamped receiving, the rest follows: despatch files that carry batch and expiry per line and load cleanly in the retailer's system, expiry visibility across the godown before stock goes short-dated, and a despatch-level batch trail that turns return claims from arguments into evidence. Sunrise 2027 is going to make batch and expiry the common language of the FMCG chain. The distributors worth more to their retailers — and harder to reject at claims time — will be the ones already speaking it.

ShelfLifePro ingests your suppliers' despatch CSVs with batch and expiry, learns SKU code mappings automatically, and gives you batch-stamped stock from godown to despatch. Be the distributor whose files just work.