Price Tables vs. Calculation

Price tables are static lists that assign a fixed price to a product or product variant. Calculated pricing derives the price at the moment of quotation from the actual production cost of that specific configuration. The difference is not just technical — it determines whether your prices are accurate, maintainable, and connected to reality.

Two Models for the Same Problem

Every manufacturer needs to answer the same question: what do we charge for this product?

Price table management answers it by lookup. Someone built a table — at some point, based on some cost structure — and the salesperson finds the right row and reads the price. It's fast, it's simple, and it works well when products are few, configurations are limited, and costs are stable.

Calculated pricing answers it by computation. The system reads the current cost of producing that specific configuration — bill of materials, production routing, overhead — and derives a price from it. It's more complex to build, but it produces a price that's accurate regardless of how many configurations exist or how frequently input costs change.

The choice between these two models matters less for manufacturers with ten standard products than for manufacturers with configured offerings where every order is different. For the latter, price table management doesn't just underperform — it breaks down entirely.

💡 Insight: A manufacturer with configurable products across sizes, materials, finishes, and quantities can easily reach millions of potential SKU combinations. No table can cover that.

The Table Problem: Configured Products Are Infinite

The fundamental issue with manufacturing price tables for configured products is combinatorial. A product with five size options, four material choices, three finish types, and six quantity ranges has 360 distinct combinations — and that's for a simple product. Add personalization variables, regional pricing, and customer-specific discounts, and the table explodes into thousands or millions of rows.

No one maintains that table accurately. They maintain a simplified version — covering the most common configurations, using averages or approximations for the rest — and accept that outlier combinations will be mispriced. Sometimes over, sometimes under. The magnitude of the error depends on how far the actual configuration sits from the nearest row in the table.

This is the static pricing problem in manufactured goods: the table creates an illusion of coverage. It looks organized. Every product has a price. But for configured products, most of those prices are approximations, not calculations. They're close enough to avoid obvious errors — but systematically wrong in ways that accumulate across hundreds of orders.

💡 Tip: A well-formatted price table feels like a pricing system. But a table that covers 200 configurations while your products generate 50,000 possible combinations is not a pricing system — it's a series of educated guesses organized into a spreadsheet.

The Maintenance Problem: Tables Become Outdated Immediately

Even for manufacturers with limited configurations, the table-vs-calculation question comes down to maintenance: how do you keep the table current?

Input costs change constantly. Raw materials move with commodity markets. Energy costs shift quarterly. Supplier contracts renew on their own schedule. Overhead rates evolve as production volume and workforce composition change. Every time one of these inputs moves, the prices derived from the old cost structure become wrong — sometimes by a small amount, sometimes by a margin-destroying amount.

Price table management requires someone to notice the cost change, calculate its impact on affected SKUs, update the relevant rows, verify the changes, and publish a new version. In practice, this happens on a quarterly cycle at best — meaning at any given moment, the table reflects costs from weeks or months ago, and every quote going out in the interim carries the error.

Static pricing problems compound silently. The commercial team is quoting with confidence. The table looks fine. Finance sees margins that don't match expectations. The investigation always finds the same answer: costs moved, the table didn't follow.

Calculated pricing eliminates the maintenance cycle. When input costs change, the next quote automatically reflects the new cost structure. There is no table to update, no revision cycle to manage, no window of exposure between cost change and price adjustment.

When Tables Are Appropriate (and When They're Not)

Price tables are not inherently wrong. For manufacturers with a small number of standard, stable products and predictable cost structures, table management is efficient and sufficient. The lookup is fast, the maintenance burden is low, and the margin for error is narrow.

The model breaks down under three conditions:

High configurability. When products combine multiple variables — dimensions, materials, finishes, quantities, personalization — the number of combinations exceeds what any table can cover accurately. Calculated pricing is the only model that scales.

Cost volatility. When input costs change frequently — raw materials, energy, exchange rates — the window between table updates creates systematic margin exposure. The higher the cost volatility, the more damaging the lag.

Make-to-order production. When each order is unique and the production cost varies by configuration, a table can only approximate. The real cost of a specific order can only be known by computing it from the actual bill of materials and routing — which is what calculated pricing does.

Understanding the limits of manufacturing price tables connects directly to cost-to-price calculation, which defines how calculated pricing derives prices from real production costs, and to configurable product pricing, which addresses how pricing scales across complex product structures.

How EXX Cloud Handles This

EXX Cloud eliminates price tables entirely for configured products. Instead of a table to look up, there's a calculation engine to run. When a salesperson opens a new quote, the system reads the configuration — every component, every specification, the production routing, the overhead allocation — and computes the price from the current cost of producing that exact combination.

If the same product was quoted last week at a slightly different price, it's because input costs shifted between the two quotes. The salesperson sees the financial result behind each price — margin, cost breakdown, comparison to similar past orders — so the number is transparent, not a black box.

There are no tables to update, no revision cycles to manage, no approximations for uncommon configurations. Every combination that can be configured can be priced — accurately, instantly, from current cost data. That's what moves manufacturing from price table management to real-time pricing in practice.

Frequently asked questions

What is the difference between price tables and calculated pricing?

Price tables assign fixed prices to products or variants, looked up at the time of sale. Calculated pricing derives the price at the moment of quotation from the actual production cost of that specific configuration. Tables are fast and simple but require constant maintenance and can only approximate costs for configured products. Calculated pricing is always current and scales to any number of configurations because it computes rather than stores the price.

Why do price tables fail for configurable products?

Configurable products generate a combinatorial explosion of possible variations — sizes, materials, finishes, quantities, personalization options — that quickly exceeds what any table can cover. Most tables address a fraction of possible configurations and use approximations for the rest, producing prices that are systematically wrong for uncommon combinations. Beyond coverage, tables require continuous maintenance: every time input costs change, affected prices must be identified, recalculated, and updated. For manufacturers with volatile cost structures and complex product portfolios, that maintenance burden becomes unmanageable.

How can manufacturers move from tables to dynamic calculation?

The transition requires connecting pricing to the production cost model — bill of materials, routing, overhead rates — rather than to a static reference. The key dependencies are: accurate, current cost data per component; a production routing model that translates configuration into manufacturing steps; and overhead allocation logic that distributes fixed and variable costs per order. When these inputs are in place, the pricing engine can compute any configuration on demand. The result is a pricing process that maintains itself as costs change, rather than requiring manual revision cycles.

Related terms

See the real result of every sale.

We're selective about who we work with. If you have configurable products and want visibility into the financial result of every order, let's talk.