Skip to main content

Order management

Every order, every channel, in one queue.

Stop bouncing between seven seller centrals to mark things shipped. Pull every channel's orders into a single inbox, route fulfillment by rules, and let status sync push the shipped event back automatically.

Start free trial Book a demo
Unified order queue

The problem in 30 seconds

Order management across channels is a tab-switching tax.

  • You ship a unit. You forget to mark it shipped on eBay. The buyer opens a "where is it?" case three days later.
  • A return comes in via Shopify, the unit goes back to a different warehouse, and now your inventory is wrong on Amazon.
  • Copy-pasting a shipping address from a seller central into ShipStation is an error rate, not a process.

How it works

One inbox. Real fulfillment rules. Status that syncs.

Unified inbox

Every channel's orders, one view.

Shopify, eBay, WooCommerce, BigCommerce — every order lands in one queue, with the channel labelled, the customer normalized, and the line items reconciled against your master catalog.

  • One queue, channel-tagged
  • Customer dedup across channels
  • Filter by status / channel / warehouse / fulfillment age
Unified inbox — placeholder

Fulfillment routing

Rules pick the right warehouse, every time.

Route by closest warehouse, in-stock first, channel preference, or any combination you build. The order arrives in the right pick queue before your operator even sees it.

  • Distance-aware routing
  • Channel-preferred warehouse fallback
  • Bulk re-route on warehouse closure
Routing rules editor — placeholder

Status sync

Mark shipped here. The marketplace knows.

Mark an order shipped with a tracking number once. We push that to every channel the order came from. Returns, cancellations, and refunds flow the same direction.

  • Tracking number pushed to source channel
  • Returns workflow updates inventory + channel automatically
  • Refund handling syncs both directions
Status sync flow — placeholder

Under the hood

What order management actually does.

Bulk fulfillment — pick 50 orders, ship in one pass
Returns workflow with state machine (requested → in-transit → received → restocked)
Refund handling syncs to source channel
Custom statuses for tenant-specific workflows
Address verification at pre-fulfillment
Packing slip generation with custom branding
Carrier label pre-staging for batch printing
Audit log per order — every state change with actor + timestamp

Who it's for

Built for teams that move boxes.

For ops leads

One inbox. Filters that make sense. Routing rules you can change without an engineer.

For warehouse teams

Orders land in your pick queue pre-routed. Bulk fulfillment cuts pack time in half.

For customer support

"Where's my order?" lookup across every channel from one place. No more channel-hopping.

Pairs with

What order management talks to.

Inventory sync

One stock count. Every channel. Order management reads from it; sync updates it after fulfillment.

Learn more

Warehouse ops

Pick lists, transfers, cycle counts — the workflows your warehouse runs after orders are routed.

Learn more

Reports

Revenue per channel, fulfillment lead time, return rate by SKU — every order becomes a reportable data point.

Learn more
We were tracking orders in three separate marketplace dashboards plus a shared spreadsheet. One queue with channel-tagged filters cut our daily ops sync from 45 minutes to 10.
Beta customer

Head of fulfillment, Early access program

Order management — common questions

Order normalization keeps marketplace-specific fields (Amazon order ID, eBay buyer username, etc.) accessible while presenting a unified shape. Custom fields per channel are stored as JSON for queryability.
Orders sit in the queue with their original timestamps. When sync recovers, missed orders backfill in chronological order. Your fulfillment SLA timer pauses for the gap so warehouse SLAs aren't penalized for our downtime.
Yes. Partial fulfillment is first-class: ship 3 of 5 line items now, update tracking, ship the rest later. The source channel sees two shipment events with separate tracking numbers.
Non-physical line items skip pick-list generation and mark fulfilled on payment. The same status-sync flow notifies the channel.
Returns flow back through the unified queue with a return_requested status. Inventory restocks (or marks damaged) based on your operator's call when the package arrives.

One queue. Every channel. Real status sync.

14-day free trial. No credit card. Connect one channel and route your first order.

Start free trial Book a demo