- Loading drop-ship products as Inventory items makes Business Central try to manage stock that doesn't exist, which triggered a cleanup that cloned each product into dash-N and Z-prefixed copies, three records per product.
- Once an item number has been used on a posted transaction, Business Central won't let you delete it; you can only block it, so duplicates linger and invite the wrong pick.
- The correct setup is Non-inventory items plus the native drop-ship workflow, where a sales order auto-generates the vendor PO, the vendor ships direct, and inventory is never touched.
- The original dash-suffix fix shows the difference between a technical consultant adding records and a functional consultant making the right setup decision behind the accounting.
Back in April, the team at a build-to-order training-equipment company showed us a Business Central setup with three copies of nearly every product. The story of how they got there is a cautionary tale for anyone who drop-ships, meaning you sell goods that ship directly from your manufacturer to your customer and never sit on your shelf.
How one wrong setting snowballed
This company holds essentially no inventory. Everything ships direct from the manufacturer. But when they were first implemented, every product was loaded into Business Central as an Inventory item, the type meant for things you actually stock and count.
That mismatch caused problems right away, because the system kept trying to manage stock that didn't exist. So someone "fixed" it by cloning each product into a second version with a dash-N suffix, set as a Non-inventory item. Later, another round of cleanup created Z-prefixed versions. The result was three records for the same physical product, and staff guessing which one to use on any given order.
Here's the trap that makes this so painful: once an item number has been used on a posted transaction, Business Central won't let you delete it. You can block it from future use, but it lingers in the list forever, inviting someone to grab the wrong one. Cleanup gets harder, not easier, the longer it runs.
What should have happened
For a drop-ship business, the answer was simple and built in:
- Set the items as Non-inventory (or use proper drop-shipment handling) from the start, because you never own the goods.
- Use Business Central's native drop-ship workflow, where a sales order automatically generates the purchase order to your vendor, the vendor ships straight to the customer, and the cost flows against that order. Inventory is never touched, because there is none.
Done right, there's one item number per product, one clean flow, and no monthly archaeology to figure out which clone to use.
This is a good example of the difference between a functional consultant and a technical one. The original fix (spawn a new product record with a dash) was a coder solving a configuration problem with more records. The real answer was a setup decision, made by someone who understood the accounting behind drop-shipping. You want the right kind of help at the right moment.
The takeaway
If you drop-ship, the most important decision in your item master happens before you import a single product: which items are truly stocked, and which never touch your warehouse. Get that line right and Business Central handles the rest cleanly. Get it wrong, and you spend the next two years deleting nothing and second-guessing every order.
If you're living with a messy item list, or you're about to migrate one into Business Central and want to avoid carrying the mess across, we're glad to take a look and map the clean version with you. Let's talk it through.