The unified operating system for supply chains.
WMS, TMS, OMS, YMS, Customs, Control Tower, ESG and Finance on a single event-driven platform, documented with canonical entities, flows, enums, REST endpoints and KPIs.
Every module is a face of the same system. They share canonical entities, events and contracts, and each one is documented here for the people who will operate, integrate or audit it.
Ten fronts of a supply chain operating system
Each module lists its entities with their code names, plus operational flows, enums, REST endpoints and KPIs.
WMS: warehouse management
Receiving, put-away, wave picking, packing intelligence, cross-docking, slotting, labor management and warehouse tax compliance.
TMS: transportation management
Routing, freight spot auction, freight audit, CT-e and MDF-e, modal shift, digital POD and carrier risk score.
OMS: order management
Omnichannel, BOPIS, ship-from-store, exception engine, digital twin and the complete order state machine.
YMS: yard management
Dock scheduling, call-to-dock, gate kiosk, check-in and check-out, with dwell time and turn time under control.
Customs clearance
NCM/HS, Incoterms, BL, AWB, Single Window, denied party check, Tariff Intelligence and AI-assisted classification.
Control Tower and digital twin
Executive cockpit, exception engine, playbooks, network design, capacity planning, peak readiness and GenAI.
ESG and carbon ledger
CO2e, eco-routing, CBAM, offset automation, AI-Pack, Reverse Chain Economics and Digital Product Passport.
Finance and billing
Accrual engine, cost allocation, claims and chargebacks, profitability lens, settlement and billing engine.
Architecture and stack
Fastify, MongoDB and Angular, multi-tenant, event-driven, unified MDM, ABAC, Zero Trust and observability.
Complete glossary
Core entities, enums, statuses, roles, plans, international standards and code conventions, each term with its code name.
Not another WMS. A supply chain OS.
Five architecture choices that apply to every module, from the warehouse to finance.
Native multi-tenant
Each customer is an isolated tenant, with plans (FREE, STARTER, PRO, ENTERPRISE) and granular roles (SUPER_ADMIN, TENANT_OWNER, MANAGER, OPERATOR, VIEWER). Scale and governance without forks.
Event-driven by default
A central event ledger, with correlationId and causationId, captures every state transition and enables traceability, auditing, replay, analytics and event-based integration with ERPs and partners.
Unified MDM
Product, Party, Asset, Location and Document Master shared across WMS, TMS, OMS, YMS and Customs. No duplication and no semantic drift.
Open APIs, ABAC and Zero Trust
Kebab-case REST endpoints versioned under /api/v1/, attribute-based ABAC authorization and integration with corporate identity providers.
AI applied to execution
AI-assisted customs classification, intelligent slotting, carrier risk score, predictive ETA, GenAI for Control Tower playbooks and replenishment recommendations.
From standalone OPS to supply chain OS
A single workflow engine chains order, allocation, picking, loading, transit, customs clearance and delivery. Each step emits a canonical event to the same ledger.
- Omnichannel orderOMS · orders
- Allocation and pickingWMS · movements
- Scheduled dockYMS · dockSchedules
- LoadingYMS · yardVehicles
- MDM and event ledgerbusinessEvents
- Transit and CT-eTMS · shipments
- Customs clearanceCustoms · declarations
- Delivery and PODTMS · digital POD
- Control TowerExceptions and playbooks
- ESG and financeCarbon, cost and margin
Illustrative flow of an order across modules.
Why a supply chain operating system
The era of siloed systems
For three decades, the supply chain ran on a patchwork of independent systems: WMS in the warehouse, TMS in transportation, OMS for orders, YMS in the yard and Customs for foreign trade. Each had its own data model, enums, roles and release cycle, connected by point-to-point integrations through files, queues or fragile webhooks.
The result: duplicated data, semantic drift between teams, KPIs that never reconcile and an integration team that grows as fast as the business. NexLog OS starts from the opposite premise: these modules are faces of the same system and share canonical entities, events and contracts.
What changes with a unified operating system
When Warehouse (warehouses), Shipment (shipments), Order (orders), Dock Schedule (dockSchedules) and Customs Declaration (tradeDeclarations) live in the same MDM, three properties emerge.
Orchestration: a single workflow engine chains omnichannel order, allocation, picking, shipping, loading, transit, customs clearance and delivery, with no intermediate gateways.
Observability: the central event ledger (businessEvents) correlates events through correlationId and causationId and delivers end-to-end traceability, ready for auditing, replay and AI.
Analytics without ETL: executive and operational dashboards query the operational MongoDB itself with typed aggregations, without duplicating data into a secondary data warehouse for common questions.
Applied AI and the future of logistics execution
The next decade of the supply chain will be written by systems that combine deterministic transactional execution with layers of contextual AI. In NexLog OS this shows up as Tariff Intelligence in customs classification, intelligent slotting in the WMS, carrier risk score in the TMS, predictive ETA in Control Tower, GenAI to draft exception playbooks and continuous replenishment recommendations in the OMS.
All of these agents consume the same event core and the same MDM, with no parallel data lake to feed them. That is what keeps data, execution and intelligence moving together.
Shall we design your supply chain operating system?
Thirty minutes with a CCX engineer, at no cost, to map your operation's modules, flows and KPIs into a single roadmap.