Blue oil painting: a store associate packs an online order with a barcode scanner at the back counter
  1. Home
  2. NexLog OS
  3. Academy
  4. OMS

Order Management System for the omnichannel order.

Distributed inventory, BOPIS, ship-from-store, exception engine and digital twin on a canonical state machine, with native NF-e, GNRE, DIFAL and ICMS.

One order, several fulfillment routes

The order starts in any channel, is approved and only then allocated, after a simulation in the digital twin. DC, store or in-store pickup are policies on the same model.

  1. Orderorders · DRAFT
  2. ApprovalAPPROVED
  3. AllocationDigital twin and what-if
  4. DC or 3PLWMS · PICKING, PACKED
  5. Ship-from-storeStore as DC
  6. BOPISIn-store pickup
  7. Shipping · TMSDISPATCHED, IN_TRANSIT
  8. DeliveryDELIVERED, COMPLETED

Illustrative flow. Uppercase codes are order states.

Overview

The NexLog OS OMS unifies the omnichannel order, distributed inventory, BOPIS, ship-from-store, exception engine, digital twin and what-if simulation.

The order state machine is canonical, has native NF-e, GNRE, DIFAL and ICMS and integrates with WMS, TMS and Control Tower through the same MDM.

Order state machine

Nine canonical states of the Order (orders), including CANCELLED, with every transition emitted to the businessEvents ledger.

CodeStateContext
DRAFTDraftOrder created in any channel: DTC, marketplace, B2B, POS or social commerce.
APPROVEDApprovedApproval in the OMS, before allocation.
PICKINGPickingAllocated and being picked in the WMS.
PACKEDPackedPacking completed in the WMS.
DISPATCHEDDispatchedDeparture through the TMS; the NF-e is issued at this transition.
IN_TRANSITIn transitOn the road, tracked by the TMS.
DELIVEREDDeliveredDelivery confirmed.
COMPLETEDCompletedOrder cycle closed.
CANCELLEDCancelledValid transition from any state prior to DISPATCHED.

The state machine is immutable: each transition, made through POST /api/v1/orders/:id/transitions, generates a canonical event with correlationId and causationId.

Core entities

The canonical OMS model, shared with WMS, TMS and ESG.

EntityCodeDescription
OrderordersCanonical transactional entity of the OMS. Accepts multiple source channels (DTC, marketplace, B2B, POS) and propagates the state machine.
ReturnreturnsComplete reverse logistics process. Connects the WMS (re-entry) and the TMS (pickup), with tax and financial auditing.
Returnable assetreturnableAssetsPallets, racks, containers and reusable packaging, tracked by SSCC/GTIN in the ESG and Reverse Chain Economics flow.

Operational flows

Six flows on the same order model.

Omnichannel

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

BOPIS

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

Ship-from-store

Store inventory as a distributed DC, with intelligent allocation routing.

Exception engine

Rules and playbooks to handle stockouts, delays, discrepancies and claims.

Digital twin

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

Reverse logistics

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

Native Brazilian tax compliance

Documents and taxes issued and calculated automatically as state transitions occur.

AcronymDescription
NF-eAutomatic issuance on the DISPATCHED transition, attached to the shipment.
GNREState tax payment form for interstate operations.
DIFALTax rate differential calculated by the destination state.
ICMSAutomatic tax calculation, integrated with tax systems.

REST endpoints

Endpoints versioned under /api/v1/.

EndpointMethods
/api/v1/ordersGET, POST
/api/v1/orders/:id/transitionsPOST
/api/v1/returnsGET, POST
/api/v1/returnable-assetsGET

Convention: kebab-case endpoints, versioned under /api/v1/, and camelCase collections.

KPIs the OMS delivers

Perfect Order Rate

Order complete, on time, undamaged and with a correct invoice.

Order cycle time

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

Return rate

Percentage of returns, analyzed by reason, SKU and channel; it affects Reverse Chain Economics.

The OMS as the brain of the supply chain operating system

The order as a canonical entity

In NexLog OS, the Order (orders) is the entity that travels most between modules. It starts in any channel (DTC, marketplace, B2B, POS, social commerce), goes through approval (APPROVED), is allocated in the WMS (PICKING, PACKED), delivered by the TMS (DISPATCHED, IN_TRANSIT, DELIVERED) and completed (COMPLETED).

Each transition generates a canonical event (businessEvents) with correlationId and causationId, which enables end-to-end traceability, auditing, replay and training of predictive models.

Real omnichannel, not fragile integration

BOPIS, ship-from-store, drop-ship and same-day stop being special cases and become allocation policies on the same model. Store inventory, regional DC and 3PL coexist in the same distributed inventory.

Return (returns) and Returnable Asset (returnableAssets) treat reverse logistics as a first-class citizen, essential for returnable packaging and the circular economy.

Digital twin and exception engine

Before allocation, the order's digital twin lets you simulate scenarios: the cost of allocating to a DC or a store, the CO2e impact, the expected delivery window and the stockout risk.

The exception engine applies playbooks to real deviations, such as pending payment, stockout, dock delay and tax discrepancy, and escalates to Control Tower when a person needs to decide. WMS, TMS, Customs, ESG and Finance share the same MDM, with no fragile integration in between.

Frequently asked questions

Does the OMS handle marketplaces and B2B in the same pipeline?

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

How do BOPIS and ship-from-store work?

They are allocation policies on the distributed inventory. The store becomes a DC for the OMS, and a lightweight WMS runs as an app.

What about reverse logistics?

Returns (returns) are first-class citizens, with reverse logistics, WMS re-entry and tax auditing.

Does it support returnable assets?

Yes. returnableAssets (pallets, racks, containers and packaging) are tracked by SSCC/GTIN and connected to ESG.

NF-e, GNRE, DIFAL, ICMS?

All native, issued and calculated automatically as state transitions occur.

Can I integrate with VTEX, Shopify, Salesforce Commerce?

Yes. CCX has ready-made connectors for the main Brazilian and international commerce stacks.

Is your OMS still a patchwork of integrations?

Thirty minutes with a CCX engineer, at no cost, to centralize order, distributed inventory, returns, NF-e and KPIs in a single model.