OverviewWMSTMSOMSYMSCustomsControl TowerESGFinanceArchitectureGlossary
Module · OMS

Order Management System omnichannel orchestrator

NexLog OS OMS unifies omnichannel orders, distributed inventory, BOPIS, ship-from-store, exception engine, digital twin and what-if simulation. Canonical state machine with native NF-e, GNRE, DIFAL and ICMS — integrated with WMS, TMS and Control Tower.

Perfect Order ≥ 95%

Omnichannel SLA

BOPIS · SFS

Flexible fulfillment

NF-e · GNRE

BR fiscal

State machine

9 states

State machine · orders

From draft to completed

Nine canonical states — including CANCELLED at any point — with events emitted to the businessEvents ledger.

DRAFT

Draft

APPROVED

Approved

PICKING

In picking (WMS)

PACKED

Packed

DISPATCHED

Dispatched

IN_TRANSIT

In transit (TMS)

DELIVERED

Delivered

COMPLETED

Completed

CANCELLEDvalid transition from any state prior to DISPATCHED.
Main entities

The canonical model of OMS

Order

orders

Canonical transactional entity of OMS. Accepts multiple source channels (DTC, marketplace, B2B, POS) and propagates state machine.

Return

returns

Complete reverse logistics process. Connects WMS (re-entry) and TMS (pickup) with fiscal and financial audit.

Returnable Asset

returnableAssets

Pallets, racks, containers and reusable packaging — tracked by SSCC/GTIN in ESG and Reverse Chain Economics flow.

Operational flows

Omnichannel no compromise

Omnichannel

DTC, marketplaces, B2B, POS and social commerce in the same order pipeline.

BOPIS

Buy Online Pick-up In Store: store as pickup point with dedicated SLA.

Ship-from-store

Store inventory as distributed fulfillment center; intelligent allocation routing.

Exception engine

Rules and playbooks to handle ruptures, delays, divergences and claims.

Digital twin

Digital replica of the order for what-if simulation before allocation.

Reverse logistics

Returns with reverse network and returnable assets tracked end-to-end.

Native BR fiscal

NF-e, GNRE, DIFAL and ICMS

NF-e

Automatic issuance on DISPATCHED transition, attached to shipment.

GNRE

State tax collection guide for interstate operations.

DIFAL

Tax rate differential calculated by destination state.

ICMS

Automatic fiscal accrual — with integration to tax systems.

REST APIs

Endpoints OMS

GET/api/v1/orders
POST/api/v1/orders
POST/api/v1/orders/:id/transitions
GET/api/v1/returns
POST/api/v1/returns
GET/api/v1/returnable-assets

KPIs that OMS delivers

Perfect Order Rate

Complete order, on time, damage-free, with correct invoice. Enterprise goal: ≥ 95%.

Order cycle time

Average order time from created to delivered — with breakdown by channel and region.

Return rate

% of returns — analyzed by reason, SKU and channel; impacts Reverse Chain Economics.

OMS as the brain of the supply chain operating system

Order as canonical entity

In NexLog OS, Order (`orders`) is the entity that travels most between modules. It originates in any channel (DTC, marketplace, B2B, POS, social commerce), passes through approval (APPROVED), is allocated in WMS (PICKING/PACKED), delivered by TMS (DISPATCHED/IN_TRANSIT/DELIVERED) and finally completed (COMPLETED). The state machine is immutable and each transition generates a canonical event (`businessEvents`) with `correlationId`/`causationId`, enabling end-to-end traceability, audit, replay and predictive model training.

Real omnichannel, not fragile integration

BOPIS, ship-from-store, drop-ship and same-day cease to be special cases and become just allocation policies on the same model. Store inventory, regional fulfillment center and 3PL coexist in the same distributed inventory. Return (`returns`) and Returnable Asset (`returnableAssets`) treat reverse logistics as first-class citizen — essential for returnable packaging and circular economy.

Digital twin and exception engine

Before allocation, order digital twin allows what-if simulation: cost of allocating to fulfillment center A vs. store B, CO2e impact, expected delivery window, rupture risk. Exception engine applies playbooks to real deviations (pending payment, rupture, dock delay, fiscal divergence) and scales automatically to Control Tower when human needs to decide. All without fragile integration — because WMS, TMS, Customs, ESG and Finance share the same MDM.

Frequently asked questions

Common questions

Yes. The same orders model covers DTC, marketplaces, B2B, POS and social commerce, with allocation policies specific to each channel.
Talk to specialists

Is your OMS still a patchwork of integrations?

Centralize order, distributed inventory, returns, NF-e and KPIs in a single model — true omnichannel.

Talk to NexLog specialistBack to NexLog OS hub
OMS — Order Management System | NexLog OS Academy | CCX Company