Wholesale process optimization starts where the margin leaks

Take the classic 2/10 net 30 term: a two percent discount for paying on day 10 instead of day 30. Annualized, that is a return of roughly 37 percent (2 / 98 x 365 / 20). Pay a supplier invoice on day 11 because it sat on a buyer's desk, and you have passed on a return no bank will give you. That is why wholesale process optimization should start with the places where margin disappears without a trace in the books, before anyone talks about software.

In wholesale, five of these places show up for a structural reason: each sits on the boundary between two departments. The information exists somewhere in the company. It just reaches the wrong person, or reaches the right one too late, and no monthly report ever flags it as a mistake.

Why wholesale process optimization should be measured in margin

Say a product costs 80 euros to buy and sells for 100. Gross profit is 20 euros. The supplier raises the price by five percent, your selling price stays put, and gross profit drops to 16 euros. In this example a five percent cost increase wipes out a fifth of the profit on that item.

The same effect shows up in all five places below. On thin markups, a small slip in price or payment terms hits gross profit several times harder than its face value. A process can look fine in revenue terms and still cost you money.

1. The supplier raises prices and your selling prices stay where they were

The price increase arrives in purchasing as a PDF or an email. Purchasing updates the cost price in the item master and considers the job done. Whether selling prices follow is a sales decision, and sales often finds out when the quarterly margin review looks worse than expected. List prices can be adjusted in one go. Customer-specific prices and framework agreements can't, because each one is its own deal.

An agent can read the supplier notice, find the affected items and produce a list: which customer prices fall below your minimum margin after the increase, how much revenue each customer brought in last year, and which salesperson owns the account. Sales still decides what gets passed on. The difference is that they see the list before the increase takes effect instead of a quarter later. Our article on customer prices and framework agreements covers how those prices can also get lost when orders are created automatically.

2. Special prices that never expire

A field rep grants a customer a special price for a construction project, or a promotional price is meant to run for one quarter. The ERP has a "valid until" field, and nobody is forced to fill it in. The project wraps up, the price stays in the system, and the customer has no reason to bring it up.

Half of the fix is a rule in the ERP: a special price without an end date can't be saved. For the prices already in the system, a monthly report pulls every special price with no end date or an expired occasion, adds margin and revenue, and sends each rep their own cases to confirm. Anything unconfirmed after two weeks goes to the head of sales. We would not reset these prices automatically. Some of them rest on a verbal promise the system knows nothing about, and a customer who suddenly sees list price on an invoice will be on the phone within the hour.

3. Early payment discounts expire during invoice approval

The discount window starts on the invoice date. The invoice lands in a shared inbox, gets uploaded to an approval tool or printed, and then waits for the buyer who placed the order. If that buyer is at a trade fair for two days and the goods receipt hasn't been posted yet, ten days go by fast. The invoice then gets paid at full price, because chasing the supplier for the discount takes more effort than it's worth.

An automated flow reads the invoice as soon as it arrives, picks out the discount rate and deadline, and matches lines, prices and quantities against the purchase order and goods receipt. If everything matches, the invoice goes straight into the payment run. Only mismatches reach a person, sorted by discount deadline. The same check catches freight charges or surcharges that were never agreed. Our piece on matching delivery notes and invoices explains why the goods receipt has to be part of that match.

This one is easy to put a number on. Your accounts team can report how much discount suppliers offered last year and how much of it you actually took.

4. Supplier rebates nobody tracks

Volume rebates with tiers, marketing contributions and promotional allowances get negotiated in the annual supplier meeting. After that they live in a spreadsheet on the purchasing manager's laptop or in a binder. Two things slip. The first is the tier. Suppose that in November you are 15,000 euros short of the next rebate level. You could pull forward orders that would have gone out in January anyway, as long as warehouse space and cash allow it. In February that option is gone. The second is the claim itself. Depending on the agreement, you have to prove volumes or completed promotions before the supplier pays, and some claims have a deadline.

Once the terms are captured in a structured way (tier thresholds, period, proof required, deadline per supplier), this is straightforward to automate. A flow compares running purchase volume from the ERP against the tiers, alerts purchasing when a level is within reach, and prepares the year-end claim with supporting documents. A language model can help pull the terms out of the annual agreements the first time. Someone who sat in the meeting still has to check them, because the clause that matters tends to hide in a footnote.

5. Customer deductions get written off

Here is a typical pattern. A customer pays 1,940 euros on a 2,000 euro invoice, taking a three percent discount two weeks after the deadline passed. Another short-pays 85 euros for a damaged pallet without ever filing a claim. Accounts receivable sees differences too small to justify a phone call and writes them off below a fixed threshold. Case by case, that's reasonable. Across a year and a few hundred customers it can add up to money nobody would hand over on purpose, and customers learn that deductions go through.

Automation helps with the sorting. It matches incoming payments and remittance advice against open items and assigns each deduction a cause: discount taken late, price difference against the order confirmation, short payment for quantity or quality, or unclear. For the clear cases it drafts a polite request for the missing amount. Whether that request goes out is up to someone who knows the customer. With a key account, letting it go may be the smarter call, but then it should be a decision and not a side effect of a write-off threshold.

Where an agent helps and where a rule is enough

Not all five need AI. The end date on special prices is a mandatory-field setting, and plenty of ERP systems already ship a discount report that nobody opens. Check that before paying anyone to build something. An agent with a language model earns its keep where the inputs are messy: price notices as PDFs, remittance advice in ten different layouts, rebate terms written as prose. Everything else is plain matching and reporting that reliably lands with the right person.

At Sophera Consulting we walk through these five places with you in the free automation check: which of them costs your business money, which numbers you can pull from your ERP and accounting system to prove it, and which flow is worth building first. We then build the agent or automation at a fixed price, with no subscription.

Where to start

Measure the two discount leaks first, because your accounting data already holds the numbers: supplier discounts not taken and customer deductions written off in the last fiscal year. For special prices, a list of every price without an end date, sorted by revenue, is enough. Price increases and rebates may well be the bigger items, but they are harder to quantify after the fact. Then automate the leak with the biggest number, starting with alerts and suggestions for the person responsible. We would only build a flow that changes prices or sends payment requests on its own once those suggestions have proven right for a few weeks.