Who it is for
Importers, exporters and freight forwarders. Four departments each hold their own version of the truth, and inside their own system every one of them is correct — all four correct, and they still don't add up. That is not an attitude problem, it is a structural one.
When something goes wrong across departments, most companies diagnose it as poor communication and respond with more meetings and more group chats. The real cause is usually not silence — it is that there is no single record everyone is reading.
How one order crosses the company
The quote and what was promised to the customer
The delivery date they promised never reached anyone's schedule — it lives in one email
Actual stock and the picking schedule
Knows this one ships, doesn't know why it is urgent
Space, declaration documents, tariff codes
One missing document usually shows up when clearance is already stuck
Invoices issued and receivables
The gap between quoted and actual cost surfaces at month-end close
None of the four departments did anything wrong. The break is not in the people — it is between four separately correct copies of the data. What the tower changes: customers, SKUs, suppliers and tariff codes exist once, and every module reads that same record; when one hand finishes, the next one's work appears on its own, carrying its context; and a stuck cell shows who it is waiting on, and for how long.
Eight business modules
One data contract, not eight systems bolted together. Here is what each module covers.
Quotes, space, shipments and declaration documents.
Receipts, issues, lot numbers and available quantity.
Receivables, payables, cost allocation and reconciliation.
People, permissions and hours.
Customers, SKUs, suppliers and tariff codes — one copy company-wide.
Cross-module queries and exports.
Assignment, approval and cross-department handoff.
Scan tasks, pending actions and the audit record.
External systems plug in
Storefronts, customs systems, external ERPs and office suites connect through integrations rather than through someone re-typing. Systems with no available integration go through the other two layers — assisted operation or document intake — described in full underthe three access layers.
It stops where it should stop
Amendments, releases and returns need a person to approve them, and both approvals and rejections leave a record. When things don't reconcile at month-end, you can find out who changed what, and when. The thing to fear in automation is not an error — it is an error you cannot trace to a stage.
The match runs four ways: the quote, the actual shipment, the declared value and the statement. When those four disagree, you know that week — not when accounting closes the month.
Current status
In development · validating with first customers. The first scenario is freight accounts receivable: overdue tracking, repeat chasing, duplicate entry, collection cycle and hours spent — all measurable. Go deep there first, then extend the reusable procedure sideways.
Which systems to connect, at which layer, to what depth is the first thing we work out during rollout — this page does not pretend everything is already plugged in.
A 30-day pilot
Pick one real business line and let us bring its data in. At month-end you write ten questions and grade it yourself — if it answers well, we talk about what comes next; if it doesn't, your data goes back untouched.