One order hub for every sales channel

Orders Hub gives every selling application one canonical order lifecycle: safe status transitions, fulfillment visibility, payment handoffs, stock coordination, and event signals for the rest of the ecosystem.

Register Go to admin
Single order truthChannels create orders here instead of maintaining competing lifecycle records.
Controlled changesCancellations, refunds, and destructive corrections stay approval-aware.
Service boundariesCatalog, Warehouse, Payments, Auth, Leads, and Notifications keep their ownership.
Live ecosystem modelAuth-protected admin data
ChannelsFlipFlop, marketplaces, Speak ASAP, Rentabox, Marathon, School Committee candidates
Orders HubContract version, external order id, lifecycle state, events, shipment links
OperationsWarehouse reservations, payment references, catalog product snapshots
AuthJWT rolesAdmin visibility and API protection
PaymentsProvider identityOrders stores references and status metadata
Leads & MarketingRead-only signalsSegmentation without owning order truth

What customers get from one order control plane

Teams can add channels and applications without rebuilding order handling every time. Orders Hub keeps the operational view consistent while letting specialized services do their own work.

Fewer manual reconciliations

External order IDs, source channels, items, totals, payments, and shipment records are visible in one operational surface.

Safer lifecycle operations

Status transitions are bounded by the order state machine, with sensitive actions separated for explicit approval.

Faster ecosystem onboarding

New services integrate through contracts, events, and role-scoped APIs instead of copying order logic.

Designed for the full commerce ecosystem

Orders Hub coordinates with adjacent services without taking ownership away from them.

CatalogProduct truth, SKUs, media, and channel readiness remain Catalog-owned.
WarehouseStock, reservations, release, fulfillment, returns, and availability remain Warehouse-owned.
PaymentsProvider sessions, variable symbols, reconciliation, and refunds remain Payments-owned.
AuthIdentity, login, JWT issuance, and role assignment remain Auth-owned.
NotificationsDelivery infrastructure stays in Notifications; Orders emits or requests lifecycle messages.
Leads & MarketingCRM and campaigns consume safe order signals without becoming order truth.

Built for traceable operations

Every future integration goal is planned with intent preservation, contract checks, sensitive-data review, role verification, build checks, and deployment evidence.