Supply Chain
Traceability that survives an actual recall
We build the layer that ties EDI messages, warehouse scans and supplier records into one lot-level history — so a recall, an audit or a customs query takes hours rather than a fortnight.
Talk to us about your projectWhere a supply chain loses the thread
The data almost always exists. It sits in an 856 nobody parsed, a scanned pallet label, a supplier's spreadsheet and two ERP instances that disagree about the same GTIN. The work is rarely collecting more data — it is reconciling what four parties already sent you into one history a person can read.
That is also why blockchain belongs here and not everywhere. When your 3PL, your co-packer and your retailer each keep a private version of the handoff, a signed timestamped event record settles the argument without one of them owning the database. Where a single organisation owns the data, we will tell you a Postgres table is enough.
Capabilities
What we build for supply chain teams
Most of this is added beside the systems you already run. Replacing a working WMS is rarely the fix, and it is never the cheap one.
End-to-end traceability
Commissioning, aggregation, shipping and receiving events keyed to GTIN and SSCC, so a pallet's history reads as one verifiable chain rather than four exports.
Recall and withdrawal tooling
Trace forward and back from a lot code in minutes, with the FSMA 204 key data elements already captured at each critical tracking event.
EDI and supplier onboarding
850, 856, 810 and 214 over AS2 or sFTP, plus the honest reality of the supplier who will only ever email a spreadsheet.
ERP, WMS and TMS integration
Connected by API, IDoc, EDI or database replication depending on your stack, so nobody retypes an ASN into a second system at midnight.
Demand and inventory forecasting
Models fitted on your lead-time variance and real order history, tuned to a service level you name instead of a generic accuracy score.
Cold chain and condition monitoring
Logger and IoT streams turned into excursion alerts against each product's own limits, with the evidence pack QA needs to release or reject the batch.
Customs and trade documentation
Commercial invoices, packing lists, certificates of origin and HS classification drafted from the shipment record, then routed to a person before anything is filed.
Smart-contract settlement
Payment or penalty released when a milestone is confirmed on-chain: a gate-out scan, a verified delivery, an OTIF miss nobody wants to relitigate by email.
Supplier portals and operator apps
Portals for ASN submission and quality certificates, plus warehouse and yard apps that keep working offline in a chilled store or a port terminal.
What you get
What you keep afterwards
Every engagement ends with things you can hand to an auditor, a retail customer, or the engineer who inherits this.
- LIVE SYSTEM
- The platform, on your data
- Deployed to your infrastructure or ours, with source, integration mappings and the deploy pipeline handed over. Your team can onboard a new supplier or EDI partner without booking time with us.
- TRACE RECORD
- Lot-level history you can export
- Every handoff, scan and condition reading tied to a GTIN, SSCC or lot code, exportable as an evidence pack for a retailer audit, a regulator, or an insurer disputing a claim.
- INTEGRATION MAP
- Every connection, written down
- Which system owns which field, how each EDI transaction and API call is mapped, and what happens when a supplier sends a malformed 856. This is the document your next hire will need.
- OPERATING NOTES
- What breaks first, and when
- Running costs at your volume, the failure modes we hit during the build, and the parts of the flow still handled by a person. Named plainly rather than quietly left out.
How we work
From one lane to a live system
Timelines below are typical for a first site and one product line. Adding sites goes faster. Adding suppliers is the part that always takes longer than anyone plans.
Mapping the flow
1–2 weeksWe follow one product from purchase order to goods receipt, listing every system, document and manual re-key on the way. The output is a written map, not a call.
Pilot on one lane
2–4 weeksOne SKU family, one supplier, one site, on your real records. This step regularly changes the scope and occasionally ends the project, which is far cheaper here than in month five.
Build and integrate
6–12 weeksThe traceability layer, the EDI and ERP connections, and the operator screens. Counts are reconciled against what your WMS actually holds rather than assumed correct.
Rollout and tune
OngoingSite by site, supplier by supplier. We watch which exception alerts get ignored and remove them, because an alert nobody acts on teaches people to close the tab.
Is this the right fit for you?
Worth reading before you get in touch — it saves both of us a call.
A good fit if…
- Several organisations touch the goods and each keeps separate records
- A recall or customer audit currently means phone calls and spreadsheets
- You run an ERP or WMS you fully intend to keep
- Someone can name the lot, batch or serial you trace by
Probably not, if…
- Only your organisation touches the records — Web & SaaS Platform Development fits
- Nothing is scanned or barcoded yet, so there is no event to record
- You need one connector between two systems — Integrations & Custom API Development
- You want a pilot to announce, not a lane genuinely cut over
Frequently Asked
Questions
Common questions about supply chain traceability software.
The core wins: end-to-end provenance (proof of where something came from), tamper-proof audit trails (nobody can retroactively change records), cross-party trust without a central intermediary, and automated settlement via smart contracts once goods reach a checkpoint. It's strongest when multiple organizations share data today but don't fully trust each other.
Demand forecasting, inventory optimization, route planning, anomaly detection (quality issues, theft, delays), document automation (bills of lading, customs paperwork), and conversational interfaces for internal teams to query inventory and shipment status. AI and blockchain complement each other — AI for prediction, blockchain for verified history.
Yes. We routinely integrate with SAP, Oracle NetSuite, Microsoft Dynamics, Odoo, Manhattan, and custom WMS systems. Integration approaches vary: direct API, EDI, sFTP, middleware (MuleSoft, Dell Boomi), or database replication. We pick per client stack.
Our blog content covers our experience across food safety, pharmaceutical supply chain, shipping and port operations, automobile parts, and manufacturing quality control — each with slightly different traceability, compliance, and stakeholder concerns.
Almost never. The usual pattern is an AI + blockchain layer added on top of your current ERP/WMS/TMS stack, connected via APIs and middleware. Your team keeps using the tools they know — the intelligence and verification happen behind the scenes.
Have a project in mind?
Fixed price after a paid discovery — no hourly billing. A real engineer reads every enquiry, and we reply within 24 hours.