Business Central Implementation for Wholesale Distribution
Business Central Implementation for Wholesale Distribution: Start With Your Price File, Not Your Warehouse
The warehouse is not the hardest part of a Business Central implementation for a wholesale distributor. Your pricing is.
Most project plans give weeks to bin layouts and scanner hardware, then treat customer-specific prices, quantity breaks and rebates as a data-load task for the final month. That order is backwards. On wholesale projects, it is the single most common reason we see go-live dates move.
Consider the arithmetic. A wholesaler carrying 20,000 SKUs across 1,500 active accounts can hold a very large number of individual price points once contract prices, buying-group terms and promotions stack up. Each one feeds order entry, margin reporting and credit notes. Get the warehouse 80% right and pickers adapt within a week. Get pricing 80% right and sales desk staff start overriding prices on every few orders, gross margin reports stop meaning anything, and customers query their invoices.
Why commercial logic sinks more projects than logistics
Independent research describes the same pattern. Panorama Consulting Group's 2026 ERP Report found that more than a quarter of organisations exceeded their ERP project budgets, with additional technology needs cited as the leading cause. Panorama's commentary on the report notes that organisations "often discover fatal misfits late in the project," then reach for extra technology, scope expansion and custom builds.
In wholesale distribution, that late misfit is rarely a pick list. It is usually commercial logic:
- Contract prices agreed with buying groups or national accounts
- Cost-plus agreements that must move when a supplier changes list price
- Quantity breaks by case, layer or pallet
- Time-bound promotional pricing
- Supplier rebates and ship-and-debit claims
Standard Business Central covers much of this well. Microsoft's price list functionality lets you set prices and line discounts for a specific customer, a customer price group or a campaign. Lists sit in Draft until you activate them, and you can export them to Excel for bulk edits. Microsoft also documents how to record special sales prices and discounts for individual customers.
Supplier rebate accruals and claim-backs are different. They are a common gap in a standard deployment and usually need either an AppSource extension or a clearly owned finance process. Make that call in discovery, not in user acceptance testing.
Four decisions to lock before anyone configures a screen
Every wholesale rollout we deliver hinges on four design choices. Settle them early and the build phase gets shorter.
1. Your pricing hierarchy. When a customer qualifies for a contract price, a group price and a live promotion at the same time, which one wins? Business Central's default logic selects the best (lowest) valid price, and Microsoft documents how developers can extend that price calculation. Some distributors want a negotiated contract to hold even when a promotion is cheaper. That is a commercial policy decision, so put it in writing before build starts.
2. Units of measure. Wholesalers commonly buy in pallets, store in cases and sell in eaches. Every item needs correct conversion factors and rounding rules. Bad conversions produce stock that looks right in the system and wrong on the shelf.
3. The right warehouse level. Business Central scales from basic inventory picks up to full directed put-away and pick, as Microsoft sets out in its guide to managing warehouse activities. A single site with a handful of pickers rarely needs the top tier. A multi-zone distribution centre with bin replenishment and wave picking probably does. Over-configuring adds documents and clicks to every transaction, so pick the lowest level that supports your real process.
4. Drop shipments and special orders. Many wholesalers ship part of their volume direct from the supplier. Business Central links sales and purchase orders for both scenarios, which keeps margin visible on each line.
A phased rollout, and the test we never skip
Below is a typical shape for a single-entity, mid-sized wholesale distributor. Treat every duration as an estimate to validate against your own scope, data quality and integration count.
| Phase | Focus | Indicative duration | Exit criterion |
|---|---|---|---|
| Discovery and commercial design | Pricing hierarchy, units of measure, rebate approach, warehouse level | 3 to 5 weeks | Signed design for pricing and stock handling |
| Core build and data migration | Items, customers, vendors, price lists, opening stock | 6 to 10 weeks | Clean item master loaded to sandbox |
| Warehouse and integrations | Locations, bins, scanners, EDI, ecommerce feeds | 4 to 8 weeks | End-to-end order flow working in test |
| Parallel pricing test and UAT | Re-price historic invoices, user testing | 2 to 4 weeks | Pricing variance at an agreed tolerance |
| Go-live and hypercare | Cutover, open orders, stabilisation | 4 to 6 weeks | Order entry without manual price overrides |
The parallel pricing test deserves its own line. Take a sample of last quarter's invoices, re-run each order through Business Central, and compare the result line by line against what you actually charged. Every variance points to a missing rule, a bad conversion or an undocumented side deal. Finding them here costs a few days. Finding them after go-live costs credit notes and customer trust.
Data quality drives the rest. Duplicate SKUs, obsolete items and inconsistent supplier part numbers slow migration more than any configuration task. Assign a named owner on your side for item master cleansing in week one.
What to ask a Business Central partner before you sign
Partner demos tend to show a clean sales order flowing to a pick and an invoice. That proves very little about your business. Use these questions to separate partners who understand wholesale from those who simply know the software:
- "Show us our three hardest pricing scenarios in a sandbox." Send them real examples in advance. A capable partner will configure them before the statement of work is final.
- "How will you handle our supplier rebates?" Listen for a clear answer: native setup, a named extension, or a defined manual process with an owner.
- "Which warehouse level do you recommend, and why not the one above it?" A good answer is grounded in your pick volumes and site layout, not in licence tiers.
- "What is your cutover plan for open sales orders, back orders and open purchase orders?" Wholesalers never get a quiet day to switch systems.
- "Who cleanses the item master, and when?" Vague answers here predict a late go-live.
You can see how our team approaches this on our Dynamics 365 for distribution page, and in the delivery method described on our Business Central implementation service in Canada.
Frequently asked questions
How long does a Business Central implementation take for a wholesale distributor?
A single-entity, mid-sized wholesaler often lands between four and nine months from discovery to the end of hypercare. Integration count (EDI, ecommerce, carrier systems), data quality and pricing complexity move that range more than user numbers do. Treat any timeline as an estimate until discovery is complete.
Is Business Central enough for wholesale distribution, or do we need Dynamics 365 Finance & Operations?
Business Central fits most small and mid-sized wholesalers that run one or a few legal entities and standard warehouse processes. Finance & Operations becomes the better fit when you run many legal entities, high-volume multi-site distribution centres, or complex global trade requirements. Base the decision on your process map, not company size alone.
Can Business Central handle customer-specific and contract pricing?
Price lists support prices and discounts by customer, customer price group and campaign, with Draft and Active statuses for control. The design work is in deciding which rule wins when several apply, and in confirming how supplier rebates will be handled.
Do we need a separate WMS alongside Business Central?
Business Central's advanced warehousing, including directed put-away and pick, covers many wholesale operations. A third-party WMS or scanning extension becomes worth evaluating for very high pick volumes, complex wave or cluster picking, or heavy automation.
Book a pricing-first scoping session
Bring your three hardest pricing scenarios and a sample of last quarter's invoices. A Dynamics Square Business Central consultant will walk through how they would run in Business Central and flag where you would need an extension or a process change, before you commit to a scope.
Book a consultation with Dynamics Square via dynamicssquare.com/contact-us.