How Order Manager order history imports

Your past orders matter after the switch. Demand planning, reorder points and sales history all read them, and a customer may return something they bought months before you moved. The Order Manager migration can bring those orders across as history: a record of what you sold, kept out of everything that acts on live orders.

This page explains what the history import does. For the steps of the whole move, see Move from Extensiv Order Manager to SKU.io. For the file's columns, see the orders.csv reference.

Which orders come across

The history import reads orders.csv, one row per order line, for a date range you choose. Each order is judged as a whole:

The order is…	What happens
Shipped (SHIPPED, or PROCESSED_OUTSIDE_OF_SKUBANA) and dated before your inventory start date	Imported as history.
Cancelled	Skipped. A cancelled order isn't demand. The plan report counts them.
Still open (awaiting fulfillment, on hold, unresolved, …)	Refused. Open orders come in from your sales channel when you connect it at cutover, as live orders that ship from SKU.io.
Dated on or after your inventory start date	Refused. Anything from that date on moves real stock, so it can't be history.
Rows that disagree on the date, status or currency, or a malformed number	Refused, with the reason in the plan report.

The inventory start date is the line between the two systems. Opening stock is counted on that date, and every order before it is history. Set it in Settings → Inventory before the migration runs. If it isn't set, the history import is blocked.

Several years of orders can be brought across in date windows, one run per window. A re-run never creates an order twice.

What a history order looks like

Each imported order appears in Orders → Sales Orders like any other, with these differences:

• Order number: OM- plus the channel and Order Manager's own number, for example OM-Shopify-LT-5001. Orders with no channel are just OM- plus the number. The OM- prefix never collides with your own SKU.io order numbers.
• Status: closed, fulfilled and paid. The fulfilled date is the ship date from the export, or the order date when there isn't one.
• Tags: extensiv-om-history, plus om-channel:<channel> for the channel it was sold on. Filter the Sales Orders list on either tag to see only migrated history.
• Customer: matched to an existing customer by email, then by name.
• Lines: each line keeps its quantity, its price net of any line discount, and its tax. Shipping becomes a separate line, Shipping (Order Manager). A line whose SKU isn't a product in SKU.io is kept as a non-product line, so the order's total still matches Order Manager, but it doesn't count as demand for any product.

What a history order never does

A history order is a record, not work to do. Importing one:

• never moves, reserves or uses up stock, and never changes your FIFO cost layers;
• never creates a fulfillment, sends anything to a 3PL, or updates a sales channel;
• never runs a workflow, sends an email, or calls a webhook;
• never posts to your accounting.

It still counts where history should: sales history, demand planning and reorder suggestions all see it on its order date.

The imported tax always stands

Order Manager already worked out, charged and collected the tax on these orders. On a history order, that saved tax total is the order's tax:

• The order's totals show Order Manager's tax, exactly as exported.
• No edit changes it. Changing a note, the customer PO number or anything else on the order leaves the tax as it was, and tax settings in SKU.io (rates, exemptions, a tax service) never recalculate it.
• A copy of a history order (duplicate, resend or exchange) is an ordinary new order: it carries no imported tax, and SKU.io works out tax on it the usual way.

Returns against history orders

You can raise a return against a history order up to the quantity that shipped, even though the shipment happened in Order Manager. A credit against a history line refunds that line's tax in proportion to the value credited. When the return is received, the units go back into stock as a new FIFO layer at the line's estimated cost.

History orders have no delivery date, so customers can't start a return on them themselves from the customer portal. Raise it for them from the order.

If you later move the inventory start date

Move the start date earlier than your imported orders and those orders fall after it, where they could post to your accounting. Don't move it once history has been imported. If you must, talk to your SKU.io onboarding contact first.