1. What inbound actually is

A retailer’s buyer in Bentonville signs a purchase order for 50,000 units of a private-label kitchen blender. The supplier in Guangdong has 60 days to make them. Once they’re made, who gets them across the Pacific, through US customs, into a Walmart DC, and onto a truck headed for a store? Whose problem is that?

If your answer is “the supplier” you’re describing one Incoterm. If it’s “Walmart’s transportation team” you’re describing another. If it’s “procurement, but they call logistics for help” you’re describing the most common organizational arrangement, and most of the reason inbound flows go wrong.

Inbound logistics is the set of disciplines that gets that PO converted into pallets-on-the-dock at the receiving DC. This chapter draws the boundary lines around what counts as inbound, and what doesn’t.

Starting cold? Inbound is everything that happens between a supplier’s loading dock and your receiving dock. The rest of this section assumes those boundaries.

The working definition

Inbound logistics is the set of physical, contractual, and informational flows that move goods from a supplier’s outbound dock to your receiving dock, including everything required to make those goods legally importable, financially accounted for, and physically putaway-ready.

Three things fall inside that fence:

• Physical flow: packing, handling, main-carriage freight, transshipment, final-mile delivery to your DC or plant.
• Contractual flow: the Incoterm, the bill of lading (or AWB , or CMR ), the commercial invoice, the packing list, insurance, any special permits or certificates (phytosanitary, origin, fumigation, FDA prior notice).
• Informational flow: ASN (advance ship notice), EDI 856, booking confirmation, vessel/flight/trailer tracking, customs release messages, carrier PoD .

What inbound is not

Three common scope mistakes

• Inbound is not procurement. Procurement decides what, from whom, and at what price. Inbound decides how it gets here. They’re adjacent but not the same. When one team owns both, the tradeoffs get collapsed in ways you feel later.

• Inbound is not inventory management. Once the pallet is scanned at goods-in, inbound is done. What happens next (putaway, replenishment, cycle count) is warehousing.

• Inbound is not the inverse of outbound. They share carriers, lanes, and even trailers, but the decision logic is different: inbound optimizes for landed cost and reliability into finite DC capacity, outbound optimizes for service level and cost-to-serve out to a fragmented demand signal.

  Where some orgs combine them anyway: large retailers (Walmart, Costco, Amazon) deliberately run inbound and outbound under one transportation team to maximize asset utilization and backhaul economics. Defensible at scale. Below that scale, the decision logics drift apart and combined ownership tends to produce muddled tradeoffs.

The three flows, mapped

Picture a single shipment leaving Vietnam for a US DC. Three things have to arrive together for that shipment to count as “in”:

1. The goods. The actual containers, pallets, parcels.
2. The documents. Commercial invoice, packing list, BoL, certificate of origin, any partner-government-agency permits.
3. The data. ASN , PO acknowledgement, EDI 856, carrier tracking milestones.

If the goods arrive without the documents, they sit in bond accruing demurrage. If the goods arrive without the data, your receiving team can’t plan dock doors and your putaway exceptions spike. Inbound delays often trace back to a late or wrong document or data stream, not the physical leg.

Stream	Examples	Failure mode when it lags
Goods	The actual container, pallet, parcel	Empty shelves, line-down at the plant
Documents	CI, packing list, BoL, C/O, permits	Goods sit in bond, accrue demurrage
Data	ASN, PO ack, EDI 856, tracking	Receiving can’t plan dock doors, putaway exceptions, phantom inventory

Pure inbound vs. hybrid flows

Imagine you’re running inbound for a multinational electronics company. On any given week, you’ll see at least five different shapes of inbound flow:

• Classic supplier-to-DC. A contract manufacturer in Thailand makes finished tablets, sends a 40-foot container to a regional DC in Memphis. Most of this site is about flows like this one.
• DC-to-DC replenishment. Your Memphis DC pulls inventory from the master DC in Reno. Technically intra-network, but operationally inbound to the receiving DC. Uses dedicated fleet or contracted LTL more than common-carrier lanes.
• Supplier-to-plant direct. A wire-harness supplier in Monterrey ships components four times a week to your assembly plant in Tennessee. Bypasses the DC entirely; common in automotive, aerospace, and CPG manufacturing. Runs on tight windows (often JIT/JIS) and lives or dies by sequencing.
• Vendor-managed inventory (VMI) inbound. A bearings vendor stocks the parts cage at your facility. The vendor owns the stock at your dock until you consume it. Physical inbound looks normal; financially everything changes. The supplier carries the inventory cost. Receipt becomes a consumption event, not an ownership event. Common in industrial MRO, automotive components, hospital supply.
• Crossdock inbound. Goods arrive at a regional facility and ship out to stores within hours. Receiving looks like inbound but putaway looks like outbound staging.
• Returns / reverse inbound. Goods coming back into the network. Operationally grouped with inbound; financially and procedurally different (RMA, disposition, refurbishment, resell vs. write-off). Treated lightly in this section; meaningful for any company with a real e-commerce channel. See Chapter 11.

Who owns it, in practice

This is where most inbound problems start. In most mid-to-large companies, inbound is a shared responsibility that lives uncomfortably across three teams:

• Procurement / sourcing owns supplier contracts and Incoterms.
• Logistics / transportation owns carrier contracts and execution.
• Operations / DC owns dock scheduling, receiving, and chargeback enforcement.

Picture how this fails: procurement signs a great DDP unit price (the supplier handles everything, all the way to your door). The procurement team logs a savings number. Six months later, the logistics team realizes they have no visibility into the lane and can’t enforce SLAs because they’re not the shipper of record. Operations gets hit with trailer-pool chaos and zero ASN integration because the supplier’s forwarder doesn’t connect to the buyer’s TMS.

Unit cost went down. Total landed cost went up. And nobody on either side of the org chart can name who owns the gap.

Putting it together

Define inbound by its boundaries, not its activities. Boundary-in: the moment title, risk, or control transfers from supplier to you (per Incoterm). Boundary-out: the moment the goods are scanned into your inventory system. Anything between those two points is inbound’s problem, including the paperwork, the data, and the political seams.

How to think about inbound on your own network

A few decisions to revisit:

When you’re evaluating a new lane: start by drawing the physical, contractual, and informational flows for that lane. Which team owns each handoff? Most teams can name the physical owner. Half can name the contractual owner. Few can name the data owner. The unnamed handoff is your problem before it ever shows up as a delay.

When inbound is misbehaving: ask “who, on my org chart, wakes up worried when one of these streams slips?” If the answer is “nobody” or “everybody,” you’ve found the problem before you’ve measured it.

When procurement wants to switch to DDP for “simplicity”: the simplicity is real, but you’re trading visibility for it. That trade is right for some lanes (low-volume, complex destinations, suppliers with stronger local logistics than yours) and wrong for most.

When your top-3 lanes share an owner gap: that’s not three separate problems, it’s an org-design problem. Solve at the seam, not at the lane level.