Dynamics 365 Business Central for Wholesale: A Practical UK Guide
Explore Business Central for wholesale, including stock, trade pricing, purchasing, fulfilment, returns and finance, with practical evaluation questions.
What is the quick answer?
Business Central can bring wholesale purchasing, inventory, sales and financial processes into one ERP system. Its suitability depends on your trading rules, warehouse design, data quality and integrations. Evaluate a complete order-to-cash and purchase-to-pay cycle using your own products, prices and exceptions. Identify where standard configuration is sufficient and where a specialist application or integration is needed before agreeing scope.
Why do wholesalers look beyond accounting software?
Wholesale businesses often reach an awkward stage where the accounts remain manageable but the operating information does not. Customer service checks a stock spreadsheet, purchasing maintains its own expected delivery dates and finance discovers margin differences later. The issue is the time needed to establish what is true before somebody can make a reliable commitment.
An ERP project should connect those decisions. Start with the questions employees repeatedly ask: can we promise this quantity, which supplier order covers it, what price applies and has the customer exceeded an agreed limit? Record how staff answer each question today and where they must leave their normal system to investigate.
Our Xero versus Business Central guide explains the broader move from accounting software to ERP. For a wholesaler, the justification should be specific: fewer unexplained stock differences, dependable order handling or clearer responsibility for exceptions. Buying a larger application without changing the underlying working arrangements may simply reproduce the same uncertainty with more screens.
↑ Back to contentsWhat can Business Central bring together for a wholesaler?
Business Central provides connected business management functions rather than a separate stock spreadsheet beside the accounts. Microsoft’s inventory management guidance describes inventory records changing through purchase, sales and transfer activity, with item costs connected to financial entries. The exact result depends on configuration and the transactions your team records.
For evaluation, follow one product from supplier order to customer invoice. Ask where expected quantity becomes received quantity, when it becomes available for sale and how a late cost changes the financial picture. Those points reveal whether the proposed process supports how your business actually trades.
Our Business Central supply chain services cover this connected operational scope. Use the discovery process to agree what belongs in the first phase, including purchasing, sales, locations and reporting. A clear first-phase boundary is more useful than a promise to automate every wholesale activity immediately.
↑ Back to contentsHow should we define products, pack sizes and units of measure?
Product information deserves early attention because wholesale transactions depend on consistent quantities. A supplier may quote by carton, the warehouse may count individual units and a customer may order by case. Document the relationships, including any product-specific variation, before loading data. An apparently small unit error can affect availability, pricing, purchasing and margin at the same time.
Prepare a sample covering the difficult products, not just the most familiar ones. Include alternate supplier references, customer-specific references and products sold in several pack sizes where relevant. Decide which identifier staff should use at each stage and how they recognise an equivalent or replacement item.
Assign an owner to the item creation process. New products should have agreed purchasing, sales, costing and handling information before routine use. Avoid treating data entry as a clerical task with no operational consequence. A controlled process for maintaining item information protects the reliability of every later report and makes training easier for new purchasing and customer service staff.
↑ Back to contentsHow do we evaluate trade pricing without creating a maintenance burden?
Write down the commercial rules that determine a customer’s price. Separate agreed contract prices from general discount policies, temporary promotions and discretionary exceptions. Ask who may approve a change, when it takes effect and how staff know which version applies. The goal is a price that can be explained, rather than a collection of discounts inherited from old spreadsheets.
Use a realistic demonstration pack: an established customer, a new customer, a quantity break, a negotiated exception and a return after a price change. Have the sales team explain the expected result before the supplier demonstrates the application. Record any gap between the required trading rule and the proposed configuration.
Consider the effort needed to maintain the design after implementation. A clever structure that only one consultant understands can become expensive to operate. Our Business Central consultants can help translate trading requirements into evaluation questions. The business should retain ownership of the commercial policy and approve any simplification before it affects live orders.
↑ Back to contentsWhat should order entry and credit control look like?
Order entry should help staff make a sound promise using approved information. Define the checks required for customer identity, delivery address, price, availability and credit. Decide which conditions block progress and which create a visible exception for authorised review. Without this agreement, employees may each invent a different response to the same situation.
Test an order that changes after entry. A customer might add a line, request a different address or split a delivery. Ask what needs to be reviewed again and whether an earlier approval still applies. A successful initial order does not demonstrate that the process remains controlled after a commercially significant amendment.
Credit control and fulfilment need a shared understanding of priority. Establish who can release an exception, the evidence required and the record kept. Our Business Central finance implementation services are relevant to connecting those decisions with receivables and cash processes. Agree the business rule first, then make the system behaviour and staff instructions consistent with it.
↑ Back to contentsHow should warehouses decide between simple and more structured processes?
Choose a warehouse process around the work being performed. Consider receiving volume, the number of people handling an order, the need for separate checking and the consequences of picking the wrong product. A smaller building can still need strong controls, while a straightforward operation may not benefit from unnecessary transaction steps.
Microsoft’s warehouse design overview explains that Business Central supports different levels of warehousing complexity. Basic and advanced approaches use different documents and ways of organising work. Agree the intended location setup with the implementation team instead of assuming a single warehouse workflow applies everywhere.
Observe the proposed process with warehouse employees present. Ask them to receive an unfamiliar delivery, find stock, handle a short pick and record a damaged item. Where scanning or specialist warehouse software is proposed, identify the product, devices, licensing and support boundaries separately. Check that the demonstration covers how mistakes are corrected as well as how normal work is completed.
↑ Back to contentsHow can purchasing respond to demand without creating excess stock?
Purchasing needs a consistent view of customer demand, existing commitments and supplier information. Begin by reviewing how replenishment decisions are made today. Some products may be bought routinely, others against particular orders and others only when a buyer judges that a supply risk justifies additional stock. Those distinctions should be deliberate.
Review the inputs that influence purchasing: realistic lead times, minimum order quantities, ordering multiples and the treatment of overdue supplier orders. Assign an owner to each assumption. If the business has repeatedly accepted a supplier’s optimistic date, importing that date into a new system will not make the resulting plan dependable.
During testing, ask why each suggested purchase exists and what happens if the buyer changes it. A useful process gives staff enough context to accept a proposal or explain an override. Monitor the reasons for overrides after launch. Repeated adjustments may show that a policy needs refinement, an input is wrong or a commercial constraint was omitted from discovery.
↑ Back to contentsWhat should we do about partial deliveries, backorders and substitutions?
These exceptions deserve their own design rather than a short note at the end of training. Decide when the business offers a partial shipment, holds an order for completion or proposes another item. Consider customer instructions, carriage cost and the financial effect of changing the order. Different customer agreements may require different responses.
Use a scenario in which the expected receipt is delayed after the customer has already received a delivery promise. Ask who identifies the problem, who contacts the customer and how the revised commitment reaches the warehouse. An automated notification is useful only when someone knows what decision follows it.
Where a wholesaler also assembles or produces goods, investigate the operational boundary carefully. Our Business Central manufacturing services are relevant when production becomes part of the requirement. Do not assume that a substitute product, a kit assembled from components and a manufactured item are interchangeable concepts. Document the required business treatment and prove it through the proposed configuration.
↑ Back to contentsHow should we connect ecommerce, EDI and customer portals?
Decide which information customers may rely on and how quickly changes need to reach each channel. Stock visibility, negotiated prices, order status and customer balances may have different owners and update requirements. Avoid promising a single live view until the proposed connection has been tested against those expectations.
Test changes in both directions where an integration permits them. Include an order amendment, a duplicate message, a cancellation and a rejected transaction. Confirm which team investigates a failure and how staff can see that work is waiting. A connector should not create an invisible queue that only a developer knows how to inspect.
Our Business Central retail ERP services provide context for organisations with trade and consumer channels. Keep each channel’s commercial rules clear, especially when shared stock serves different customers. The solution design should describe which system owns the order, how corrections are authorised and how the business reconciles the channel records with the ERP.
↑ Back to contentsHow do we handle landed costs and understand the margin?
Define the margin you need to measure before choosing a report. The commercial view may need to account for purchase cost, freight, handling or other costs your finance policy treats as relevant. Agree the allocation approach with finance, including what staff should expect when a cost becomes known after goods have already been sold.
Use a worked example during design. Start with a product receipt, sell part of the quantity, then introduce a late supplier charge. Ask the implementation team to explain the resulting operational and financial records. The important test is whether the responsible people can reconcile the result and understand when a reported margin is provisional.
Keep operational performance and accounting policy connected without confusing them. A salesperson may need an immediate estimate while finance needs the final supported valuation. Label the measures clearly and give users a way to investigate a difference. Do not present a dashboard as authoritative merely because it is visually polished or refreshes frequently.
↑ Back to contentsHow should returns and damaged stock be controlled?
A return can involve several decisions: whether the customer is entitled to credit, whether the goods may be resold and whether the supplier should be involved. Define those decisions separately. Goods arriving at the loading bay should not automatically become saleable stock or trigger a financial outcome that nobody has approved.
Walk through a return without an original reference and a return that cannot go back into normal inventory. Decide who identifies the item, records its condition and authorises the next step. Give customer service a clear way to explain the status without needing a separate telephone investigation for every case.
Include the financial completion of the process in testing. A physical movement, a customer credit and a supplier claim may finish at different times. Make outstanding work visible and assign it. This reduces the risk that an operationally resolved return remains financially incomplete, or that a credit is issued while goods are still being handled incorrectly.
↑ Back to contentsHow should multiple depots and project customers affect the design?
Each depot needs clear ownership of physical stock and shared rules for the information used by other locations. Test a transfer from both ends, including a shortage or delay while goods are in transit. Customer service should understand which stock can actually fulfil an order and who is responsible for confirming its availability.
Do not assume every site must operate identically. Differences may be justified by layout, product handling or the customers served. Record approved variations and the reason for them. A common standard should make cross-site decisions easier while preserving the controls that a particular operation needs.
For wholesalers supplying construction or other project customers, order references, staged deliveries and cost attribution can add requirements. Our Business Central ERP for construction page can help frame those discussions. Demonstrate the complete customer arrangement rather than assuming a conventional stock order will satisfy project-specific administration and evidence needs.
↑ Back to contentsWhat data and processes should we prepare before implementation?
Prepare customers, suppliers, items, stock quantities and open orders through named business owners. Agree what to retain, correct, combine or archive. A migration team can move records, but it cannot safely decide which of two conflicting customer terms reflects the current commercial agreement without business input.
Rehearse migration using useful acceptance checks. Compare quantities by location, investigate unexpected values and prove that opening orders can be completed. Keep a record of exceptions and their resolution. Successful import messages are not a substitute for a purchasing or warehouse user confirming that the migrated records support actual work.
If your existing system is NAV, our NAV 2013 to Business Central migration guide provides additional context for legacy assessment. Review old customisations by business purpose. Preserve necessary controls while challenging workarounds that no longer serve a clear need. This prevents a modernisation project from reproducing years of accidental process design.
↑ Back to contentsHow should we compare Business Central with other wholesale ERPs?
Use the same scenarios for each product and insist on evidence for the important exceptions. Include pricing, credit, partial fulfilment, purchasing, returns and reconciliation. Classify each requirement as standard configuration, a named application, integration or development. Ask who will support every component after launch.
Our Business Central versus NetSuite comparison offers another starting point for a shortlist. It should lead to better questions, not replace a current fit assessment. Avoid choosing by brand familiarity alone or assuming one system fits every wholesaler simply because several similar businesses use it.
Compare the proposed operating model as well as the software. Check implementation responsibilities, data preparation, training, update testing and support coverage. Evaluate whether the business can maintain the solution after the project team leaves. A lower initial price may not be better value if important work is excluded or if the design depends on skills the organisation does not have.
↑ Back to contentsWhat should a wholesaler ask a Business Central partner?
Ask the partner to show how it will discover your trading rules and test the proposed design. Request named ownership of financial, warehouse and integration decisions. Establish which activities your team must perform and how much time the relevant people need to reserve. Participation should be planned rather than squeezed around every other responsibility.
Our Business Central implementation services explain the broader delivery scope. Discuss your difficult transactions early and request a written account of assumptions, exclusions and dependencies. Ask how unresolved requirements will be decided and how changes to scope affect cost, testing and the delivery plan.
Before signing, agree the evidence needed for go-live. That should include completed business scenarios, reconciled opening information, trained users and an operating support route. Make the final decision around readiness to trade, rather than the date on a slide. A well documented project gives both sides a clearer basis for resolving differences and making informed decisions.
↑ Back to contentsHow do we measure value after the first live trading cycle?
Choose measures connected to the problems that justified the investment. You might track disputed stock availability, avoidable credit-note work, unresolved receiving differences or the effort needed to explain order margin. Define each measure before launch so a later improvement is not simply the result of changing its calculation.
Review the first important business cycles with the people doing the work. Ask which tasks are dependable, where staff still maintain shadow records and which exceptions take too long to resolve. Treat the answers as evidence for a prioritised improvement list. Do not assume an informal workaround is harmless because it keeps orders moving today.
Give every improvement an owner and an expected outcome. Some issues require training, clearer approval or better data rather than another extension. Business Central creates value for a wholesaler when staff can make sound commitments, fulfil them consistently and explain the financial result. Keep those outcomes at the centre of ongoing support and development.
↑ Back to contentsWhat else do businesses ask?
Is Business Central only suitable for large wholesalers?
No fixed employee threshold determines suitability. Evaluate the trading model, stock complexity, controls, integrations and resources required to run the proposed solution.
Does every wholesaler need advanced warehouse software?
No. Choose the warehouse configuration and any specialist application around the required work, controls and volume. Demonstrate real receiving, picking and exception scenarios before deciding.
Can we move from spreadsheets and accounting software in phases?
A phased approach may be appropriate, provided data ownership, interfaces and reconciliation are designed for each phase. Agree which system owns each process during the transition.
Who wrote this guide, and how was it checked?
Written by Caleb Adoh, Growth Marketing Manager at NetMonkeys. The limited inventory and warehouse capability statements were checked against the linked Microsoft Learn documentation on 2 November 2026. The wholesale evaluation scenarios are original editorial guidance. Validate specific trading rules, applications, licences and integrations against a written proposal.
How can NetMonkeys help your business?
Talk to our team about your priorities and agree a practical next step.
Speak to NetMonkeys
