Pricing is one of the few levers that can lift margin without touching labour, scrap, or throughput. Yet in most manufacturing businesses, pricing decisions still depend on memory, spreadsheets, and informal approval processes that were designed for a business one-third of its current scale. Rule-based pricing systems replace this with configured commercial logic: a set of explicit rules that calculate the appropriate price for each transaction based on the variables that legitimately affect it, enforce margin floors without requiring manual intervention, and route genuine exceptions through a structured approval process rather than an informal one. Building a rule-based pricing system is not primarily a technology project. It is a commercial design project that technology implements. The design work. Defining what the rules should be, how they should interact, and where exceptions should be routed --- The Architecture of a Rule-Based Pricing System A rule-based pricing system has five components that work together to produce consistent, margin-protective pricing across all transactions. Component What It Does What Breaks Without It Cost integration Connects pricing to live cost data Prices become detached from actual margins as costs move Customer tier logic Applies rate structures based on validated customer classification Pricing reflects negotiation history rather than commercial policy Volume break rules Calculates volume discounts from confirmed order economics Volume discounts granted without verification of qualifying volumes Margin floor enforcement Prevents below-floor pricing without formal approval Below-floor deals ship routinely without review Exception workflow Routes above-threshold exceptions to appropriate authority All exceptions go to the same approver regardless of size or risk Cost integration is the foundation. A rule-based pricing system that calculates prices from a cost base updated quarterly is no more accurate than a spreadsheet. The system must connect to current cost data. Live ingredient or material costs, current freight rates, actual overhead allocation Without this, the system can enforce rules consistently and still produce quotes that are priced below actual cost. Customer tier logic is where most implementations get stuck. Defining customer tiers sounds straightforward. Strategic accounts, preferred accounts, standard accounts, spot A customer classified as strategic because they are a large account in terms of revenue may be a small account in terms of margin. The tier logic must be built on the commercial criteria that actually matter to the business, applied from objective data, and reviewed regularly. Volume break rules must reflect the actual economics of scale rather than a discount table that someone created in 2019 and has been applying ever since. The volume threshold at which a 5% discount is warranted should reflect what the economics of producing and shipping that volume actually justify. Taking into account setup costs, storage costs, and the working capital implications of large orders. --- Designing the Rules: The Commercial Work That Precedes Implementation The most common failure mode of rule-based pricing implementations is implementing the system before the rules are designed. The technology is deployed. The existing pricing is loaded. The result is a digitised version of the existing problems, now enforced consistently. The commercial design work that must precede implementation involves three activities. Mapping current pricing reality. Pull the last twelve months of transaction data and analyse the actual distribution of prices and discounts across the customer base. This analysis almost always reveals that the current pricing is more varied than the official price list implies. With a significant tail of transactions at rates that were never explicitly approved as policy but have become de facto standard through accumulated exceptions. Defining the rules from the data. The rules in the system should reflect where the data shows pricing genuinely varies for legitimate commercial reasons, and should close the gaps where it varies for illegitimate reasons. Customer tier thresholds should be set where the data shows natural breaks in commercial relationship quality. Volume break thresholds should be set where the data shows the economics genuinely change at scale. Designing the exception workflow. The exception workflow — the process by which prices outside the configured rules are approved — is as important as the rules themselves. A workflow that is too slow creates pressure to set the rules loose enough that most situations do not require exceptions. A workflow that is too bureaucratic creates pressure to work around it. The right design routes exceptions to the minimum authority level needed, requires documented justification, and returns a decision within hours rather than days. --- Measuring Whether the System Is Working A rule-based pricing system is working when three things are true simultaneously: margin is improving, deal velocity is maintained, and the exception rate is falling over time. If margin is improving but deal velocity is falling, the rules are too tight and are blocking legitimate commercial activity. If deal velocity is maintained but margin is not improving, the rules are too loose and exceptions are too freely granted. If the exception rate is rising rather than falling over three to six months, the rules do not reflect commercial reality and need to be recalibrated. The data that the pricing and promotion management system generates — every transaction, every exception, every approval, every outcome — is the feedback loop that enables this calibration. This is the compounding benefit of rule-based pricing that goes beyond the immediate margin recovery: the system gets more accurate over time because it learns from the data it accumulates.