Drop shipments and special orders in Business Central
How Business Central links sales orders to purchase orders for drop-ship and special-order fulfilment — the requisition worksheet, the linkage, and the gotchas.
For distributors and resellers, fulfilling customer orders without holding inventory is a real cost-of-doing-business advantage. Business Central supports two related patterns natively: drop shipments and special orders.
Drop shipments. A drop shipment is a sales transaction where the goods never enter the seller's warehouse. The vendor ships directly to the customer. From the seller's perspective: a sales order is placed, a corresponding purchase order is placed with the vendor, the vendor ships, the seller invoices the customer, and the vendor invoices the seller. No item ledger inbound entries for the seller; no warehouse handling.
Special orders. A special order is similar — a sales order driving a purchase order — but the goods do enter the seller's warehouse first before being shipped to the customer. The seller takes possession briefly. Used for items that must be inspected, repackaged, kitted, or labelled before shipping.
The mechanism — drop shipment.
- On a sales order line, the user marks Drop Shipment. The line stops behaving like a normal sales line — it doesn't try to ship from inventory.
- The user runs the Requisition Worksheet with the drop-shipment view, which lists sales lines marked for drop shipment.
- The user assigns a vendor and runs Carry Out Action Message, which creates a purchase order linked to the sales line.
- On the purchase order, the Drop Shipment field is set, and the Ship-to address auto-populates from the sales order's ship-to.
- When the vendor confirms shipment, the user posts the purchase receipt — which simultaneously posts the sales shipment (no inventory entries, just the matching ledger movements).
- Both invoices post against the related documents normally.
The mechanism — special order.
- On a sales order line, the user runs Special Order from the Functions menu.
- The system creates a purchase order linked to the sales line, with the seller's warehouse as ship-to.
- The purchase order receives normally, into stock.
- When the goods are ready, the sales shipment is posted normally — but the link to the purchase order ensures the inbound and outbound transactions are reconciled cost-accurately.
Why the linkage matters. Without the link, you could just create a purchase order manually for each sales order and it would kind of work. The linkage adds:
- Cost accuracy. The purchase cost flows to the sales line's COGS automatically when posted.
- Reservation. The incoming purchase is reserved for the sales line, so warehouse staff can't accidentally allocate it elsewhere.
- Visibility. Both documents show the linked counterpart; status, dates, and quantities reconcile.
- Cancellation safety. If the sales order is cancelled, the purchase order is flagged for review.
Pitfalls.
- Partial deliveries require careful matching — the sales and purchase quantities must align or the linkage gets confused.
- Currency mismatches between sales (customer currency) and purchase (vendor currency) need FX handling; supported but adds reconciliation effort.
- Returns of drop-shipped goods are awkward — the goods may or may not come back to the seller's warehouse. Handle by case.
Reporting. A standard Drop Shipment Status report shows open sales-purchase pairs; useful in customer service for "where's my order" responses.
Related guides
- Accessibility in Dynamics 365 appsHow Dynamics 365 supports accessibility — keyboard navigation, screen readers, colour contrast, ARIA, and the requirements for compliance with WCAG, Section 508, and EN 301 549.
- Data protection and compliance for Dynamics 365How to address data protection and compliance requirements for Dynamics 365 — GDPR, HIPAA, SOX, industry regulations, and the operational practices.
- Dynamics 365 and Azure OpenAIHow Azure OpenAI powers AI features in Dynamics 365 — under-the-hood model usage, custom AI scenarios, and the patterns for integrating LLMs with Dynamics.
- Dynamics 365 and Conditional AccessHow Conditional Access protects Dynamics 365 — policy patterns, MFA, device compliance, location-based controls, and the Zero Trust patterns.
- Dynamics 365 and Microsoft DefenderHow Microsoft Defender protects Dynamics 365 environments — Defender for Cloud, Defender for Cloud Apps, Defender for Identity, and threat detection patterns.