CMRs, customs documents, packing lists, carrier invoices: qualified, extracted, and integrated into your TMS or ERP with a human review queue whenever in doubt.
A file per shipment, an EDI that only covers some partners, margins that leave no room for data entry errors, and TMS systems that stop where your specifics begin.
CMRs, DAUs, packing lists, delivery notes, carrier invoices: every shipment generates its own file, and every file ends up re-entered into the TMS or ERP. It’s the most predictable and least addressed administrative cost.
Major accounts are connected; others send a PDF by email. EDI handles 30 to 40% of the flow depending on the company; the rest arrives as attachments and is re-entered manually.
A data entry mistake on weight, an Incoterm, or a reference can cost more than the file’s margin. A delay in carrier invoicing ties up already strained cash flow.
Chartering, transit, dispute management, demurrage rebilling: off-the-shelf solutions cover the common ground and stop where your specific workflows begin.
From incoming documents to the dispute dashboard, every intervention equips your existing operations—never silently integrating what the AI isn’t certain about.
Emails and attachments as input, document type qualification, structured extraction via OCR and Mistral, integration into your ERP or TMS. Anything uncertain goes to a human review queue.
Automationsn8n, APIs, EDI, webhooks: synchronisation between TMS, WMS, ERP, and partner portals. We extend your existing EDI to cover the flows it doesn’t, rather than replacing it.
n8n agencyShipment tracking, operational dashboards, delay and dispute alerts, rebilling: a tool tailored to your workflows, complementing your TMS.
Business applicationIncoterms as you apply them, internal customs procedures, rate grids, client-specific terms: queryable in natural language, with systematic source citation from your internal documents.
AI assistants connected to your dataWhat happens when AI is uncertain, who submits the declaration, what becomes of the chain during peak season? The answers that determine whether automation holds up in real-world operations.
An unreadable field, an unknown reference, an inconsistent amount: the document goes to a human review queue rather than entering the system. No silent integration—that’s what makes automation acceptable for low-margin flows.
We extract and prepare customs data. Submitting the declaration, assessing tariff classification and origin, and liaising with authorities remain the responsibility of your declarant or your RDE. We do not intervene in declarations or your AEO status.
Original document preserved, extraction timestamped, review decision assigned, integration logged. In the event of a carrier dispute or audit, the full document path can be reconstructed and exported.
Mistral by default, open models self-hosted when volumes or confidentiality require it. Your commercial data and that of your clients never leave France.
The architecture is sized for peak demand, not the average: queue-based processing, horizontal scaling, scalable self-hosting. A flow tripling in November must not break the chain.
Code delivered, extraction rules documented, connectors described, data exportable. Switching TMS or provider does not mean losing your configuration work.
The flagship case is an import-export player: the document qualification process mirrors that of a CMR or carrier invoice. The second demonstrates workflow resilience at scale.
Freight forwarder, carrier, importer, or supply chain management: we focus on a single flow—CMRs or carrier invoices, for example—and measure the time saved per document before expanding. The scope is intentionally narrow to ensure clear ROI.
TMS, WMS, and ERP connectors, an existing EDI enhanced rather than replaced, and a self-hosted, scalable architecture to handle seasonal spikes.
The questions that come up during scoping with an operations manager, a transit director, or a supply chain executive.