Before the Shelf: How Goods Become Ready to Sell
The inbound map, the cast, and the cheat sheet for retail fulfillment.
Part 1 of 18 · Before the Shelf
The truck is here. Why can nobody sell the books?
The delivery record says the books have arrived. The warehouse team can see the cartons. Yet I still cannot order a copy in our illustrative scene.
Where is the missing step?
Maya has done more than send a truck. She has promised the right edition, in the right quantity, by an agreed date. eComm Inc must identify the load, count it, resolve damage, record its location and decide which copies are eligible for sale. A successful journey between addresses leaves several of those promises unfinished.
This is the Inbound Inventory Supply Chain series within Supply Chain Management in hyperscale ecommerce. The companion Procure-to-Pay series follows purchasing commitments and supplier settlement; the outbound series follows a finished-product sale to the end consumer. Here, the completion test is usable inventory. Those lifecycles overlap, so a receipt does not by itself close a supplier claim or fulfill a customer order.
This series follows one question all the way upstream: what must become true before a good can be used or sold? It begins with a book on a retailer's shelf and reaches back to the paper, the printing machine and the decisions that made the book possible.
Why this matters before we learn the vocabulary
A low freight quote is useful only if the journey supports the business. Maya can save on transport and lose more through damage or a missed selling window. eComm Inc can unload faster and merely move its queue to inspection. Mayan can deliver a printing machine on time while Maya waits for the site, installation or acceptance work that makes the machine productive.
These are different problems with a similar symptom: the goods are present, but the expected benefit has not arrived. Knowing the mechanism helps decide whether to buy more stock, improve data, change a route, add capacity or fix the handoff that is already failing.
It also changes how we read a business. More warehouse space may improve availability; it may simply accommodate more waiting. Lower inventory may reflect faster replenishment, weaker service or a burden shifted to suppliers. The physical story helps explain the financial one.
Meet Maya, Mayan and Sathya
Maya runs Stories Inc, our fictional basic vendor. She produces books and sells them to eComm Inc, our fictional ecommerce retailer. Mayan runs Sapiens Inc, our fictional, more sophisticated supplier of printing machines. He supplies equipment to Maya; he is not her paper supplier. Separate, unnamed suppliers provide paper, covers, binding materials and packaging.
Sathya Narayanan is the author and the customer in our illustrative scenes. The customer viewpoint gives the chain a reason to exist: someone wants a book. The scenes are teaching examples, not accounts of my actual purchases.
There are two inbound stories here. A printing machine reaches Maya and must become productive equipment. Books reach eComm Inc and must become usable inventory. Recurring material deliveries feed Maya's production between those two journeys. Equipment, materials and finished goods share some logistics concepts, but their completion tests differ.
Our main book case is a wholesale sale to eComm Inc. When Maya instead sells through a marketplace and buys fulfillment services, we will say so explicitly. Goods in the same warehouse can belong to different businesses and serve different promises.
The same cast appears in Behind the Buy Button and From Click to Doorstep, with distinct worked transactions. The commercial series has eComm Inc buy a machine for its own print-on-demand operation; here, Mayan delivers equipment to Maya. Our main book shipment is a separate inbound case, not a continuation of the commercial series' quantities or costs.
The cheat sheet to keep beside the map
| Decision | Words you will meet | The question underneath |
|---|---|---|
| Know the need | Forecast, service level, replenishment, safety stock | What might be needed before fresh supply becomes usable? |
| Make a feasible commitment | Sourcing, purchase order, acknowledgment, bill of materials | Can the supplier actually make and release the required goods? |
| Describe the goods | SKU, trade item, lot, unit of measure, pack hierarchy | Do both sides mean the same product and quantity? |
| Describe the movement | Shipment, ASN, pallet identifier, bill of lading | Which goods are declared on which movement? |
| Allocate responsibility | Shipper, consignee, carrier, broker, freight terms | Who arranges, performs, pays and bears each responsibility? |
| Choose the journey | Parcel, LTL, truckload, intermodal, consolidation | Which feasible route balances time, cost and handling? |
| Cross a border | Importer, classification, origin, customs release | Who supplies accurate evidence and satisfies each requirement? |
| Receive safely | Appointment, yard, dock, inspection, quarantine | Can the destination accept the actual load safely? |
| Make stock usable | Goods receipt, putaway, available inventory, reservation | What remains before these units can support a promise? |
| Learn from disagreement | Shortage, claim, correction, reconciliation | What is missing, what is uncertain, and who must resolve it? |
GS1's public labeling guidance distinguishes a shipment declaration from the receiver's checks. ICC likewise distinguishes transport obligations and risk from ownership. These are useful foundations for keeping our fictional map honest. The framework and examples in this series are my teaching synthesis, not either organization's operating prescription.
Five flows and several clocks
The goods move through physical locations. The commitments describe what each party has promised. The information records expectations and observations. The money follows its own commercial terms. The exceptions preserve the gaps between them. A carrier can complete its movement while a quantity dispute remains open and the invoice still awaits resolution.
Our main teaching shipment contains 1,000 books, arranged as 100 cartons of 10 books. Later, eComm Inc will count 992, temporarily hold 12, and release 980. We will preserve all those numbers rather than overwriting them with one field called “quantity.”
The total lead time ends at usable inventory. It may include supplier preparation, pickup waiting, transit, border procedures, dock waiting, receiving, inspection and putaway. Some steps overlap; a real timeline must avoid counting the same hour twice.
Old ideas, newer capabilities
Consolidation, purchasing, inventory buffers and receiving long predate online shopping. Newer tools can make data travel sooner, let smaller sellers access shared logistics, and coordinate more countries and partners. They still depend on accurate product information, physical capacity, lawful trade and credible promises. Cross-border selling is old; its reach and ease of coordination have changed unevenly.
The eighteen essays move from these foundations to sourcing, transport, customs, receiving, economics, resilience and recent innovations. The last essay assembles a complete shipment. This opening stands alone; the full reading path above is there when a question needs more depth.
What this series does and does not try to teach
Our boundary ends when goods are usable for production or eligible for downstream fulfillment. Customer-order picking, packing, last-mile routing and consumer returns are covered in the outbound companion, From Click to Doorstep. We discuss them here only when they change an inbound decision. Specialist food, medical, dangerous-goods and oversized supply chains need additional rules; a book shipment cannot stand in for them.
Start with three marks on a page: the physical route, the party responsible at each handoff, and the event that completes each promise. Then follow the books until those marks agree. That is how a box at the gate becomes a book Sathya can buy.
The inbound map: steps and the records they create
“Receive the books” sounds like one action. A system may need an expected delivery, an appointment, a posted receipt and warehouse work. If quality inspection applies, it needs that evidence too. The step is what people or systems do. The entity is the named record they create or update.
This view follows books from Maya’s Stories Inc to eComm Inc. I use documented SAP names for transport and warehouse objects, GS1’s message terminology, and a Microsoft appointment example. These are recognizable industry implementations, not a claim that every business uses one combined schema. The commercial graph explains the buyer’s PO, seller’s SO and invoice branch.
Plan, pack and announce the movement
| Step | Digital record created or updated | What I should recognize |
|---|---|---|
| Ordering / outbound delivery creation | Buyer creates a purchase order (PO); seller records a sales order (SO) and creates an outbound delivery for the selected lines. | Commercial demand and the seller’s logistics document remain linked, separate records. |
| Freight unit building | SAP creates a freight unit (FU) from order- or delivery-based transportation requirements. | A grouping of goods for transport planning. It is not a physical carton or pallet. |
| Transportation planning | Planner creates a freight order in the road/rail example. | The transport execution document. SAP distinguishes a freight booking for air/sea; these are not simply “requested” and “confirmed” versions of one noun. |
| Packing | Warehouse creates or updates a handling unit (HU) record. | Identified packaging and its contents, such as a pallet containing cartons. HUs can be nested. An SSCC, when used, identifies the logistic unit; it is not the whole HU record. |
| Shipment notification | Shipper sends a despatch advice / advance shipment notice (ASN). | Order references and declared goods/package information sent ahead of receiving. |
| Inbound delivery creation | Receiver creates or updates an inbound delivery. | The receiving system’s expected quantities and references. Receiving the message does not mean receiving the goods. |
The distinction between freight unit, freight order and freight booking, and handling unit comes from SAP’s public object definitions. GS1 describes the despatch-advice exchange; SAP shows an inbound delivery created from a shipping notification.
Buyer pays freight or seller pays freight describes a term of the arrangement. Record the transport arranger separately. The payer label does not create a freight order, prove carrier acceptance, or determine ownership on its own.
Arrive, receive, inspect where required, and put away
| Step | Digital record created or updated | What I should recognize |
|---|---|---|
| Appointment scheduling | Site/transport coordinator creates a dock appointment for a load. | The agreed handling window at an existing dock. The dock itself is a location/resource, not a record created for this shipment. |
| Driver check-in / unloading | Site records actual arrival and updates the appointment or yard record. | An appointment and a checked-in vehicle are different states. Neither establishes the item count. |
| Goods receipt posting | Receiver creates a goods receipt document; SAP uses a material document for the posting. | Quantity received against the inbound delivery/PO, with references for subsequent checks. |
| Quality inspection, when configured | Quality process creates an inspection lot and records inspection results. | The defined scope of inspection and its evidence. A lot for inspection is not automatically the product’s manufacturing batch. |
| Quality disposition | Quality role records a usage decision on the inspection lot. | The decision and configured follow-up treatment, which may change stock status or trigger movement work. |
| Putaway | Warehouse creates and confirms a warehouse task (WT). | An instruction to move goods to a destination bin, then evidence of execution. Confirmation updates location records; it need not remove a quality hold. |
Microsoft’s appointment example and driver check-in procedure separate planned and actual arrival. SAP documents receipt posting, inspection and usage decisions, and warehouse tasks for putaway.
The dashed branch matters. Inspection is not a universal prerequisite for putaway. Oracle documents direct receipt, standard receipt and inspection receipt routes; some combine receiving and putaway, while others separate them. Our inspection branch illustrates one route, not a mandatory sequence. Goods can also be stored while held. Oracle receipt routing.
What I leave outside the first map
A shipment groups goods for delivery; a load groups transport work and may contain several shipments. These are distinct from the HU that identifies packed contents. Microsoft’s release-to-warehouse model provides a concrete shipment/load distinction. A bill of lading, waybill, customs declaration and freight invoice add documents for the applicable route and agreement. None is another name for an ASN.
Supplier, product, packaging and location master data already give these records meaning. The SKU identifies an item in a business’s catalogue; a unit of measure tells me whether “one” means a book, carton or pallet. Those details become essential when quantities disagree.
Follow product and quantity identity, shipment messages, dock capacity or receipt and availability as needed. The customer-fulfillment graph follows goods toward the consumer.
Sources checked October 22, 2026. Cards name steps and records; arrows show selected handoffs and references. This is a directed acyclic teaching view of forward work, not a mandatory timetable or a private company’s system design.
Public sources and evidence boundary
Public material checked on 18 October 2026. Sources support the named definitions or frameworks; the scenarios, diagrams, calculations and proposed decisions are original teaching examples. No private company systems or performance data are described.