This page explains Shipping Conditions for consultants, solution architects, and prototype builders working through FIT 4 SAP. In short, Shipping Conditions describe the customer’s delivery expectations so SAP can choose the right path for moving goods out of the building. It matters because delivery behaviour in SAP does not happen magically; it is calculated. The right Shipping Condition ensures the system picks the correct shipping point and forms deliveries that match real-world promises. Use it when customers expect specific handling or timing, and avoid it when the business pretends all deliveries behave the same.

</aside>

A reasoning page explaining why Shipping Conditions exist and why they matter for In-House Secure’s logistics flow.

The Principle

Shipping Conditions are not about trucks or warehouses. They are about promises. The moment a customer says “deliver it fast” or “collect at 4pm,” you need a clean way to encode that expectation into SAP so the system does not make up its own rules. Shipping Conditions turn subjective human expectations into predictable system behaviour.

Jargon explained (The WHAT section)

Shipping Condition

A small classification that tells SAP what kind of delivery service the customer expects. Examples: Standard, Express, Collect, Same Day.

Shipping Point Determination

SAP’s internal detective. It takes three clues: Shipping Condition, Loading Group, Plant. Together they tell SAP which physical area ships the goods.

Delivery Creation Behaviour

How SAP groups order items into outbound deliveries. Shipping Conditions influence timing and grouping.

WHEN it matters

Shipping Conditions become critical the moment a sales order is created. Because SAP needs this information early, it is stored on the Customer Master and can be overridden at the Sales Order level.

When a sales order line is saved, SAP immediately evaluates:

• The plant supplying the product

• The product’s loading group

• The Shipping Condition