See what disconnected Order Operations costs you. | Try the ROI Calculator
The vocabulary of order operations, defined in plain language. Each term links to the page that covers it in depth.
No terms match your search.
The quantity available to commit to new orders: on-hand inventory minus existing commitments, optionally extended by incoming supply.
An order accepted for a product that is temporarily out of stock, fulfilled when inventory arrives so revenue keeps flowing through a stockout.
The customer buys online and collects at a physical store, usually the same day; it depends on store-level inventory accuracy and a verified handoff.
The umbrella term for buy online, collect locally: covers store-stock pickup, BOPIS in US usage, and orders shipped to a store for pickup.
Pipe17's canonical data model: one normalized representation of orders, inventory, products, and returns that every connector maps into.
The customer orders online and collects outside the store: the same promise, pick, and stage pipeline as BOPIS with the handoff at the car.
Order routing scaled to a network: placing each order across warehouses, 3PLs, and stores instead of one default facility; a discipline and a product category.
The shopper-facing arrival date, computed from fulfillment location, carrier service levels, transit times, and cutoffs rather than padded defaults.
Detecting the order, inventory, and fulfillment events that deviate from their expected flow, and resolving each before it reaches the customer.
Assembling multiple products into one sellable unit with its own SKU, in advance or per order, at the price of component-level tracking.
The software that captures orders from every channel and coordinates routing, inventory, and tracking between selling and shipping systems.
The intake of orders into the managing system from storefronts, marketplaces, ERP, EDI, or manual entry, normalized into one format and queue.
Manual creation of an order by a team member for phone, B2B, replacement, or goodwill cases, treated identically to channel orders.
The coordination of every step an order takes across systems, from capture and promising through fulfillment, tracking, and settlement.
The decision of which location fulfills each order, made by rules, real-time inventory, and ranking criteria such as proximity and cost.
Accepting orders for more units than you can fulfill, usually after channel counts lag reality; it costs cancellations and account health.
The movement of goods from customer back to seller: returns, exchanges, repairs, recycling, and the work of recovering value from them.
The seller's approval for a return, issued before the item ships back, and the record that receiving, inspection, refund, and restock reconcile against.
Translating product identities between systems so marketplace, warehouse, and ERP codes resolve to the same product and inventory lands right.
Demand arriving with no sellable inventory: either supply truly ran out or sellable units sit hidden in silos, padding, or stale counts.
The 12-digit GS1 product identifier behind retail barcodes, constant across retailers while each seller assigns its own SKU.
