| Term | Meaning |
|---|---|
| Account | The outer boundary of your business in OTO. Nothing crosses it. |
| Area | A delivery zone drawn geographically, attached to hubs and rules. |
| Available | Stock that can still be promised to a customer. Falls when an order is assigned to a pickup location. |
| AWB | Air waybill — the carrier’s shipping label and tracking reference. |
| Bin | A specific location on a shelf, with a type, a capacity and sometimes a preferred SKU. |
| Box | One physical parcel. A shipment can contain several, each with its own barcode and weight. |
| Brand | A trading identity within one account — logo, sender name, templates and tracking page. |
| Branch | A shop configured as a hub, so it can fulfill and ship orders. |
| Carrier | The company that carries the parcel. Called a delivery company or DC in the API and in rules. |
| Chargeable weight | What a carrier bills for — the greater of actual and volumetric weight. Desi in Türkiye. |
| City group | Several cities named together so one rule can reference them all. |
| Click and collect | Bought online, collected in a shop, with the handover recorded. |
| COD | Cash on delivery. The carrier collects payment at the door and remits it to you. |
| Condition | A test against an order — value, weight, destination, brand, tags and much else. |
| DC | Delivery company. See Carrier. |
| Delivery option | One named service from a carrier, such as Aramex Same Day. What a shipping rule actually selects. |
| Dispatching unit | A trolley, cage or pallet grouping packed parcels for one carrier’s collection. |
| Driver | Someone on your own fleet, working in the OTO FLEX app. |
| Feasibility | Whether a carrier is eligible at all, checked before selection. A rule can match an order and still find no carrier available. |
| Hub | Anywhere you hold stock and can ship from — warehouse, shop or third-party site. Called a pickup location in the API. |
| Hub code | The identifier that joins a hub to the same place in your ERP, POS or sales channel. |
| incrementId | The merchant-facing order number. Kept unchanged when an order syncs from a sales channel. |
| On Hand | Stock physically in the building. Falls when goods leave, at fulfillment. |
| Order | What the customer bought. Exists whether or not anything has shipped. |
| otoId | OTO’s internal reference for an order. Unique across the platform and never reused. |
| Pickup location | The API’s name for a hub, with a type of warehouse or branch. |
| Preparation SLA | How long a hub takes to get an order ready, in hours. Defaults to 24. |
| Proof of delivery | What a driver must capture to close a task — a photo, a code, a barcode, or a combination. |
| Putaway | Moving received goods into their bins. |
| Role template | A named set of permissions applied to people. One per user at a time. |
| Route | An ordered set of stops assigned to one driver. |
| Rule | Conditions plus what to do when they match. Evaluated in order. |
| Sales channel | A storefront, marketplace or app you sell on, connected to OTO. |
| Serving radius | How far a hub will deliver, in kilometers. |
| Shipment | The booking with a carrier to move goods, created from an order. |
| Short address code | Saudi national addressing — four letters and four numbers identifying a precise address. |
| SKU | The product identifier, and the join between OTO and every other system you run. |
| Surcharge | A charge a carrier adds after the fact, usually when a parcel is heavier or larger than declared. |
| Task | One stop on a route — a pickup or a delivery. |
| User type | What kind of account a person has: Company Admin, Warehouse User, Branch User, Driver User, Customer Service User or Brand Manager User. |
| Volumetric weight | Weight calculated from a parcel’s dimensions, used when it exceeds actual weight. |
| Wave | A batch of orders released to the warehouse floor together, so one walk serves many orders. |
| Webhook | An event OTO pushes to a URL of yours, so your systems are told rather than asking. |
| Zone | A group of bins, usually an aisle, worked by one picker. |
Three pairs worth knowingHub and pickup location are the same object. Carrier and delivery company (DC) are the same company. Service and delivery option are the same thing — and it is the delivery option, not the carrier, that a shipping rule selects.Each pair is one name from the dashboard and one from the API. See Core concepts.