On this page
Walk the counter at a distributor on a Tuesday morning and you will see the same thing every time: a contractor with a truck outside, a rep with three windows open, and a pause. The pause is the product. Everything else — inventory accuracy, pricing discipline, fill rate — eventually shows up as either a short pause or a long one.
Most ERP platforms were not built to make that pause short. They were built for retail checkout, where the customer picks the item off a shelf and price is price, or for manufacturing, where the order arrives days before it is needed and MRP has time to think. Distribution sits between the two, and the order entry screen is where the mismatch becomes visible.
Distribution order entry is its own discipline
Retail checkout answers one question: what is the total? Manufacturing order entry answers a different one: can we build this, and when? Distribution order entry has to answer half a dozen questions simultaneously, for a customer who is present, about items whose availability, price and substitutes all vary by account.
Can I get it today, or from the other branch by tomorrow? What does this customer pay for it — under their contract, or the last time they bought it? If it is out, what supersedes it? Are they already waiting on three backorders? Is their account on credit hold? Which lot did we ship them last time, because they will ask.
A generic order screen makes each of those a separate lookup. Six lookups is not six times slower than one — it is worse, because each one is a context switch, and each context switch is a chance for the rep to guess instead of check. Guessing is how you get a mis-priced line, a promise you cannot keep, or a sale that quietly walks out the door.
The counter is not a checkout lane. It is a live negotiation about availability, price and substitution, conducted under time pressure, by someone who needs six answers on one screen.
What has to be on one screen
Here is the working list. Not a wish list — the minimum a counter or inside-sales rep needs visible without leaving the order.
- Live available-to-promise across branches. Not "on hand". On hand includes stock already committed to picked orders and to the will-call rack. The rep needs what is genuinely promisable, here and at every other location, right now.
- Customer-specific contract pricing. The negotiated price for this account, applied automatically, not looked up in a binder or a spreadsheet on someone's desktop.
- Last price paid. The single most-asked question at a counter is "why is it more than last time?" A rep who can see the last price paid for that item and that customer answers in three seconds instead of escalating.
- Substitutes and supersessions. When the requested item is out or discontinued, the replacement should appear on the screen, not in the memory of whoever has been there longest.
- Open backorders for the account. So the rep can consolidate a shipment, cancel a duplicate, or tell the customer the truth before the customer tells them.
- Credit status and terms. Visible before the order is built, not surfaced as a posting error afterwards.
- Lot and serial detail where it applies. For regulated, warranty-bearing or traceable goods, capture at the point of sale, not reconstructed later from paperwork.
What each missing element costs
Every item on that list, when it is missing, converts into either dwell time (the customer waits) or lost lines (the order ships smaller than it could have). Both are measurable in your own data, which is the point — you do not need an industry benchmark to know what this is costing you. You need to look.
| Missing on the order screen | What the rep does instead | What it costs |
|---|---|---|
| Cross-branch availability | Phones the other branch, or says "we're out" | Dwell time, or a line lost to a competitor who checked |
| Contract pricing | Looks it up, or charges list and issues a credit later | Margin leakage plus rework in accounts receivable |
| Last price paid | Escalates the "why is it more?" question to a manager | Dwell time and an unnecessary discount to close it |
| Substitutes and supersessions | Relies on tribal knowledge, or lets the line drop | Lost lines, and a hard ceiling on how fast new hires ramp |
| Open backorders for the account | Nothing — the duplicate ships | Double shipment, return handling, credibility |
| Credit status | Builds the order, discovers the hold at posting | Rework, an awkward call, sometimes a pick already done |
| Lot and serial at the point of sale | Records it on paper for later entry | Traceability gaps and a warranty claim you cannot defend |
Pull thirty days of counter transactions and tag the ones that involved a phone call to another branch, a manager override on price, or a credit memo issued within a week of the sale. That number is your gap, in your business, with no assumptions attached.
Will-call and pickup: the forgotten workflow
Will-call is where generic ERP shows its origins most clearly. In a retail model, the customer takes the goods away at the moment of sale. In distribution, a huge share of volume is ordered now and collected later — sometimes hours later, sometimes days, sometimes by a driver who is not the person who placed the order.
That creates a state the software has to represent honestly: stock that is physically in the building but is not available to anyone else. If will-call inventory still shows as on hand, your availability numbers are fiction, and the fiction is discovered by the next customer who is promised something that is already sitting in the rack with someone else's name on it.
A workable will-call flow needs a few specific things. The order has to reserve stock at the moment of commitment, not at pick. The rack location has to be visible to whoever is at the counter when the customer arrives. The handover needs a recorded release — who collected it and when — because "we never got it" is a conversation you want to settle with data. And a partial pickup has to be normal rather than an exception that requires a supervisor, because customers routinely take four of the six items and leave the rest.
The same logic applies to the retail-facing counters distributors increasingly operate alongside trade sales; that hybrid pattern is what Retail Point of Sale is built around, with inventory updating in the ERP at the moment of transaction rather than at end of day.
Quote to order, and where margin leaks
Ask a distributor where quotes are prepared and you will often get an answer that involves a spreadsheet. It is understandable — the quoting tool is flexible, the rep knows it, and the ERP screen is slow. It is also the single most reliable place to find margin leakage in a distribution business.
Here is the mechanism. A rep builds a quote outside the ERP, using pricing they believe to be current. The customer accepts a week later. Someone re-keys the quote into an order. In that re-keying, three things can go wrong and usually at least one does: the price on the quote is no longer the cost basis it was built on, a line is transcribed wrong, or an item that was available when quoted is not available now — and nobody re-checks, because the quote said it was.
Every re-key is also pure cost. It is a second person doing the same data entry twice, and it is the reason quote-heavy distributors quietly carry more inside-sales headcount than their revenue justifies. Conversion should be a single action: the accepted quote becomes the order, carrying its line detail, its pricing basis and its availability check with it, with an explicit re-validation at conversion rather than an assumption.
None of this is exotic. It requires that quoting live in the same system as pricing, inventory and the customer record — which is the whole argument for handling it inside order management rather than beside it.
The modules that close the gap
Centerprism approaches this as a set of connected modules rather than a single screen, because the data the rep needs is owned in different places.
Order Entry
Brings together the data points the team needs at the moment of entry — customer account status, inventory availability, pricing rules, alternates for out-of-stock items and kit configurations — on one screen, with every order flowing straight through to your Microsoft Dynamics GP financials. The Order Entry datasheet (PDF) covers the module in detail.
Pricing Management and Price Memorization
Pricing Management embeds volume tiers, contract pricing, promotional rules and item-class rates directly in GP, so the correct price applies at order entry without a manual lookup or an override. Price Memorization is the piece that answers the counter's most common question: it retains what a given customer paid for a given item, so last price paid is on the screen rather than in someone's memory. The Pricing Management datasheet (PDF) has the specifics.
Interactive Sales Advisor™
Centerprism's Interactive Sales Advisor™ puts the suggestion in front of the rep at the point of entry rather than relying on tenure — the alternate, the related item, the thing the experienced counter hand would have mentioned. It is the mechanism by which a six-month hire sells like a six-year one.
Inventory Management underneath all of it
None of the above works on stale numbers. Inventory Management supplies the live position the order screen quotes from, and PrismView™ is where you go afterwards to see which lines dropped, which quotes never converted and which accounts are consistently taking the substitute instead of the original.
Distributors comparing this against their current setup can browse the full module documentation in the datasheet library, or read how the pieces fit together for wholesale distribution specifically.
A five-minute diagnostic
Stand behind your counter for one hour, with a notepad, and count four things.
- How many times did a rep leave the order screen to find something?
- How many times did a rep phone another branch to check stock?
- How many price questions were escalated to a manager?
- How many customers left with fewer lines than they asked for?
Multiply by your operating hours and your number of counters. That is the size of the gap, and it is the number worth taking to a demo. If you would like us to walk your own scenarios through the order screen rather than a canned one, request a demo and bring your three hardest counter transactions with you.
