Follow a single ordinary enquiry through a wholesale business, and the cost becomes clear. A customer calls to ask where their order is. Sales pick up, opens Business Central, and find the order. To be sure about delivery, they check with the warehouse, which confirms the shipment went out yesterday. Sales then write an email with the tracking details and the expected date. Four people, three systems, and several minutes have been spent handing over information that already existed, fully, before the phone rang. Now multiply that by the number of times it happens in a day. This article follows that enquiry, shows why it is so expensive even when the data is ready, and lays out what customers should be able to see for themselves through a Business Central customer order portal.
One enquiry, step by step
The enquiry looks trivial, which is exactly why its cost stays hidden. Break it down and the steps are these: the customer decides it is easier to ask than to wait, so they call or email; a salesperson stops what they were doing to take it; they open the ERP and locate the order; they confirm the physical status with the warehouse, because the system shows what was planned and the warehouse knows what actually left; and finally someone composes a reply and sends it. Every step is short. Together they add up, and none of them created anything new, since the order status, the shipment record, and the documents were all sitting in Business Central the whole time.
The deeper cost is interruption. Each enquiry pulls a salesperson out of selling and an operations person out of running the warehouse, and the switching back and forth is where the real time goes. The information was available; what was missing was a way for the customer to reach it without a person in the middle.
Why does "the data is already there" not help?
Wholesalers often assume that because the data lives in the ERP, answering an enquiry is quick. In practice, having the data and delivering it are two different jobs. Business Central runs the business and holds an accurate record, and that is the job it should do. Putting a slice of that record safely in front of an external customer, in a form they can read, is a separate job that the ERP was never meant to perform, so the gap is filled by people. Every enquiry is the cost of that gap, paid one call at a time.
The load also grows with the business. Each new customer adds another stream of "where is my order" contact, so the enquiry workload climbs with sales while margin stays flat. Handling it with more staff scales the cost in step with growth, which is the opposite of what a wholesaler wants as volume rises.
What should customers be able to see themselves?
The way to remove the cost is to let customers answer their own routine questions against live data, under access to your control. A customer order portal gives each customer a view of their own orders, drawn straight from the ERP, covering the handful of things they call about.
Order status. Where each order stands, from placed through to dispatched, the most common question answers itself.
Shipment details. Tracking and delivery of information for orders that have shipped, which is the point most "where is my order" calls are really chasing.
Associated documents. Order confirmations, delivery notes, and invoices tied to the order, available to download whenever the customer needs a copy.
Notifications. Automated alerts when an order changes status or ships, so the customer is told before they think to ask, which removes the enquiry altogether, so it never has to be answered.
Alongside these, a customer can also check livestock, see their own pricing, and place a new order in the same place, so the portal handles the whole ordering relationship, beyond the status of question alone. Each customer sees only their own orders and data, governed by role-based access.
A simple way to measure the cost
Before and after any change, it helps to size the problem with one figure: enquiries per 100 orders. Count the order-status enquiries you receive over a set period, whether by phone, email, or chat, count the orders you processed in the same period, and express the first as a rate of the second. If you handled 800 orders in a month and fielded 240 status enquiries, that is 30 enquiries per 100 orders.
The number is useful in two ways. It turns out a vague sense of "we get a lot of these" into something you can track, and it gives you a clear before-and-after measuring once customers can self-serve. A visible drop in enquiries per 100 orders is the cost coming back to your team at the time. It is worth logging the rough handling time per enquiry too, since the rate multiplied by that time is the hidden cost expressed in hours.
Where to start?
Pick the single most common enquiry, almost always order status, and make that self-service first, before extending to documents, stock, and ordering. Decide what each customer should see and which records stay private between accounts, since that shapes the whole setup.
Xpand Portal's Customer Order Management module is designed around common order management processes, this ready-to-use module gives customers a structured way to place orders, check stock availability, view agreed pricing, exchange documents, and track deliveries. With direct access to ERP data and configurable ordering workflows, businesses can standardize order processing while keeping customers connected through one secure portal. The Xpand Portal Team can show you how it works on your own orders in a demo.