The shipment as one entity, not five records
Order, container, bill of lading, declaration and invoice resolved as one shipment. The question stops requiring the number that one particular system uses.
WMS, TMS, ERP, customs brokerage and the carrier’s portal each hold a piece of the same shipment. Strattum resolves cargo, route, documents and cost as one context and serves it to the AI your teams already use.
Order, container, bill of lading, declaration and invoice resolved as one shipment. The question stops requiring the number that one particular system uses.
Pickup, warehouse, route, arrival and clearance on one timeline. The delay surfaces tied to the event that caused it, not to the day somebody noticed.
Tariff code, Incoterm, licence, special regime and trade agreement read together, in the version in force on the filing date. The requirement surfaces before the channel, not after it.
Today each one runs through WMS, TMS, ERP and an email to the broker, and the answer usually arrives after the cost has already started.
Order, container, document and route event resolved as one shipment. The team stops assembling the status across four systems to answer a customer who asked one question.
Tariff code, Incoterm, regime and agreement resolved per item, with the duty each one produces. The calculation stops being redone by hand on every similar shipment.
What that destination requires, what previous shipments ran into, and what the terminal needs to receive. Written from the operations the company has already run.
Route events, storage deadlines and documentary requirements read together. The cost surfaces tied to the step that generated it, while there is still a window to act in.
Through entity resolution. The order in the ERP, the container in the TMS, the pallet in the WMS, the carrier’s bill of lading and the customs declaration all come to point at the same shipment, even with no shared key between them. The answer cites the source record behind each figure, so the system can be opened and checked rather than trusted as a summary.
Yes. Tariff codes, special regimes, agreements and regulations are versioned context, and the answer carries what was in force on the filing date, with what it replaced. On an operation where the same goods were classified two different ways in two years, that is the difference between repeating the correct call and repeating the mistake.
Both, and the difference is which systems come in. A shipper connects ERP, brokerage and the carrier portal; an operator also connects WMS and TMS, and usually runs for several clients, which makes per-client isolation a requirement rather than a detail. The permission filter is applied before ranking, so one client’s context does not enter an answer given to another.
No. Strattum is the layer between those systems and the AI. They remain the system of record. What changes is that cargo, route, documents and cost get resolved as one thing when someone asks.
A generic assistant answers from whatever it can search, and here the data is not missing, it is spread across five different keys. What is missing is not the model, it is the context: which container belongs to which order, which rule applied on the filing date, what that user is entitled to see.
Inside your cloud. The entire platform is deployed in your infrastructure: AWS, Azure, GCP, OCI or on-prem. Strattum has no runtime access to the data, and your records, credentials, keys and network access never leave it.
Strattum
