Drop-ship orders: linking the customer PO to the supplier PO without retyping
NetSuite, Business Central, Acumatica and Sage 100 can all link a drop-ship sales order to a supplier PO. The retyping lives around that link: reading the customer's PO, the supplier's confirmation, the tracking number and the customer update. Here's how each one handles it, and what to automate.

In brief
Turn on your ERP's drop-ship feature first. NetSuite, Business Central, Acumatica and Sage 100 can all create the supplier PO from the sales order and keep the two linked, with the customer's address as the ship-to. That link isn't where most of the typing happens. It happens around it: keying the customer's PO into a sales order, copying the supplier's confirmation and tracking number back, and telling the customer. Automate those reading and copying steps. Keep a person on price changes, address changes and substitutes.
- NetSuite, Business Central, Acumatica and Sage 100 can all create the supplier PO from the sales order and put the customer's address on it. Use that first.
- The retyping lives around the link: the customer's PO, the supplier's confirmation, the tracking number and the customer update.
- Copying data out of documents is where errors pile up: 6.57% of fields in one clinical research review, vs. 0.29% when typing from a form.
- Automate the reading and comparing. Keep a person on price differences, substitutes and any ship-to address change.
- At low volume, the ERP's built-in feature is enough.
Where the typing actually happens on a drop-ship order
A drop-ship order is one your supplier ships straight to your customer. You never touch the goods. On paper that sounds easy. In the office it often means the same order gets typed four or five times:
- The customer's PO arrives by email or PDF. Someone keys it into a sales order.
- Someone creates a PO to the supplier and types the customer's ship-to address on it.
- The supplier sends back a confirmation with a ship date, and sometimes a new price. Someone copies that into the ERP or a spreadsheet.
- The supplier ships and sends a tracking number. Someone copies it to the order and emails the customer.
- The supplier's invoice comes in. Someone checks it against the PO with no receiving slip from your own dock to lean on.
Each copy is a chance for a mistake. The best data we know of comes from clinical research, not order desks, but the pattern carries over. A review of 93 studies by Garza and colleagues found a pooled error rate of 6.57% of fields when people read records and copied the data out. Typing from a form built for data entry had a pooled error rate of 0.29%.
Copying from a document is where errors pile up
Pooled error rate, share of fields. Clinical research data entry, 93 papers published 1978 to 2008.
Source: Garza et al., systematic review and meta-analysis (PMC). Not order-entry data; use it as a sign of where errors happen, not as your rate.
A customer's PO and a supplier's confirmation are both "records" in that sense. They come in whatever layout the other company picked. That's the copying that hurts, and on a drop-ship order you do it at both ends.
What your ERP already links for you
Start here, because many teams build spreadsheets for a link the ERP already makes. The four systems below all tie the supplier PO to the sales order and put the customer's address on it. They differ in how the PO gets created and what counts as "shipped."
Drop-ship links in four ERPs, from each vendor's own help pages
| ERP | How the supplier PO gets made | What closes it out |
|---|---|---|
| NetSuite | Approving a sales order with a drop-ship item creates a PO to the item's preferred vendor, with the customer's ship-to address | With Advanced Shipping and Receiving, "Mark Shipped" on the PO fulfills the sales order |
| Business Central | "Create Purchase Orders" from a sales order with lines marked Drop Shipment, or "Get Sales Order" from the PO | Posting the sales shipment posts the linked purchase receipt |
| Acumatica | Marking lines "Drop-Ship" creates purchase requests; you turn them into POs on the Create Purchase Orders form | Releasing the purchase receipt completes the PO and the sales order |
| Sage 100 | Purchase Order Entry with order type Drop Ship and the sales order number, which fills in the customer's address | Entering the vendor invoice records delivery to the customer, not a receipt into stock |
Sources: Oracle NetSuite help, Microsoft Learn, MYOB Acumatica help, Sage 100 help (2016 edition). Checked Nov. 8, 2026.
NetSuite
You mark an item as a drop-ship item and give it a preferred vendor. Oracle's help says that when the sales order is approved, NetSuite generates a PO for that vendor showing the customer's shipping address. You can also set a single line to drop ship in the Create PO column, and that column then shows the PO number. Two details trip people up. When you drop ship from an order that is already approved, the PO gets made for one vendor at a time. And if you receive the PO on the Receive Purchase Order page instead of using Mark Shipped, the sales order is not updated, so someone has to fulfill it by hand. Oracle also warns to use the same unit of measure on both orders, or rounding errors can creep in.
Business Central
You tick Drop Shipment on the sales line. Microsoft notes that this checkbox isn't on the lines by default, so you may have to personalize the page to see it. Then "Create Purchase Orders" builds the PO, or a requisition worksheet builds POs for every open drop shipment at once. When the supplier sends a tracking number, Microsoft's suggestion is to add it as a comment line on the PO. That's a manual step. Posting the sales shipment posts the purchase receipt for you.
Acumatica
You check Mark for PO and pick Drop-Ship as the PO Source. The help guide (MYOB's edition of Acumatica's documentation) says this creates purchase requests, which become POs that carry the sales order number. A drop-ship PO can link to only one sales order. So you can't roll three customers' orders to the same supplier into one PO. You release the purchase receipt once you've confirmed the customer got the goods.
Sage 100
In Purchase Order Entry, you pick order type Drop Ship and enter the sales order number. Sage fills in the customer as the ship-to and assigns the PO number back to the sales order line. An option controls whether the PO pulls in only lines for that vendor or every drop-ship line. This is Sage's 2016 help page; check your version's help, since screens move.
If your team types the customer's address onto supplier POs today, fix that first. It's free, and it removes one of the riskiest copies on the list.
The ERP links the two orders. Nobody links the emails.
What the ERP doesn't do
All four systems link their own sales order to their own PO. None of them reads the outside documents for you. The gaps are the same everywhere:
- The customer's PO. It still has to become a sales order. Their part numbers have to match yours. If they don't, someone looks them up. We wrote about automating email and PDF orders separately.
- The supplier's confirmation. It arrives as an email or PDF with a ship date and maybe a changed price or quantity. Nothing compares it to your PO unless a person does.
- Tracking. The number lands in someone's inbox. Getting it onto the order and to the customer is a copy-and-paste job.
- Changes. If the customer revises their PO after you've ordered from the supplier, you now have two orders to fix. See automating revised POs and change orders.
- The invoice check. There's no receiving slip from your own dock. Your proof of shipment is the supplier's word, a tracking number or the customer's confirmation. That makes the invoice match softer than on stock orders.
What to automate and what to keep with a person
A sensible split for drop-ship orders
| Step | Automate | Keep with a person |
|---|---|---|
| Customer PO to sales order | Read the PO, match part numbers, draft the order with lines flagged drop ship | Approve the draft; decide on parts that don't match |
| Supplier PO | Let the ERP create it; send it to the supplier | Pick a different supplier or a substitute part |
| Supplier confirmation | Read it and compare price, quantity and date to the PO | Accept or push back on any difference |
| Ship-to address | Copy it from the customer's order | Any change after the order is placed. Confirm it by phone with someone you know |
| Tracking and customer update | Pull the tracking number, update the order, draft the customer email | Late or partial shipments: what to tell the customer |
| Supplier invoice | Match it to the PO and the shipment record | Anything that doesn't match |
The address line deserves a second look. A drop-ship order sends goods to an address someone else gave you, and the goods never pass through your hands. A request to change that address after the order is placed is the moment to slow down. Treat it the way a careful AP team treats a request to change a vendor's bank details: call back on a number you already have.
The confirmation check is where automation earns the most. A person scanning a PDF for a changed price is easy to fool when they're busy. Software that compares every line and flags only the differences gives that person a short list instead of a stack.
Where the other side has a point
If you do a few drop ships a week, the ERP is enough. Turn on the feature, set preferred vendors, and stop there. The reading and comparing steps only add up when volume does.
Some suppliers already solve the supplier side. Large suppliers may send confirmations and ship notices by EDI or through a portal. If your biggest drop-ship vendors do, the confirmation and tracking steps may already be handled for them. The gap is the long tail of suppliers who send PDFs.
An off-the-shelf add-on may cover it. Check your ERP's add-on marketplace for drop-ship tools. If one fits how your suppliers actually send documents, buying it is often simpler than building. We compared buying vs. building PO automation in more detail.
Not every step should be automated. Choosing a substitute part or deciding what to tell an upset customer is judgment. Keep a person there even after the rest runs on its own.
A short plan
- Count them. Pull last month's drop-ship orders and count how many touches each one took, from customer PO to paid invoice.
- Use the built-in link. Make sure the supplier PO comes from the sales order, not from a blank screen.
- Set preferred vendors. NetSuite's automatic PO depends on them, and Business Central suggests the vendor from the item or stockkeeping unit card.
- Pick the worst copy step. For most desks it's the supplier confirmation or the customer PO. Automate that one first, with a person approving.
- Measure minutes per order before and after. Here's how to measure it.
Common questions
What is a drop-ship order?
It's an order your supplier ships straight to your customer. You sell the goods and bill the customer, but the goods never go through your warehouse.
Can NetSuite create a drop-ship PO automatically?
Yes. Oracle's help says that when a sales order with a drop-ship item is approved, NetSuite creates a PO to the item's preferred vendor with the customer's shipping address. The item needs to be marked as drop ship with a preferred vendor.
How do I link a sales order to a purchase order for drop shipment in Business Central?
Tick Drop Shipment on the sales line, then use Create Purchase Orders on the sales order. Or, on the PO, set Ship-to to Customer Address and use Drop Shipments, then Get Sales Order. Microsoft notes you may need to personalize the page to see the checkbox.
Can one Acumatica drop-ship PO cover several sales orders?
No. Acumatica's help says a drop-ship purchase order can be linked to only one sales order.
How do you confirm a drop-ship order shipped if it never reaches your dock?
You rely on the supplier's shipment notice, a tracking number or the customer's confirmation. Each ERP then has its own step to close the order, like Mark Shipped in NetSuite or releasing the purchase receipt in Acumatica.
What should stay manual on drop-ship orders?
Price or quantity differences on the supplier's confirmation, substitute parts, and any change to the ship-to address after the order is placed. Confirm address changes by calling a number you already have.
Is it worth automating drop-ship orders?
Only if you have the volume. If you do a few a week, the ERP's built-in link is enough. If you do many, with suppliers who send PDF confirmations, the reading and comparing steps are where the time goes.
Sources
- Oracle NetSuite help, Drop Shipment and Special Order Purchases, checked Nov. 8, 2026
- Oracle NetSuite help, Selling a Drop Ship Item, checked Nov. 8, 2026
- Microsoft Learn, Business Central: Make drop shipments, updated April 1, 2026
- MYOB Acumatica help, Sales with Drop Shipping: General Information, checked Nov. 8, 2026
- Sage 100 help (2016), Enter Drop-Ship Orders
- Garza et al., Error Rates of Data Processing Methods in Clinical Research: A Systematic Review and Meta-Analysis (PMC)
Orders from customers who won't do EDI: how to automate email and PDF orders
Automating revised POs and change orders
Three-way match for manufacturers: automating invoice matching