The restructuring landed. The volume didn’t shrink. Four Alaska plants listed for sale, Saint Paul closed through 2025, 10 percent of Seattle HQ cut[4][7][10]. The same 1.2 million annual transactions[2] still move vessel to customer across a tighter network. Every exception now lands on the planners who remain.
Four Alaska plants listed for sale. Saint Paul closed through 2025. Ten percent of Seattle HQ cut[4][7][10]. Catch volume is unchanged. Every remaining planner now carries a heavier exception load with less buffer at each node.
A shipment enters at Demand Sensing, exits at Settlement, autonomously, in minutes. Then the next one enters. The loop runs 24/7.[9]
Every number below comes from deployed customer outcomes, not projections. Pick the shape closest to Trident's.
No seafood customer to name yet. Multimodal, cold-chain adjacent, and SAP-heavy deployments where the operating shape transfers. Named references at the booth.
One AI-native platform. Demand sensing, inventory, dispatch, execution, freight settlement, sustainability reporting. All on one intelligence layer that sits above the systems you already own.







We leave with a shared view of where the exception load is landing post-restructuring, and three scoped experiments against it. Three questions shape what we bring.
If you have already solved these, that is the conversation we most want to have. Bring one Alaska operations lead, one integration engineer, and one planner who owns exception resolution.