SAP Business One shipping is the native logistics workflow that manages outbound order fulfillment within the B1 ERP, covering shipping type configuration, delivery document creation, and carrier execution from sales order through invoicing.
Out of the box, SAP Business One supports shipping type configuration, delivery document creation, pick and pack processes, and drop shipping. For teams managing higher shipping volumes or multiple carriers, capabilities such as real-time rate shopping, label generation, and shipment tracking typically require an integrated solution.
This guide explains how SAP Business One shipping works, starting with native functionality and highlighting where integrations are typically added.
Key Takeaways:
Shipping types are the method definitions that attach to every outbound transaction in B1. They tell the system how a shipment is moving and feed into delivery documents, reporting, and any connected shipping integration.
Configuration path: Administration > Setup > Inventory > Shipping Types.
Each shipping type gets a name (Ground, Air, Freight, Next Day, and so on), a website field for tracking URLs, and an associated tracking number field. Once defined, shipping types appear as a selectable field on Sales Orders and Delivery Documents.
A few practical notes on setup:
Naming matters for reporting. Shipping type names appear in delivery reports and can be filtered in queries. Teams that ship across multiple modes benefit from names that map cleanly to actual carrier services rather than generic labels.
Tracking URL format. The website field accepts a tracking URL template. When a tracking number is entered on a delivery document, B1 can use that URL to generate a clickable tracking link in customer-facing documents.
One type per transaction. A single shipping type attaches to each delivery. Teams managing multi-leg shipments or split deliveries need to account for this at the document level.
Shipping types in SAP B1 are intentionally lightweight. They capture the intended method without enforcing carrier selection or live rate logic. That keeps the built-in setup simple and flexible, and it's the starting point for any connected shipping workflow.
The standard outbound shipping process in SAP Business One follows a defined document chain. Each document has a specific role, and skipping steps or working outside the chain creates reconciliation problems downstream.
Step 1: Sales Order. The process starts with a Sales Order, which captures the customer, items, quantities, pricing, and shipping details including the ship-to address and assigned shipping type. The Sales Order does not move inventory. It is a commitment, not a goods movement.
Step 2: Pick and Pack (optional). For warehouses using pick lists, B1 supports a pick and pack workflow before the Delivery Document is created. Pick lists generate from open Sales Orders and allow warehouse staff to confirm quantities before shipment.
Step 3: Delivery Document. When items are physically ready to ship, the Sales Order is copied into a Delivery Document. This is the step that formally moves goods out of inventory and records the corresponding accounting entries. The Delivery Document is where freight charges, package weight, and tracking numbers are recorded in the native B1 workflow.
Step 4: AR Invoice. After delivery, the Delivery Document is copied into an AR Invoice, which generates the customer billing record. Freight charges recorded on the Delivery Document carry forward into the invoice.
The copy function between documents is central to how B1 maintains document linkage. Manually re-entering data at each step introduces errors and breaks the audit trail. Well-configured B1 environments use the copy function consistently to keep the chain intact.
SAP Business One supports drop shipping through a warehouse configuration rather than a separate workflow. When an item on a Sales Order is assigned to a drop-ship warehouse, the system treats fulfillment as coming directly from the vendor to the end customer.
The setup: a warehouse is flagged as a drop-ship location in warehouse master data. When a Sales Order line routes to that warehouse, B1 can auto-generate a linked Purchase Order to the vendor. The vendor ships to the customer address on the Sales Order. Physical inventory is never touched, but the financials record both the customer sale and the vendor cost correctly.
For distributors managing vendor-direct fulfillment alongside warehouse-held stock, both models run within the same Sales Order without separate processes.
Inbound freight in SAP Business One is managed through the Purchase Order and Goods Receipt PO document chain. When a vendor ships goods, the Purchase Order is copied into a Goods Receipt PO, which formally records the inventory receipt and generates the corresponding accounting entries.
SAP B1 does not connect to carrier tracking for inbound shipments natively. Teams managing inbound visibility, knowing when a vendor shipment is in transit, where it is, and when it will arrive, typically rely on vendor communication or carrier portal lookups outside the system. For operations managing both inbound and outbound freight, a connected TMS that handles both directions provides a unified view without separate tools or manual tracking.
SAP B1 covers the document workflow and basic logistics fields well. Several execution-layer capabilities fall outside the native setup, and teams running meaningful shipping volume typically address these through a connected integration.
Live carrier rate comparison. SAP Business One does not connect to carrier rate APIs. Comparing rates across UPS, FedEx, regional parcel carriers, and LTL providers requires logging into carrier portals separately or maintaining manual rate tables. For teams processing high shipment volumes daily, this creates measurable processing overhead.
Carrier label generation. Shipping labels, bills of lading, and packing slips are not generated within SAP B1 natively. They are produced in carrier portals or dedicated shipping software, then reconciled back to the B1 delivery record manually.
Real-time tracking writeback. Tracking numbers and carrier status updates do not populate SAP B1 delivery documents automatically without an integration. Teams pulling tracking data from carrier websites and entering it manually into B1 are doing work that a connected system would eliminate.
Freight invoice audit. Validating carrier invoices against originally quoted rates, catching accessorial overcharges, and flagging duplicate billing requires manual comparison across documents. At scale, those discrepancies compound quickly.
International shipping documentation. SAP B1 does not generate customs documentation, commercial invoices, or harmonized tariff codes natively. For teams shipping cross-border, these documents are typically produced outside the system and reconciled back manually, or handled through a connected integration that generates them from the existing Delivery Document data.
The standard approach is a bi-directional TMS integration that sits alongside SAP B1 without replacing the native document workflow. Order and delivery data flows from B1 into the TMS for execution. Shipment details, tracking numbers, freight costs, and carrier data write back to the corresponding B1 delivery document automatically.
FreightPOP connects to SAP Business One as a full transportation management layer across the shipment lifecycle. Rate shopping, booking, label and BOL generation, and tracking writeback handle the outbound execution side. Freight audit runs against every carrier invoice, matching billed charges to quoted rates and flagging accessorial overcharges and billing discrepancies before payment. Visibility tools surface shipment status across all modes and carriers in a single view, without logging into carrier portals separately.
For SAP B1 teams managing inbound freight, FreightPOP handles purchase order-based shipments alongside outbound, giving operations a unified view of both directions rather than separate tools for each.
The SAP B1 document chain stays intact throughout. Core ERP processes, order management, inventory, and financials remain in Business One. FreightPOP extends what B1 does well rather than replacing it, adding the execution and audit layer on top of the existing workflow.
FreightPOP's SAP Business One integration deploys in weeks without custom development. Teams using FreightPOP report up to 30% reductions in freight costs, 95% faster shipment processing, and 40% improvement in on-time deliveries.
Learn more about FreightPOP SAP Business One integration , or review how a global automotive manufacturer runs the integration in production in the SAP customer success story.
What are shipping types in SAP Business One? Shipping types are method definitions configured under Administration > Setup > Inventory > Shipping Types. They define how a shipment moves (Ground, Air, Freight, and so on) and attach to Sales Orders and Delivery Documents to capture the intended carrier method for each transaction.
How does a Delivery Document work in SAP Business One? A Delivery Document is created by copying a Sales Order when items are ready to ship. It formally records the goods movement, reduces inventory, and generates the corresponding accounting entries. Freight charges, package details, and tracking numbers are recorded on the Delivery Document in the native B1 workflow.
Does SAP Business One support multi-carrier rate shopping? Not natively. SAP B1 does not connect to live carrier rate APIs. Teams that need to compare rates across parcel carriers, LTL providers, and regional carriers integrate B1 with a TMS that provides real-time rate shopping from within the existing workflow.
Can SAP Business One generate shipping labels? SAP B1 does not generate carrier-compliant shipping labels natively. Label generation is handled through a connected shipping integration that pulls Delivery Document data from B1 to produce labels, BOLs, and packing slips without manual re-entry.
How do tracking numbers get recorded in SAP Business One? In the native B1 workflow, tracking numbers are entered manually on the Delivery Document. With a connected TMS integration, tracking numbers write back automatically from the carrier to the B1 delivery record in real time as soon as the shipment is booked.
How long does it take to integrate a TMS with SAP Business One? Timeline depends on the TMS provider and the complexity of the B1 environment. FreightPOP's SAP Business One integration deploys in weeks using a standard bi-directional connector, without custom development.
How does SAP Business One shipping affect freight costs? Native SAP B1 shipping does not include tools for comparing or optimizing carrier rates, so freight costs are largely determined by manual carrier selection. SAP B1 shipping connected to a TMS enables real-time rate shopping across parcel, LTL, and FTL carriers, which is where most teams see measurable freight cost reductions. FreightPOP customers report up to 30% reductions in freight costs through multi-carrier rate shopping.
SAP Business One provides a well-structured document chain for outbound shipping. Teams that configure shipping types correctly and use the Sales Order to Delivery Document workflow consistently get accurate inventory and financial records without manual workarounds. When carrier execution requirements grow beyond what the native setup handles, a connected TMS extends that foundation without disrupting the B1 workflow that already works.
For SAP Business One teams evaluating connected shipping, explore the FreightPOP SAP integration.