Skip to content

Kentro OS · Order management

Ecommerce order management with every channel in one queue

Kentro OS brings orders from Shopify, WooCommerce, Amazon, TikTok Shop, retail EDI, your B2B portal and orders your team enters by hand into one list. Each order carries its invoices, payments, routing and shipments. Your team, Kentro AI and your own agents read the same record.

  • Store, marketplace, EDI and manual orders
  • Invoices and payments on the order
  • Routing to warehouses, vendors and 3PLs
  • Included in every Kentro OS plan
On the floor
In the office
Kentro OS · Fulfillment Queue
Order FH-10482 updates the moment it is scanned
A pick confirmed on the warehouse handheld moves the same order from Picking to Packed in the fulfillment queue the office is watching.

What is ecommerce order management?

Ecommerce order management is the work of collecting orders from every sales channel, checking stock and payment, routing each order to a warehouse, vendor or 3PL, and tracking it until it ships. Kentro OS, an ecommerce ERP, does this in one queue for store, marketplace, EDI, wholesale and manual orders, with invoices and payments on the same record.

What it does

From the moment an order arrives to the moment it ships

One order list for every channel

Orders from connected stores and marketplaces, retailer purchase orders that arrive by EDI, wholesale orders from the B2B portal, orders created through the API and orders your team enters by hand all land in one list. Search by order number, filter by channel, tag, customer, status or ship-to address, and save the filter as a view.

  • Shopify, WooCommerce, Amazon and TikTok Shop
  • Retail EDI through SPS Commerce, drop-ship through Rithum DSCO
  • Manual orders one at a time or from a CSV file
Multichannel selling
One order list with orders from several sales channels

Statuses and holds that say what each order needs

Every order shows two statuses side by side. Fulfillment status runs from pending and processing to partly fulfilled, fulfilled and delivered. Financial status runs from unpaid to partly paid, paid and refunded. From the order you can cancel it, revise it, mark it a backorder, give it shipping priority or keep it out of the shipping queue until you release it.

  • Fulfillment and financial status on every row
  • Backorder, priority and exclude-from-shipping controls
  • A pending review list for orders that wait on a stock check
An order with its fulfillment status and its financial status

Invoices, payments and the customer on one record

Create the invoice from the order and email it to the customer. Record a payment against an invoice, charge a saved payment method or apply store credit. Refund in full or in part. Each customer has one record with their orders, shipments, invoices, payments and credits.

  • Invoices created from the order
  • Full and partial refunds, with store credit as an option
  • Invoices and payments sync to QuickBooks Online or Desktop
Payments in Kentro OS
An invoice with a payment applied to it

Routing to the right warehouse, vendor or 3PL

When an order arrives, Kentro creates its fulfillment orders. Routing rules for the sales channel decide where each one goes: a warehouse you choose, the warehouse for the fulfillment zone, a vendor that drop-ships, or a 3PL. With no matching rule, the order goes to the channel default warehouse. One order can split into several fulfillment orders, and you can pin a warehouse by hand.

  • Rules on tags, the customer, the order total or the address
  • One fulfillment order per warehouse, vendor or 3PL
  • Orders for Shipfusion and 3PLGUYS go through their integrations
Automation rules
One order routed to one of several warehouses

A fulfillment queue the warehouse works from

Routed orders appear in the fulfillment queue with their step and status. The team generates pick lists for a batch of orders, packs, and ships with a rate-shopped label, or picks on the handheld in Kentro WMS. When the label prints, the order status changes and the tracking number goes back to the store.

  • Pick, pack and ship steps on every row
  • Pick lists for one order or a batch
  • Saved views for the filters you use every day
Shipping and labels
A fulfillment queue with orders at the pick, pack and ship steps

One job, three ways

Find out why an order has not shipped, three ways

Find out why an order has not shipped

  1. In the app

    Open the order. Its fulfillment status, routing, stock and payment are on one page. Fix what blocks it and it moves on in the fulfillment queue.

    An order page in Kentro OS with status, routing and payment
  2. With Kentro AI

    Ask "Why has order 10482 not shipped?" Kentro AI reads the order and the fulfillment pipeline and answers with the reason and a link to the record. It reads. You act.

    Kentro AIIn Kentro
    1. you ›Why has order 10482 not shipped?
    2. getOrderDetailRead the order, its lines and its fulfillment orders
    3. getFulfillmentPipelineRead open fulfillment orders by status and age
    4. One line is waiting on stock at the main warehouse. The other two lines are picked. The order record is linked below.

  3. With your agent

    Your agent reads the same order over MCP with getOrderDetail and listOrders, or starts from the investigate-order prompt. It creates and updates orders through the Channel API with a write-scoped key. Buying labels happens in the app.

    ClaudeConnected to Kentro over MCP
    1. you ›Which of yesterday's orders are still not shipped, and why?
    2. listOrdersListed yesterday's orders that are not fulfilled
    3. getOrderDetailRead each open order and its fulfillment orders
    4. Here are the open orders, grouped by reason: waiting on stock, waiting on payment, or packed with no label yet.

Questions about order management in Kentro OS

Which order sources does Kentro OS bring into one queue?

Connected stores and marketplaces (Shopify, WooCommerce, Amazon and TikTok Shop), retailer purchase orders through SPS Commerce EDI, drop-ship orders through Rithum DSCO, wholesale orders from the Kentro B2B portal, orders created through the Channel API, and orders your team enters by hand or uploads as a CSV file. They land in one list with the channel shown on each row, and they draw on one stock count.

Can I split an order across warehouses or send part of it to a 3PL?

Yes. Kentro creates one fulfillment order for each place an order ships from, so one order can ship partly from your own warehouse and partly from a vendor or a 3PL. Routing rules decide the split when the order arrives, and you can pin a warehouse by hand on a single order. Each fulfillment order has its own status, and the order shows partly fulfilled until the last one ships.

How do I hold an order or keep it out of the shipping queue?

Open the order and use Exclude from Shipping to keep it out of the fulfillment queue, or mark it a backorder until stock arrives. Manual orders can also wait in a pending review list until someone accepts or rejects them after a stock check. Rules can tag orders or hold them out of the queue as they arrive. To release an order, include it again or release the backorder.

Does Kentro OS handle returns and RMAs?

Not as a workflow. Kentro OS has no return authorization, return tracking or inspection flow. What it does have: full and partial refunds on an order, refunds to store credit, credits on the customer record, and a one-off return label from the quick ship screen. If returns are a large part of your operation, plan to keep your returns tool and record the refund in Kentro.

Can I enter phone, wholesale or offline orders by hand?

Yes. The New Order screen walks through five steps: the sales channel, the customer and order settings, addresses, items and a review. You can pick a price list for the customer, override a price, set fixed or free shipping and save the order as a draft. For many orders at once, upload a CSV file. Submitted orders land in the same list as orders from your stores.

What can an AI agent do with my orders?

Over MCP, an agent reads orders with your permissions: it lists orders with listOrders, opens one with getOrderDetail and checks the fulfillment pipeline with getFulfillmentPipeline. To create or update orders, it uses the Channel API with a write-scoped key. Agents do not buy labels or issue refunds over MCP; a person does that in the app.

Put every order in one queue

Connect a store, see its orders next to your wholesale and retail orders, and ship from one list.

Choose what this site may use. Necessary storage is always on.

  • Necessary

    Remembers this choice for 12 months and keeps forms safe from spam. No tracking.

    Always on

Cookie policyPrivacy policy