In many businesses, the price on an invoice is the product of a surprisingly complicated set of data: a list price, a customer’s price group, a contract price that may or may not have expired, quantity breaks, a promotional discount, a freight surcharge, a manual override typed by a busy sales officer and a GST setting. When that data is well structured and controlled, prices are consistent and margins are protected. When it is not, small errors repeat across thousands of invoice lines, and margin leaks away without anyone deciding to give it.
Pricing problems are rarely dramatic. A contract price expires but keeps being used. A price increase is loaded with the wrong effective date. A product is priced per box in one list and per unit in another. A discount intended for one customer is applied to a whole price group. Manual overrides become routine because the system’s prices are not trusted. Each costs a little on each transaction; together they can cost more than the business spends on many of its improvement projects.
This article explains the elements of pricing data, how business systems decide which price applies, how to manage price changes, contract prices, discounts and rebates, how GST affects displayed prices, the common errors and how to monitor and govern pricing. It is general information for managers in manufacturing, distribution and service businesses, not advice on pricing strategy itself.
The elements of pricing data
| Element | What it is |
|---|---|
| List price | The standard price for an item, often by price list or channel |
| Price groups or tiers | Categories of customers sharing a price list or discount, such as trade, wholesale or retail |
| Contract prices | Prices agreed with a specific customer, often for a set period |
| Quantity breaks | Lower unit prices for larger quantities |
| Discounts | Percentage or amount reductions, by customer, product group or promotion |
| Surcharges | Additional charges, such as freight, small-order fees or urgent delivery |
| Rebates | Retrospective payments or credits based on volume or other conditions |
| Costs | Purchase or production costs used to calculate margins and check floors |
| Currency | The currency of each price list and any exchange rate rules |
| Tax treatment | Whether prices include or exclude GST, and the item’s GST status |
| Effective dates | When each price starts and ends |
Each element is reasonable on its own. The difficulty lies in how they combine.
How a system decides the price
Most business systems use a pricing hierarchy, also called precedence rules, to decide which price applies when several could. A typical hierarchy might be:
- A customer-specific contract price for this item, if current.
- A current promotional price for this item.
- The customer’s price group price, less any group discount.
- The standard list price.
Systems differ in whether they use the first price found in the hierarchy or the best price for the customer among those that apply, and in whether discounts stack, applying one after another, or the largest applies alone. These rules have large commercial effects and are often configured once and forgotten. Document them, test them with real examples, and make sure sales staff understand them.
| Situation | Question to settle |
|---|---|
| Contract price and promotion both apply | Does the customer get the lower, or does the contract prevail? |
| Customer discount and product group discount | Do they stack, or does the higher apply? |
| Quantity break and contract price | Does the contract price apply at all quantities? |
| Price expires mid-order | Which date determines the price: quote, order or dispatch? |
Effective dates and price locking
Prices should carry effective from and effective to dates, so that changes can be loaded in advance and expire automatically. Equally important is deciding when a price is locked:
- At quote: the quoted price holds for the validity period stated on the quote.
- At order: the price on the order is preserved, even if list prices change before dispatch.
- At dispatch or invoice: the price current on the dispatch date applies, which suits some long-running supply arrangements.
Whatever the rule, the price used should be stored on the transaction itself, so later price changes do not alter historical orders and invoices. The keeping history in business data article explains effective dates and snapshots more generally.
Managing price changes
A controlled price change process typically includes:
- Trigger: supplier cost increases, exchange rate movements, market changes or a scheduled review.
- Analysis: effect on margins, competitiveness and key customers.
- Approval by the person with pricing authority.
- Customer notice where contracts or relationships require it.
- Loading new prices with effective dates, ideally through a controlled import with checks rather than manual editing.
- Verification: checking a sample of prices in the system against the approved list, and test quotes for typical customers.
- Communication to sales and customer service staff.
Unit of measure consistency
Prices must match the unit of sale. A price per box applied to a quantity in single units, or the reverse, produces errors of tens or hundreds of times. Check that every price list states its unit and that conversions in the system are correct.
Contract prices
Contract prices need particular care:
- Record start and end dates, and the contract they come from.
- Alert before expiry, so renewals or reversions to standard pricing are deliberate.
- Record adjustment clauses, such as annual reviews or indexation to published price indexes, and diarise them.
- Limit the number of items under contract pricing where practical; thousands of individually negotiated prices are hard to maintain.
- Review profitability of contract customers periodically, including rebates, freight and service costs.
Expired contract prices that continue to apply are one of the most common sources of margin leakage.
Discounts and authority
Discount authority should be clear and enforced by the system:
- Limits by role, such as sales officers up to 5% and managers up to 15%.
- Approval workflows for discounts beyond limits.
- Margin floors, so the system warns or blocks when a price falls below a minimum margin over cost.
- Reasons recorded for overrides.
The discounting without destroying your margin article explains the commercial effect of discounts on profit.
Rebates and retrospective discounts
Rebates paid after the sale, based on annual volume or other targets, reduce the real price received. They should be recorded in the system against the agreement, accrued as sales occur and included in customer profitability reports. Rebates tracked only in spreadsheets are easily miscalculated or forgotten until a customer claims them.
Quote rules and configured products
Businesses that quote configured products or services often use pricing rules rather than fixed prices: options priced as additions, labour priced at rates per hour, materials priced at cost plus a margin, minimum charges and rounding rules. Keep these rules in the system or in controlled quoting tools, not in individual estimators’ spreadsheets, and review them when costs or labour rates change.
Prices in online channels
Online shops and customer portals add another place where prices can go wrong. Prices may be copied from the business system to the website on a schedule, customer-specific prices may need to appear only after a trade customer logs in, and promotions may be configured separately in the web platform. Keep the business system as the source of prices, synchronise them automatically, show logged-in customers the same price they would receive on an order, and test price displays after every price change and platform update. A pricing error published on a website can reach many customers within minutes.
Imported goods and exchange rates
For businesses that import, costs move with exchange rates, freight rates and duties. Record the currency and exchange rate assumptions behind each cost, update landed costs when significant shipments arrive, and set review triggers, such as an exchange rate movement beyond an agreed band, that prompt a pricing review. Without these, margins on imported products can erode for months before anyone notices that prices were set at a more favourable rate.
GST and displayed prices
Australian GST affects pricing data in several ways. Items may be taxable, GST-free or input-taxed, and price lists must state clearly whether they include or exclude GST. Business-to-business prices are commonly quoted excluding GST, while prices advertised to consumers must generally be shown as a single total price that includes GST and other compulsory charges under the Australian Consumer Law. Check that each channel’s price list follows the right convention and that systems calculate GST consistently. Seek advice for specific tax questions.
Common pricing errors
| Error | Effect |
|---|---|
| Expired contract prices still applied | Customers keep receiving old, lower prices |
| Overlapping effective dates | The system picks an unintended price |
| Wrong unit of measure | Prices out by large factors |
| Stale costs | Margin checks pass when real margins are thin or negative |
| Routine manual overrides | Inconsistent prices and hidden discounting |
| Duplicate customer accounts | The same customer receives different prices |
| Promotions without end dates | Temporary discounts become permanent |
| Rounding inconsistencies | Small differences between quotes, orders and invoices |
Monitoring pricing
Regular reports reveal leakage before it compounds:
- Override reports: how often prices are changed manually, by whom and by how much.
- Margin exception reports: invoice lines below margin floors.
- Expiring and expired contracts.
- Price realisation: actual invoiced prices compared with list prices by customer and product group.
- Price waterfall analysis: a technique that traces the price from list price through discounts, rebates, freight allowances and payment terms to the net amount the business actually keeps, showing where value is given away.
The gross margin and pricing power article discusses how pricing decisions shape profitability.
Testing prices after changes
After any significant change to price lists, contracts or pricing rules, run a set of standard test quotes: a typical customer in each price group, a contract customer, a quantity break, a promotional item and a GST-free item. Compare the results with expected prices calculated independently. Keeping these test cases and rerunning them after each change catches configuration errors before they reach customers.
Ownership and governance
Pricing data needs a clear owner, often a pricing manager, commercial manager or finance manager, responsible for the structure, rules, change process and monitoring. Sales staff should be able to quote and sell efficiently within clear rules, while changes to price lists, contracts and discount authority go through the owner.
Common mistakes
- Undocumented pricing hierarchies that nobody can explain.
- No effective dates, so price changes are made manually on the day.
- Contract prices without expiry dates.
- Discount limits not enforced by the system.
- Costs not updated, making margin checks meaningless.
- Price lists maintained in spreadsheets outside the system.
- No monitoring of overrides and margin exceptions.
A worked example
This is an illustrative example. A building products wholesaler with annual revenue of about $14 million sells to about 300 trade customers, many on contract prices. Gross margin has drifted down for two years, although list prices have kept pace with supplier increases.
Review. An analysis of a year’s invoices finds that about 18% of invoice lines carry manual price overrides, about 40 customers are still receiving contract prices from agreements that expired more than six months earlier, and several products are priced per length in one price list and per metre in another. A price waterfall shows the gap between list price and net price is widest for small customers, who were not supposed to receive large discounts.
Estimated leakage. The review estimates margin leakage of about $210,000 a year, around 1.5% of revenue, from expired contracts, unauthorised overrides and unit errors.
Changes. Contract prices are given end dates and expiry alerts. Expired contracts are reviewed with customers and either renewed on current terms or reverted to standard pricing with notice. Discount limits by role are enforced in the system, with approvals for exceptions. Unit of measure errors are corrected, and monthly override and margin exception reports go to the commercial manager.
Result. Over the following year, overrides fall to about 5% of lines, and the business recovers an estimated $150,000 of the leakage while retaining its key customers. The figures are illustrative, but leakage of this kind is common where pricing data is not actively managed.
Applying this in an Australian business
- Document the pricing hierarchy and test it with real examples.
- Use effective dates for all prices, contracts and promotions.
- Store the price used on each transaction.
- Control price changes through approval, controlled loading and verification.
- Enforce discount limits and margin floors in the system.
- Track contracts, expiry dates and rebates in the system.
- Check GST conventions for each channel and price list.
- Monitor overrides, margins and price realisation monthly.
Questions worth considering
- Could we explain exactly how our system decides the price on an invoice line?
- How many of our contract prices have expired but are still applied?
- What share of invoice lines carry manual overrides?
- Are our costs current enough for margin checks to mean anything?
- Who owns our pricing data and rules?
Bringing it together
Pricing data combines list prices, contracts, discounts, surcharges, rebates, costs, tax and dates through rules that decide the price on every transaction. Document and test those rules, date-control every price, lock and store prices on transactions, manage changes through a controlled process, enforce discount authority and margin floors, track contracts and rebates, and monitor overrides and realised prices. These disciplines protect margin that would otherwise leak away one invoice line at a time.
Source: KEVOS editorial notes, drawing on general pricing, sales operations and business systems practice. Tax and consumer law points are summarised for orientation; seek professional advice for specific situations. Figures in the worked example are illustrative. This article is general information.
