Skip to main content
A dozen words carry most of OTO. Several of them mean something more specific than they sound, and a few appear under two different names depending on whether you are looking at a screen or an API response. This page is the reference for both.

Order and shipment are not the same thing

This is the distinction everything else rests on, and the one that most often trips people up.
One order is not necessarily one parcelAn order can be split across locations, shipped on more than one carrier, packed into several boxes, and returned in pieces. Each of those is a separate shipment or box against the same order.Which is why status questions have to name their subject. “Is it delivered?” is ambiguous for an order in three boxes; it is precise for a shipment.

The same thing, under two names

Some objects are called one thing in the interface and another in the API or in older material. These are the ones worth knowing.

Stock is two numbers, not one

Inventory carries Available and On Hand, and they move at different moments.
The gap between the two numbers is reserved stockBetween assignment and dispatch, an item is spoken for but has not moved. Available has dropped; On Hand has not. One order produces two separate movements, sometimes days apart.This is why a stock count that matches On Hand can still look wrong against Available, and why the right question is not “how much do we have” but “how much can we still sell”. See Inventory tracking.

Places

Inside a warehouse

All of these live in Warehouse Management and are configured per hub.

Your own fleet

Identifiers

Order numbers

Every order carries two identifiers, and they do different jobs.

Where the order number comes from

Channel orders keeping their own number is the important partWhen a customer emails about order #1043, that is the number on their confirmation from your storefront. Because OTO did not renumber it, it is also the number your agent searches, the number on the AWB, and the number in the tracking message.The alternative — a fulfillment system that assigns its own numbers — means every customer conversation needs a translation and every reconciliation against the channel needs a mapping table. OID- appears only where there was no channel number to keep.

Prefixes and suffixes

Related records are built from the order number rather than getting identities of their own — whatever that number happens to be.
The suffix carries information worth readingBecause a return is numbered from its order, it matches to the original sale without anyone looking anything up — and an order carrying -R2 has been returned against twice, which is a pattern worth noticing on a customer or a product. See Return Management.If a prefix in OTO does not suit a downstream system, webhook registration accepts an orderPrefix to strip before the payload is sent. See Webhook events.

Money

Volumetric weight is where shipping bills surprise peopleA large, light parcel is billed on the space it occupies rather than what it weighs. Declare a pillow at its actual weight and the carrier will bill it at several times that.The difference arrives weeks later as a surcharge on an invoice, long after the order was priced — which is why the reconciliation exists, and why declared dimensions are worth getting right at packing rather than at invoicing.

Rules and automation

Identity and access

Where to go next

What is OTO

The platform in one page.

Omnichannel OMS

Where an order lives.

Developers

The same objects, as an API.