Handling Special Pricing Without Spreadsheets
Short answer: Customer-specific pricing managed in spreadsheets is fragile — it gets stale, creates disputes, and depends on the one person who maintains it. A system connected to AutoCount applies the right price automatically at the point of order, every time.
How Special Pricing Gets Complicated
Trading companies almost always have pricing variation. The reasons are legitimate:
- Customers who buy in volume get a lower unit price
- Long-standing accounts have negotiated rates that predate current catalogue prices
- Contracts specify fixed prices for a defined period regardless of cost changes
- Certain customers receive prices in a different currency
- Some customers receive product bundles at a package price
Each of these is a business decision that made sense when it was made. The problem is what happens to that information over time.
The Spreadsheet Failure Pattern
The typical setup: one person (often an experienced sales coordinator or the owner) maintains a master pricing spreadsheet. Sales reps refer to it before quoting. Invoices are checked manually.
This breaks in predictable ways:
| Point of Failure | What Happens |
|---|---|
| Spreadsheet not updated | Customer is quoted last year's rate after a price increase |
| Wrong version used | Two versions of the file exist; sales uses the older one |
| New rep doesn't know | Quotes catalogue price to a contract customer; dispute at invoicing |
| Person who maintains it leaves | Pricing knowledge walks out the door |
| AutoCount has different prices | Finance invoices at catalogue; customer paid at contract rate; credit note required |
Each failure is recoverable individually. Over a year, they add up to meaningful revenue loss and a finance team spending significant time on corrections.
How Systematic Pricing Works
A customer-specific pricing system stores pricing rules in a structured database connected to your AutoCount integration. When a sales order is created, the system looks up the correct price based on:
- Customer identity — specific prices agreed for this account
- Product — the item being ordered
- Quantity — if tiered pricing applies (e.g., 1–99 units at RM X, 100+ at RM Y)
- Date — contract prices with start and end dates; expired contracts fall back to catalogue
- Currency — if the customer is invoiced in USD or SGD
The sales rep sees the correct price populated automatically. They do not need to look it up, calculate it, or ask anyone.
AutoCount Integration for Pricing
AutoCount has a price list function, but it has limits — particularly for complex tiered pricing, time-bound contract rates, or pricing that varies by both customer and quantity simultaneously.
The integration layer extends AutoCount's pricing capability by managing the logic externally and pushing the resolved price into the AutoCount transaction. The result: AutoCount invoices at the right price, and the pricing rules are maintained in one place with an audit trail.
Wei Yot, who previously worked at AutoCount, designed the integration approach around how AutoCount handles price lists and customer-specific overrides — which means the pricing data in the integration database stays consistent with AutoCount rather than creating a parallel system that diverges over time.
What Pricing Management Looks Like in Practice
| Function | How It Works |
|---|---|
| Set a contract price | Enter customer, product, price, start date, end date — system applies automatically |
| Update a price for all customers | Change catalogue price; contract prices unchanged until their end date |
| See what price a customer gets | Look up any customer/product combination and see which rule applies |
| Approve a price exception | Sales requests a one-time exception; manager approves with reason logged |
| Review pricing by customer | Report shows all active price agreements per customer |
The Approval Layer
Not every price change should be free for any sales rep to make. A pricing system with an approval workflow means:
- Sales can request a price exception, not unilaterally apply one
- Approved exceptions are time-limited and documented
- The owner or sales manager sees a weekly summary of exceptions granted
- Exception patterns — the same product being discounted repeatedly to the same customer — become visible data rather than invisible habit
FAQ
Can we handle both percentage discounts and fixed prices in the same system?
Yes. Pricing rules can be expressed as a fixed unit price, a percentage discount from catalogue, or a formula (e.g., cost-plus margin). Multiple rule types can coexist in the same system for different customers or products.
What happens when a contract price expires?
The system automatically falls back to the next applicable rule — either another active contract price, a customer-level default, or the current catalogue price. Expiring contracts can be flagged in advance so sales can renegotiate before they lapse.
Does this require replacing AutoCount?
No. The pricing system integrates with AutoCount and pushes the resolved price into each transaction. AutoCount continues to handle invoicing, AR, and accounting as normal.
Book a System Audit