SAP & Enterprise Systems
Inbound and Outbound Logistics
Inbound logistics covers goods coming into an organization — typically a delivery from a vendor, received and recorded as a goods receipt. Outbound logistics covers goods leaving — typically a delivery to a customer, recorded as a goods issue. SAP models both directions with a similar underlying pattern (a delivery document, followed by the physical movement, followed by a confirming posting) even though what triggers each one, and what departments care about it, differ.
Why it matters
- It's the physical side of processes that are otherwise just data
- A purchase order or a sales order is a commitment on paper; inbound and outbound logistics are where that commitment actually becomes a physical event — something arrives, or something leaves — that the system needs to record accurately.
- It's where inventory quantities actually change
- A goods receipt increases on-hand inventory; a goods issue decreases it — these postings are the actual mechanism by which the system's inventory numbers stay tied to physical reality, rather than being adjusted through purchase orders or sales orders alone.
- It connects procurement and sales to finance
- A goods receipt is what typically enables invoice verification on the purchasing side (covered in this section's SAP MM guide), and a goods issue is often what triggers billing on the sales side — the physical event is frequently the point that unlocks the financial step.
- Timing and accuracy here affect everything downstream
- A goods receipt or issue recorded late, or for the wrong quantity, doesn't just create a local data error — it propagates into inventory reports, matching processes, and financial postings that depend on it being right.
Inbound: goods receipt
When a vendor delivery arrives, a goods receipt is posted against the relevant purchase order, recording what actually arrived — which may match, or may differ from, what was ordered. This posting is what actually increases the recorded inventory quantity; before it happens, the purchase order represents an expectation, not a change in stock on hand. The goods receipt is also typically what a later invoice gets checked against, alongside the purchase order itself, in the matching process covered in this section's SAP MM guide — which is part of why accuracy at this step matters beyond just the warehouse's own records.
Outbound: goods issue
On the other side, when goods leave — most commonly to fulfill a customer's sales order — a goods issue is posted, which is what actually decreases the recorded inventory quantity. Depending on how the warehouse is set up, this can involve a picking step first (locating and gathering the specific items, potentially using the bin-level detail from WM or EWM, both covered in this section's own guides) before the goods issue itself is posted. The goods issue is frequently the trigger that allows billing to proceed on the sales side, similar to how a goods receipt enables invoice verification on the purchasing side — in both directions, the physical confirmation is what unlocks the corresponding financial step, rather than the financial step happening independently of what actually moved.
Mistakes people make here
- Assuming inventory changes the moment a purchase or sales order is created
- The order itself is a commitment, not a stock movement — on-hand inventory only actually changes when the corresponding goods receipt or goods issue is posted, which can happen well after the order and doesn't always match it exactly.
- Not accounting for partial or over/under deliveries
- A goods receipt or issue doesn't have to exactly match the originating order's quantity — partial deliveries, over-shipments, and under-shipments are all real, expected scenarios the system has to represent accurately, not edge cases to ignore.
- Treating the physical movement and the system posting as automatically the same event
- The system only knows about a movement once it's recorded; if goods physically move but the corresponding posting is delayed or skipped, the system's inventory picture is temporarily wrong until it's corrected.
- Overlooking the link to downstream financial processes
- A goods receipt or issue isn't just a warehouse-level event — it's frequently the specific trigger for invoice verification or billing, so a delay or error here has direct financial-process consequences, not just inventory-accuracy ones.
Strengths and trade-offs
Where it is strong
- Tying inventory changes to a specific, confirmable posting (goods receipt or issue) keeps stock records grounded in actual physical events, not assumptions.
- Linking these postings to invoice verification and billing gives the system a built-in check between what physically happened and what gets financially processed.
- The same underlying pattern applies to both directions, which makes the two processes easier to reason about together rather than as unrelated mechanisms.
The trade-offs
- The system's inventory accuracy depends entirely on these postings being made promptly and correctly — a delayed or skipped posting creates a real, if temporary, mismatch with physical reality.
- Handling partial deliveries, over-shipments, and exceptions adds real process complexity beyond the simple, expected case.
- Because downstream financial steps depend on these postings, an error here doesn't stay contained to inventory — it can hold up invoice matching or billing as well.
Who needs this
Anyone working with procurement, sales, or warehouse processes in SAP, or building reports and integrations against inventory movement data, needs these concepts. If your work doesn't touch inventory or fulfillment at all, this specific process isn't necessary background.
Questions about inbound and outbound logistics
- Is this official SAP logistics training?
- No. This explains the inbound and outbound goods-movement concepts conceptually; it isn't official SAP training material or certification preparation.
- Does a goods receipt always exactly match the purchase order?
- Not necessarily — partial deliveries, over-shipments, and under-shipments are all real scenarios the system is built to represent, not exceptions that break the process.
- What actually changes inventory — the order or the delivery?
- The order (purchase order or sales order) represents a commitment; the actual goods receipt or goods issue posting is what changes recorded on-hand inventory. This distinction matters for anyone reading inventory reports.
- How does this connect to warehouse management specifically?
- Inbound and outbound logistics describe the receiving and shipping process generally; WM or EWM, both covered in this section, add the bin-level detail of exactly where within the warehouse those movements happen.