Customer-Specific Pricing: Make Every Invoice Price Explainable

The difficult customer price is rarely the one printed on the main list. It is the old agreement somebody remembers, the percentage discount buried in a spreadsheet, the account that buys only part of the range, or the promotion that has quietly become treated as a permanent price.

Customer-specific pricing becomes manageable when every invoice price can be traced to a deliberate rule. The aim is not to force every customer onto one price. It is to make the exceptions visible, owned and repeatable so the order desk, driver, portal and invoice do not each produce a different answer.

Start with the reason the price is different

A useful pricing audit asks two questions separately: what is the rule? and who does it apply to? The rule may be an absolute price, a discount from a base or a markup from a base. The assignment may be one customer, a customer group or a broader price list.

Do not add precedence rules that the business cannot explain. If two legacy spreadsheets disagree, that is not a configuration problem yet; it is a commercial decision that needs an owner. Resolve the intended agreement before importing it into any new system.

Audit real invoices, not the setup screen

The cleanest test is to choose a small customer sample and work backwards from recent invoice lines. For each line, ask why that exact price was charged. If the answer is “because that is what the spreadsheet says”, keep going until you find the commercial logic underneath.

Use invoices from different order channels if you have them. The same customer should not receive a different price merely because one order came through telesales and another was taken on the round, unless the business has deliberately designed that rule.

Use groups to remove duplication, not hide exceptions

If twenty customers genuinely share the same commercial terms, a customer group can be a cleaner owner than twenty copied rules. The benefit is maintenance: one approved change can apply to the intended group rather than requiring somebody to remember every account that was copied from the original.

But do not use groups to avoid understanding exceptions. If three customers inside the group have a separate agreement, record those exceptions deliberately and review whether they still belong. A migration is a good moment to ask which exceptions are commercial policy and which are just history.

Price, range and promotion are three different controls

A customer’s commercial agreement is not only the price. Some accounts may only buy an approved range, while others should be prevented from buying particular products. If the price list is cleaned but the range rule is left in somebody’s memory, the order desk can still sell the wrong line to the right customer at the right price.

Audit customer whitelists, blacklists or other range controls alongside pricing. Ask whether the rule is commercial, operational or regulatory, who owns it, and how an exception is approved. The aim is one customer record that explains both what may be sold and how the permitted items are priced.

Promotions are temporary selling mechanics. Customer-specific pricing is the standing commercial agreement. Mixing them makes both harder to manage because staff cannot tell whether a low price should still exist after the promotion ends.

Define the base price first. Then apply the promotional rule separately and record its scope. When the promotion closes, the customer should fall back to the intended standing price rather than to whatever value somebody last typed into the order.

Put ownership and review dates on exceptions

Not every pricing exception needs an expiry date, but every temporary arrangement should have a review point. That can include launch support, a short-term retention concession, a branch-opening deal or a customer-specific arrangement agreed for a fixed period.

The review does not have to mean automatic removal. It means the commercial owner is prompted to decide again rather than letting a temporary concession become invisible permanent margin erosion.

Pricing disorder can be created after the first clean-up. A salesperson agrees a temporary exception, a cost increase prompts a rushed change, or a customer is moved between groups and nobody checks the lines that were already specific to that account. Six months later the business has a price that is technically valid but difficult to explain.

Give price changes a small governance rule. Record who approved the change, which customers or groups it applies to, whether it is permanent or temporary, and when it should next be reviewed. If the agreement replaces an older exception, remove or retire the old rule rather than leaving both in place for somebody else to interpret later.

Temporary commercial deals deserve particular care. A price agreed for a promotion, a short supply arrangement or a customer recovery conversation should not quietly become the permanent baseline because nobody set an end point. Where the system does not enforce a review date for that exact rule, keep the review in the commercial process and make the owner explicit.

Prove the same rule through every order channel

A customer-specific price is only useful if the same commercial agreement reaches the order regardless of who captures it. Test representative accounts through the channels they use: telesales, back-office entry, field sales, portal or another integrated order feed where applicable. The test is not whether every screen looks identical. It is whether the final order and invoice carry the price the business intended.

If one channel produces a different result, investigate the data assignment and workflow before staff create a manual workaround. Channel-specific patches are how a clean price list turns back into several unofficial price books.

How RouteMagic represents the rule

RouteMagic supports Price Lists built as absolute prices, percentage discounts or percentage markups from a base, and those lists can be assigned to customers or customer groups. The product also supports tiered and customer-specific pricing. Pricing automation is configuration-dependent: the lists, tiers and customer/group assignments need to be set up.

Customer records can also carry product whitelists and blacklists, helping the order workflow enforce which products may or may not be sold to that account. Promotions are a separate mechanism: RouteMagic supports Buy X Get Y and percentage discount promotions tied to a payment type, assignable per customer; multiple promotions can apply to one order.

The practical implementation task is therefore the same one the audit exposes: make the intended commercial rules explicit before configuration. Once the rule and customer assignment are clear, the same customer master can carry that pricing into the order workflow rather than relying on a separate desk spreadsheet.

Conclusion

Customer-specific pricing is not a problem to eliminate; unexplained pricing is. Start with real invoice lines and trace every price back to a named rule, customer or group assignment and commercial owner. Review the approved product range at the same time, because selling the wrong line is still a commercial error even when the price is correct. Keep promotions separate from standing agreements, give temporary exceptions a review point, and use groups where the customers genuinely share the same terms. The result should be simple to test: two authorised staff members looking at the same customer, product and order context should be able to explain why the price is what it is. If they cannot, fix the commercial rule before automating it.