Loading and manifest checks
Every consignment scanned at the dock, so a short load is caught before the truck leaves.
Supply chain
Supply chain software that can answer within 24 hours
Dispatch, loading checks and proof of delivery on one record. Traceability rules now ask for exactly that chain, which is why it is where we start.
24Hours to produce traceability records on request
2028FSMA 204 compliance date, 20 July
68Dispatcher calls a day before the build
40+Developers on staff
What this is
The chain is only as good as its weakest handover
Most supply chain pain sits at a handover: the dock, the truck, the drop. Each one needs the same few facts captured the same way, or the record breaks exactly where an auditor looks.
Capture once, at the event
Lot code, time, place and person recorded when the thing happens. Nobody rebuilds it a week later from three systems.
Offline is the default
Loading bays and cold stores kill mobile data. Every record is written to the device first and queued.
Services
What we build for supply chain teams
Proof of delivery
Receiver, reference, photo and signature captured before a drop can be closed.
Lot and event records
The handovers of a chain captured as events, each tied to the lot it concerns.
Route sequencing
Stops reordered with the saving stated in kilometres.
Telematics ingest
Position and engine data over MQTT, with a broker in front so the console stays responsive.
WMS and ERP integration
The record has to reach the system of record, not stay in the driver app.
Rules
What the US traceability rule asks for
FSMA section 204 is the clearest current example of a regulator asking for the whole chain.
Compliance date, 20 July 2028The FDA moved the date from January 2026, said the requirements do not change, and a later appropriations act also directs it not to enforce before then.
Critical tracking eventsRecords are kept at events such as harvesting, cooling, packing, shipping and receiving, each with its own key data elements, lot codes among them.
The 24-hour ruleRecords have to reach the FDA within 24 hours of a request, so the work is search and export, and filing comes second.
Who is in scopeBusinesses that make, process, pack or hold foods on the Food Traceability List, and foods that contain them as an ingredient.
Case study
The dispatch layer, built and running
Logistics
TruckFleet Labs
A short-haul operator ran 42 trucks on a spreadsheet with nine tabs and a group chat holding 61 people. We built a dispatch console and an iOS driver app where every record is written to the phone first, with proof of delivery and a loading gate at the dock.
68Dispatcher calls a day before the build
Who we build for
The teams who call us
Food distributors and processors
Where a lot code has to follow a pallet from the dock to the drop.
Third-party logistics providers
Operators answering to customers who want evidence, not reassurance.
Retailers with their own fleets
Distribution that runs beside the shop floor and has to feed it.
Cold chain and temperature-sensitive operators
Where a missing reading is a failed shipment.
Related reading: logistics software, IoT fleet management and offline-first apps.
FAQs
What buyers ask first
Does FSMA 204 apply to us?
If you make, process, pack or hold foods on the FDA Food Traceability List, or foods that contain them, yes. Check the list before assuming either way.
Can you tie lot records to our WMS or ERP?
Usually yes. The integration is normally the part that decides whether the data gets used, so we scope it first.
What happens when a driver has no signal?
The record is written to the phone and queued. The driver can watch the queue drain, so nothing depends on coverage at the moment of the drop.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Send us one handover
Thirty minutes with the engineers on the dock, the truck and the drop, and which facts you need at each one.