Order Management

(OMS)

End-to-end order lifecycle management from multi-source capture to allocation, fulfillment, shipment tracking, and return merchandise authorization. Handle orders from manual entry, API integrations, or e-commerce channels.

Multi-Source Capture Allocation Fulfillment Shipments Returns Holds Exception Management

Key Features

Everything you need to manage orders from capture through delivery and beyond.

Multi-Source Capture

Capture orders from any source — manual entry, API, or e-commerce channels. Each order tracks its origin for reporting and routing.

Allocation & Fulfillment

Orchestrate allocation with automatic or manual strategies. Support partial shipments and split fulfillment across warehouses.

Shipment Tracking

Full shipment lifecycle with tracking events. Create shipments, assign carriers, and track delivery status in real-time.

Returns (RMA)

Return merchandise authorization workflow. Manage return requests, approvals, receiving, and restocking or disposal.

Order Holds

Place orders on hold with reason tracking. Manage holds for fraud review, payment issues, or custom business rules.

Exception Management

Automatic detection and tracking of processing exceptions. Handle allocation failures, payment issues, and shipping errors.

Kubrik OS — agent layer

Order Management, assisted and operated by AI

Most order work is exception handling. The AI takes the exceptions and leaves the judgement calls.

AI-assisted

What the AI advises on

Available on every plan, Starter included.

Flags orders at risk — short stock, held payment, an address that will fail delivery, a promised date that no longer holds
Reconstructs the whole history of an order across channels, payments, shipments and returns in one answer
Recommends the fulfilment split that costs least and arrives soonest across locations

AI-operated

What the AI does under governance

Professional and Enterprise. Starter runs the AI in advisory mode only.

Allocates and re-allocates orders across warehouses and stores under the routing policy
Releases holds, splits shipments and re-books carriers inside value and margin thresholds
Opens RMAs and issues refunds up to the configured limit, escalating anything above it

Governed tools an agent can call in this module

allocateOrder() splitShipment() releaseHold() createReturn() issueRefund()

Autonomy is a setting, not a promise — choose the rung per role and per module

Suggest

The agent proposes. Nothing changes until a person acts on it.

Prepare

The agent builds the transaction and leaves it waiting for approval.

Execute below threshold

Acts on its own under a value or risk limit you set.

Execute by policy

Acts inside a written policy, every action fully audited.

Escalate

Anything outside the policy stops and goes to a person.

Same rules, either operator. An agent obeys the same permissions, validation and business rules a person does, and every action lands in the audit trail: who or what initiated it, the inputs, the rationale, the approvals, the resulting transaction and how to reverse it.