A customer wants an item the warehouse doesn't have on hand right now. The rep who just closed the deal is staring at a sales order screen with no obvious next step, so they do what feels safest: call someone in operations, explain the situation over Slack, and wait. Twenty minutes later, someone tells them about a feature called drop shipment that would have solved this in the order itself, if anyone had shown them where it was.
This is a common, avoidable pattern. Business Central has native functionality built specifically for the two most common reasons a sales order gets stuck — an item not normally stocked, and a stocked item needing special handling — and a lot of sales teams never get properly trained on either one.
Two Problems, Two Different Native Solutions
Drop Shipment: When You Never Touch the Item
A drop shipment handles the scenario where a business doesn't regularly stock an item a customer wants — the vendor ships the item directly to the customer, and the business never physically receives it. In Business Central, this is set up by selecting the Drop Shipment checkbox on the sales order line, or by using a purchasing code that has drop shipment enabled by default, which links the sales order to a corresponding purchase order automatically.
The real value here is the linkage itself: when the vendor ships and the sales order is posted as shipped, the corresponding purchase order is automatically updated as received — no separate manual reconciliation required to keep the two documents in sync. Most sales teams either don't know this checkbox exists or were never shown when to use it, so the same scenario gets handled manually every time it comes up.
Special Order: When the Item Comes Through Your Warehouse First
A special order is similar in structure but different in flow — items still get linked between a sales order and a purchase order, but they're received into the warehouse before being shipped to the customer, rather than going directly from vendor to customer. This fits situations where a customer wants a non-stock item but the business still wants to inspect or process it before it goes out the door.
Both drop shipments and special orders can be initiated manually or generated through the Requisition Worksheet, using the Get Sales Order function to pull in the relevant order details automatically rather than re-keying them onto a new purchase order by hand.
The Setup Detail That Trips Up Drop Shipments Specifically
A specific, easy-to-miss configuration issue: if Location Mandatory is enabled on the Inventory Setup page, Business Central will require a location code on drop shipment documents even though the location is functionally irrelevant — the item never touches your warehouse. This produces a confusing posting error the first time someone tries it, with no obvious explanation for why a location field matters for an item that was never received. The practical fix isn't disabling Location Mandatory system-wide, which affects every other transaction — it's simply entering a location code on the drop shipment order even though it doesn't reflect anything physically meaningful, so the transaction posts cleanly.
Why This Friction Usually Isn't a Software Problem
Neither drop shipment nor special order functionality is complicated once it's understood — the friction almost always comes from sales staff never being trained on when to use each one, not from the functionality itself being hard to use. A sales team that's never been shown the difference between the two will default to manual workarounds and cross-department Slack messages every single time a non-stock item comes up, even though the system has a built-in answer.
This is worth treating as a training gap specifically, not a configuration gap. The checkboxes and purchasing codes already exist in most Business Central environments — they're just invisible to a sales rep who's never had someone point them out during onboarding.
What Smooth Sales Order Processing Actually Looks Like
A well-functioning sales team knows, without asking, whether a specific customer request calls for a standard stocked order, a drop shipment, or a special order — and can select the right option on the sales order line itself instead of escalating to another department. That's not an advanced configuration outcome. It's a training outcome, built on functionality that's usually already sitting in the system unused.
Where to Start
If your sales team routinely escalates non-stock item requests to operations rather than handling them directly on the order, it's worth checking two things: whether drop shipment and special order purchasing codes are actually configured, and whether your sales staff have ever been walked through when to use each one. Often the functionality is already there — it's the training that's missing.