Why Unwritten Commercial Rules Decide What Your Automation Costs

The most expensive line in an automation project is rarely the technology. It is the rules nobody ever wrote down, because they have worked for twenty years.

The minimum order value is the clearest example. It lives in a price list, in a framework agreement or in the footer of a quotation. It rarely lives in the system that creates the order. As long as every order passes through inside sales that is enough, because the people there know it by heart. As soon as orders arrive through a shop or an electronic connection, nobody checks it any more.

This is precisely where an automation project either stays within its planned scope or does not.

A rule that fires too late costs more than no rule at all

Suppose a wholesaler works with a minimum order value and a small-order surcharge below it. A customer orders through the shop below that threshold. The order is created, confirmed, picked and shipped. Only in the invoicing run does a rule in the ERP apply the surcharge.

The order confirmation shows one amount, the invoice another. Anyone checking invoices against confirmations, which larger customers always do, rejects the invoice. The transaction goes into dispute, and the dispute costs both sides more processing time than the surcharge brings in.

The rule existed and was substantively correct. It fired too late. Between order intake and invoicing the customer already held a document with a different number on it. That is the underlying mistake almost every automated order intake contains in some variant.

Three thresholds that end up in the same field

Master data usually holds several thresholds side by side, and in conversation they get mixed up.

The minimum order value is an amount per order. The minimum order quantity is a number of units per item, and it usually comes from the manufacturer. Who pays for shipping is governed by yet another threshold, the free-freight limit. The pack size is different again: it says in what increments an item can be ordered, while the minimum order quantity says where those increments start.

An automation that checks against one of these numbers and triggers the response belonging to another is a common sight. A larger order gets held even though only freight was at stake. A small order passes through because the freight limit is stored in the field being checked. Such errors do not arise while building. They arise in the conversation beforehand, when four terms are treated as one number.

Net, gross, before or after discount

The number in the framework agreement is unambiguous. The value it gets checked against rarely is.

It can mean the line total before customer discount or after it, with or without freight and surcharges, with or without VAT. A customer on a substantial framework discount sits above the threshold on list prices and below it on net. Both readings are defensible. The only requirement is that the same one applies in the contract, in the shop and in the process.

If that is not decided beforehand, the process decides it in passing, in whichever way was nearest to hand for whoever built it. From then on that reading applies to every order, without anyone on the commercial side ever having approved it.

The order clears the threshold, the delivery does not

The minimum order value refers to an order. Deliveries split.

An order above the threshold becomes a partial delivery and a back order, each of which sits below it. If the surcharge is applied per delivery at invoicing, the customer pays a surcharge on an order that cleared the threshold. An order with several delivery addresses, for instance several wards of the same hospital, produces the same effect.

Which unit the threshold refers to is a commercial decision, not a technical one. It should be made and written down before anybody puts the condition into a process.

Exceptions that exist only in an email do not exist

Every company has customers with an agreed exception. For inside sales that is no problem, they know them. For an automation, an exception that exists only in an email from a field sales rep simply does not exist.

Such commitments belong in the master record as a flag with a validity date. That is work which falls due before the project and which nobody can take off your hands, because only you know which commitments exist. It is also the point where automation projects most often stall, not on technology but on waiting for a decision.

Why this is the biggest lever on your price

The effort in an automation does not come from the normal case. The normal case is built in a day or two. The effort comes from the exceptions and from the questions that surface during the build and that nobody outside your company can answer.

If there is a person allowed to decide within a few days whether a threshold applies before or after discount and whether it refers to order or delivery, the schedule holds. If every one of those questions has to travel through three departments, the timeline doubles. Billed by effort, the cost doubles with it, and under a fixed price you pay the buffer the provider priced in for exactly this uncertainty.

This is where you have the greatest influence on the price, and it costs you no money, only a decision before the project starts.

What to write down before asking for a proposal

Pull the orders of the last three months and count the ones below your threshold. Where a rule actually bites, those are isolated cases. If there are noticeably more, the rule exists on paper but not in the process, and you now know where the automation has to start.

Then put four decisions in writing: which thresholds apply and what they are called, on what basis the value is calculated, whether the threshold refers to order or delivery, and who approves exceptions. One sheet of paper, no more.

With that sheet you get comparable proposals instead of ballpark figures. Without it, every provider prices the normal case and bills the exceptions later as a change request.

Sophera Consulting records these rules before implementation, puts them in writing with you and only then quotes a fixed price, with no subscription. The entry point is free in the automation check.