Logistics & Supply Chain
Logistics Software Development — TMS, WMS, Freight Visibility & Trade Compliance
Logistics software is held together by EDI from 1992 and APIs from last week — and the integration layer is where most platforms quietly break. We build TMS, WMS, and visibility platforms that survive contact with real carriers and real customs filings.
What we hear from Logistics & Supply Chain teams
- Carrier integrations that mix AS2/X12 EDI with modern REST APIs — one bad spec change breaks everything downstream
- Real-time visibility dashboards that lag 4 hours because the ELD/telematics provider rate-limits
- TMS systems modelled around single-mode shipments — and your business is actually multi-modal
- Dock-scheduling chaos: warehouses run on whiteboards and phone calls
- Trade-compliance gaps that surface only when CBP / customs flags a shipment
- Last-mile platforms with 60% driver churn because the app is hostile to use
- Reconciliation between TMS / WMS / accounting that nobody trusts at quarter-end
Regulation & compliance we work with
C-TPAT (US trade security)
USMCA / FTA rules of origin (US-Mexico-Canada and bilateral)
EU customs (UCC / ICS2)
Dangerous-goods / hazmat regulations (IMDG, IATA DGR, 49 CFR)
FSMA 204 (US food traceability) where perishables flow
GDPR for driver/workforce data
DOT / FMCSA + EU mobility-package compliance for fleet operations
What we deliver
Transportation management systems (TMS): rating, routing, tendering, tracking, settlement
Warehouse management systems (WMS): receiving, putaway, pick/pack, ship, cycle counting
Freight-visibility platforms with carrier-integration layers (ELD, telematics, EDI 214 + APIs)
Trade-compliance + customs workflows (HS classification, screening, automated filings)
Driver / fleet mobile apps with offline-tolerant workflows and turn-by-turn navigation
Multi-modal orchestration: ocean → drayage → rail → truck → last-mile
Trade-finance + factoring platforms for freight payments
FAQ
- Do you do EDI, APIs, or both?
- Both. AS2 + X12 (204, 210, 214, 990) is still how most asset carriers transact, and pretending otherwise locks your platform out of half the market. We build an integration layer that abstracts the transport (EDI vs REST vs SOAP vs webhook) and presents a single domain model to the rest of the platform — so adding the next carrier is a translator, not a redesign.
- How do you handle real-time visibility when telematics providers rate-limit?
- Tiered polling, change-event subscriptions where the provider supports them, and a freshness model that's honest with the user — 'last known position 12 minutes ago' is better than a stale dot pretending to be live. We've worked with Project44, FourKites, Trimble, Geotab, and direct ELD integrations across past engagements.
- Can you build multi-modal TMS, or only single-mode?
- Multi-modal is where most TMS migrations go wrong, so it's the default in our work. A single shipment can move ocean → drayage → rail → truck → last-mile, and the platform has to track ownership, milestones, exceptions, and reconciliation across every leg. We model legs as first-class concepts, not as nested children of a parent shipment.
- Are you familiar with US customs / trade-compliance workflows?
- Yes — HS-code classification tooling, denied-party screening, antiboycott checks, USMCA rules-of-origin, and integration with brokers + automated filings (CBP ACE for US, ICS2 for EU). We don't act as a customs broker, but we build the workflow tooling the broker and the importer/exporter both use.