In FMCG specifically, we aren't dealing with bespoke units. We are dealing with high-velocity, low-margin SKUs where a single mispick—swapping a 500g pack for a 1kg variant or sending the wrong flavor in a multi-pack—triggers a cascade of failures.

When an order is flagged as "incorrect item" by the customer, the logistics cost doesn't just stay with the carrier. You pay for the outbound leg, the warehouse processing fee for the return, and the inbound handling. In high-volume plays, these "minor" errors can eat up to 12% of your net margin per unit. If your WMS (Warehouse Management System) isn’t enforcing strict SKU-specific weight checks at the packing station, you aren't managing a supply chain; you're managing a gamble.

I once worked with an apparel and personal care brand that scaled to 50k orders a day during a peak festive window. They were pulling "good enough" numbers—roughly 96% accuracy. They figured the other 4% was just "noise."

It wasn't noise. It was a systematic failure in their hub logic. Because they didn't implement unique SKU-level barcodes for different weights of the same product line, the packers were manually selecting items based on visual recognition. During the 3x volume spike, fatigue set in. They started shipping "Large" size sachets instead of "Trial" packs because the packaging looked identical to a tired worker at 2:00 AM. Within 72 hours, their seller rating tanked, and they were hit with a heavy penalty for high RTO rates. The cost of fixing those labels and re-shipping the correct items wiped out the entire month's marketing spend.

To move from "messy" to "mathematically sound," you need to strip the human element out of the picking decision. You don't do this with "better training." You do it with architectural constraints.

*1. Weight-Validation at Gate: Every outbound parcel must pass through a weight-verification scale integrated with your shipping API. If the expected weight (calculated by `Unit_Weight Quantity + Packaging_Weight`) deviates by more than 2% from the actual scale reading, the system must hard-block the label generation. No exceptions.

2. Batch & Expiry Logic: For FMCG, you cannot just track "Quantity." You must track "Batch ID" and "Expiry Date." The WMS should trigger a "FEFO" (First Expiry, First Out) logic. If a picker tries to scan a batch nearing its 90-day expiry window for an online order, the system must flag it for manual override.

3. Zone-Specific Slotting: You cannot have high-velocity SKUs sitting in "overflow" areas. High-velocity items must be placed in primary "golden zones" near the packing stations to reduce travel time and selection errors. If a picker has to walk 50 meters to find a shampoo bottle, they are more likely to grab the wrong one from a nearby bin.

4. Real-Time Sync Cycles: You need sub-minute syncs between your platform’s API (e.g., Shopify or Amazon) and your physical WMS. If an item is "reserved" in a physical bin but not updated, you risk selling the same unit twice—a logistical nightmare that leads to instant cancellation.

Stop viewing 99% accuracy as a "target." View it as the minimum requirement for keeping your warehouse lights on. If your system allows a human to make a choice about which SKU to pick based on visual similarity, you have already lost the margin war. Automate the validation, harden the data inputs, and stop letting "close enough" erode your bottom line.