Davello & Co.

What Davello & Co. changes in the rules an order runs on.

the account

The order cleared. The rule failed.

22% on the contract; 14.3% realized across eighteen plants.

Plant 14 placed an order on Tuesday: six line items, standard SKUs. The account had been ordering through the plant for three years.

The order priced off the matrix, six points above contract pricing. The CSR who usually caught the plant-level exception was on PTO. The order released through standard workflow, shipped, was invoiced Friday, and entered the customer’s normal AP cycle.

Two weeks after the invoice, before remittance cleared, the customer’s national procurement team ran a variance check: same SKUs, same freight, six points higher to Plant 14 than to Plant 8.

The customer called the rep, the rep escalated to the CRO, and AR opened the dispute against the invoice.

The CRO opened the account: plants 1 to 9 on the 2019 contract; plants 10 to 18 not. The dispute log showed twelve disputes from this customer in two years, each resolved the same way: a credit memo for the price difference. The current invoice was moving toward the same settlement.

What the dispute log did not show: the 2019 contract priced the relationship at 22% gross margin. Realized margin across the eighteen plants today runs at 14.3%.

The customer’s order pattern had shifted from monthly consolidated buys to weekly orders averaging 30% smaller. Freight to the southeast plants moved through a 3PL the original cost-to-serve did not model. Twelve SKUs were being kitted to customer specification without an upcharge, and service touches per order had doubled.

The contract was still the contract on file, but the account no longer behaved like the account priced in 2019.

The gap was $1.1M annually on this customer, and widening.

The CRO settled the dispute the same way as the prior twelve, and put thirty minutes on the calendar with the master data team for Tuesday. The meeting got pushed for ERP integration work. It was rescheduled.

Six other accounts on the books would show the same shape. This one is the second-largest.

the pattern

Settled twelve times. Solved none.

Accounts the business calls profitable that are not.

Plant 14 was not a pricing error. It was one place where the customer relationship had outgrown the rule on file. This is not one customer.

The 2019 contract was priced against the relationship as it stood then. The relationship has not stopped moving since: new plants came online, order size changed, freight moved through a different path, kitting became normal service, service touches doubled. The contract stayed in the file, and everything that no longer fit it was carried by people.

The senior CSR knew the plant-level exceptions, the third rep knew which calls could not sit in the queue, AR knew the credit path, the CRO knew the customer could not be left on a disputed invoice, and the controller could reconstruct the variance later. Every settlement closed a dispute. None wrote a rule. None triggered a review.

The cost did not show up on a single line. It showed as margin that would not reconcile against the deal book, the same dispute settled every quarter, renewals closing at last year’s terms, and credits clearing issues nobody wanted to reopen. Accounts the business still called profitable were not, because freight, kitting, service touches, and credits were living outside the rule the account was priced against.

The pattern gets diagnosed first as pricing discipline, then as contract management, then as master data, then as commercial operations. Each diagnosis is partly right, and each function sees the piece that lands on its desk. None owns the whole question: how commercial terms should keep up with the relationship underneath them.

The same shape appears away from pricing. Availability the system carries and the branch does not trust. Substitutes that clear spec but change cost. Customer rules (ship-complete, packaging, documentation) in the senior CSR’s notes and not on the customer record. Service obligations that win the deal but were never priced into the order. Inherited supplier terms from the last acquisition that reps still operate against.

Each surfaces inside a function: supply, fulfillment, customer service, billing, integration. The issue gets worked where it appears, but the rule that would prevent the next repeat belongs across them.

Someone has to decide what triggers a review, who has authority, where the new term gets encoded, and what the system should do until the new rule is in place. That decision crosses commercial, finance, master data, systems, and operations, so it keeps losing to work already on the calendar.

That is the layer the work sits at.

the rule

The dispute is where the rule surfaced.

Fifteen to twenty rules in a single engagement.

Plant 14 enters the room as a pricing dispute. That is where the issue became visible, but not where the work stops.

The easy answer is to put plants 10 to 18 on the 2019 contract and move on. That would close the visible gap, but it would not answer why the account kept producing the same dispute, why the same credit path kept clearing it, or what the business should do when the relationship changes again.

If a nineteenth plant comes online, does it inherit the contract automatically? If weekly orders keep replacing monthly consolidated buys, does the account still carry the same freight logic? If kitting and service touches are now part of normal service, does the price still mean what it meant in 2019? If the next invoice prices off the matrix before anyone catches it, does AR defend the invoice, credit the difference, or send the issue back for a decision?

That is the work: not to settle the dispute again, but to keep the question open until the business can say what should happen on the next order.

Commercial has to know what can change without damaging the relationship; finance, which margin evidence the business trusts; master data, what treatment to encode and maintain. The customer record and pricing logic have to know what the next quote and invoice should do before the next exception appears; AR, what it can defend when the customer disputes the bill.

The decision cannot stay as “reprice the customer.” It has to become specific enough for the next quote, invoice, review, and override path to use without sending the question back into the room.

That is one rule. An engagement usually has fifteen to twenty.

Availability produces the same kind of decision. The system says stock is available; the branch does not trust the number. The home branch protects margin but may lose the order; network stock protects the sale but gives the margin back in transfer freight. A ship-complete customer cannot be treated like an account that accepts partials. The work is not to improve the inventory report, but to decide what the business is prepared to promise before the next quote goes out.

Customer rules produce another version: ship-complete, packaging, documentation, service expectations, approved substitutes, billing treatment. Some are valuable account knowledge. Some are accommodations the business should price or stop funding. Some are workarounds the system should support cleanly. The work is to decide which answer the next order should inherit.

The room changes with the decision. Plant 14 pulls in commercial, finance, master data, AR, and the people carrying the plant-level exception. Availability pulls in the branch, the planner, the customer-facing surface, and the order workflow. Customer rules pull in the CSR, the warehouse, billing, AR, and the record owner who can make the treatment visible before the order moves.

The logic has to live where the business runs: in the customer record, in the pricing configuration, in the order-release workflow, in the report the controller closes against. Not in a slide. Not in a target operating model. The rule has to live where the next quote uses it, or the next override will erase it.

the override

Whatever bills under exception is the real rule.

The dispute log goes quiet; realized margin meets the deal book.

The override is the test.

A rule the team has agreed to is not the work. A rule in a slide deck is not the work. A rule trained into the field is not the work.

The test comes when something does not fit: a plant comes online between reviews, the freight path changes, the customer’s order pattern shifts again, a substitute clears spec but changes cost, a ship-complete account runs into a partial-availability problem.

At that moment, the business does something: the quote uses a price; the order releases, holds, or routes; the invoice bills an amount; someone may override the path.

That behavior is the actual rule of the business.

An override is not failure by itself. The failure is an override no one can see, defend, or learn from. If a rep can bypass the rule with a side file, if a CSR can carry the treatment from memory, if AR can credit the difference without review, the decision has not held. The business is still settling the exception instead of settling the rule.

The work is complete when the next exception has a governed path: the rule holds, the issue escalates to the right authority, or the rule changes because the business has decided it should.

The proof is operational. On Plant 14, the next quote uses the account treatment without being rebuilt by hand. The next invoice can be defended, corrected, or routed for review because the customer record, pricing logic, and billing treatment agree. The next rep reads the rule from the business, not from the senior CSR’s memory. The variance the controller used to reconstruct by hand now closes by itself.

The same standard applies when the exception is availability, substitution, packaging, documentation, or service treatment: the next order has to reveal the rule instead of rediscovering it.

The work is not complete when the slide is presented. Not when the policy document is signed. Not when the team agrees the new logic makes sense. Those are stops along the way.

If the next override can still disappear into private handling, the work is not complete.

the exception

The business has more room.

The CSR’s notebook is no longer the only place the rule lives.

When the work holds, the first change is often quiet.

The dispute log stops carrying the same unresolved question. The variance no longer has to be reconstructed by hand to explain what already happened. The senior CSR’s notebook is no longer the only place the account treatment exists. The pricing analyst stops rebuilding the same account price from the contract, the override log, and the last credit memo.

The branch stops walking the row before promising routine availability. Billing stops discovering the customer treatment after the invoice is already wrong. AR stops receiving the same dispute as if it were a new event. The COO is no longer settling allocation decisions that should never have reached the COO.

The people do not become less important. The senior CSR still knows the customer. The rep still understands the relationship. The branch still knows when the number on screen cannot be trusted. Finance still sees the pattern before the system explains it cleanly.

What changes is what their judgment is used for.

They are no longer the storage layer for rules the business depends on every week. Their knowledge is carried by the record, workflow, or rule before the next order moves. Their judgment can be used on the next exception, not spent carrying the last one.

The cost shows up before the business has paid it in margin, freight, labor, or credits. Freight treatment is no longer discovered after margin has already leaked. Kitting is no longer normal service with no commercial decision attached. A substitute no longer protects the sale while quietly giving back the margin. A credit memo no longer closes an issue without saying what the business paid to make the issue disappear.

Some exceptions stay. Some should stay. A good customer may need a treatment the standard account does not receive. A branch may need to protect a delivery promise. A service commitment may be worth the cost. The difference is that the business knows what it is choosing.

Growth still creates new difference: a new plant comes online, a new channel changes order behavior, an acquired account brings inherited terms, a customer adds packaging, documentation, or delivery requirements the old record did not carry.

The work does not make those conditions disappear. It changes what happens when they arrive.

A real exception becomes a decision to keep, price, route, encode, or stop. A workaround becomes evidence. A repeated credit becomes a rule problem. A customer accommodation becomes either part of the account treatment or a cost the business chooses not to keep funding.

What changes is not the count of exceptions. It is what an exception means.

the entry

However it starts, the work is the same.

A system replacement, an acquisition, a margin leak, or a sponsor’s portfolio pattern.

Sometimes the company is already inside a system project: ERP is being replaced, CPQ rebuilt, a portal launched. The integrator is asking for rules the business has not yet settled. The question is no longer how one field maps to another. It is what price, availability, customer treatment, approval path, or exception the system is being asked to carry.

Sometimes the trigger is an acquisition. A new branch brings its own price files, supplier records, customer rules, units of measure, freight habits, and promises made before close. Corporate integration may be moving on schedule, but the order path is still carrying two histories. Unless the business settles which history holds, the next order decides for it.

Sometimes the pressure is more focused. A quote-release path is creating margin leakage. Availability cannot be trusted where the rep, portal, or customer needs to see it. A revisioned part is shipping at a cost the deal book did not assume. A regulated shipment is missing the certificate the customer’s compliance team requires. A channel is growing faster than the rules behind it.

Sometimes the question comes through ownership. A sponsor sees the same pattern across one or more portfolio companies: revenue moving, margin not following cleanly, working capital heavier than the plan assumed, system projects exposing operating questions the company has not answered.

The entry point changes. The work does not.

These are different openings into the same condition. The form of the work follows the pressure point, but the object is the same: a rule that has been left to memory, settlement, inherited practice, or system default has to be made explicit before the next order writes it again.

The shape follows the situation. The question underneath every entry is the same: which rule the business settles, and which the next order writes in the meantime.

the question

A first conversation is a specific operating question.

A portfolio company where margin is not matching the deal book.

A first conversation starts with a specific business and a pattern that keeps returning.

A portfolio company where margin is not matching the deal book. A customer account producing the same credit, dispute, or exception every time the order path repeats. An acquired branch still quoting, sourcing, shipping, or billing through inherited logic the parent has not absorbed. A system project asking for rules the business has not yet decided clearly enough to encode.

The question is not whether the process can be improved.

The question is whether the pattern is being produced before the order moves, in the price, promise, availability, customer treatment, approval path, or inherited logic the business is asking the order to carry.

If the pattern is being produced there, the conversation has a place to begin.

Not as a predefined scope. Not as an RFP. Not as a procurement process looking for comparable bids.

As a specific operating question.

At that point, the shape of the practice matters: who is in the work, how close they stay to the operating decisions, and whether the change holds after the room clears.

The next question is who holds that work, and how.