No thought-leadership theatre. These are write-ups of problems we have actually hit, measured and fixed — written for people who run lines and compliance programmes.
Most "scan to verify" implementations can be defeated with a phone camera and a ₹15,000 label printer. Here is the difference between a QR code that points at a website and one that actually proves something — and what to ask a vendor before you sign.
Consent, purpose limitation and the grey area of approximate location data. A practical walkthrough of the decisions we made, and the ones we deliberately avoided making for our customers.
Read moreSlow nozzle degradation does not stop a line — it just erodes readability until rejection rates spike a week later. Here is the monitoring threshold we settled on after four plants.
Read moreAlmost every brand we work with discovers its leakage pattern is narrower than expected — a handful of routes and two or three pin codes. What scan data reveals in the first 60 days.
Read moreConflict resolution, idempotency and why we gave up on last-write-wins. The architecture behind dispatch verification that survives a dropped connection mid-pallet.
Read moreWhat inspectors actually ask for, mapped to the data your serialization system already holds. A template for the record export we ship to food customers.
Read moreBulk scanning, code sharing, retailer-side abuse and recycled cartons. Each needs a different control — and one of them cannot be solved by software alone.
Read moreSplitting a carton at a depot breaks the parent-child chain unless you designed for it. How to handle re-pack without losing traceability.
Read moreThe questions we wish customers asked us first, and the answers that should worry you. Includes the ones we don't score well on yet.
Read moreA short monthly email with one problem we solved and the numbers behind it. No product announcements.
