A Cairo-based supermarket chain opens its ninth store and gets moved from the distributor's Regional Partner tier into Strategic. Nobody reviews the contract price override sitting on the account from the old tier. The next invoice reflects that stale override stacked on top of the new tier's base price list — a net price nobody in the room agreed to, on an order the buyer's procurement manager will dispute the moment finance reconciles it against last month's number.

The tier sets one price. The contract sets another.

Commercial tiers and contract pricing exist for different reasons, which is exactly why they collide. Tiers — Standard, Growth, Regional Partner, Strategic, Enterprise — give a distributor a base price list that scales with the size and value of the relationship, without negotiating every SKU individually. Contract pricing exists for the opposite reason: specific customers with specific history need specific terms that a tier-wide list cannot capture — a two-year volume commitment, a launch incentive, a legacy rate carried over from before the tier structure existed.

Both mechanisms are correct in isolation, but neither one by itself tells you what a buyer should actually pay. A contract override written against a Regional Partner base price does not automatically make sense against a Strategic base price six months later — it was calculated as a discount off one number, and nobody recalculated it against the new one.

When tier assignment and contract overrides are managed as two disconnected settings — one on the customer record, one on a pricing spreadsheet — this drift is not an edge case. It is the default outcome of any customer relationship that grows.

Five tiers, five different pricing behaviors

The five commercial tiers are not just labels for account size. Each one implies a different pricing posture, and conflating them is where a lot of the drift starts.

Standard
List price with minimal deviation. Volume discount tiers apply, but contract overrides are rare — there is usually no negotiated history to override against.
Growth
A tier built for buyers scaling order volume quickly. Base pricing sits below Standard, and volume tiers are the primary lever — contract overrides are the exception, not the rule.
Regional Partner
Buyers with geographic exclusivity or multi-branch coverage. Contract overrides start appearing here — a rate tied to a specific coverage commitment rather than pure volume.
Strategic
High-value accounts with individually negotiated terms as the norm. Nearly every SKU may carry a contract override, and those overrides are reviewed on a schedule, not left to persist indefinitely.
Enterprise
The largest accounts, often multi-entity buyers with their own procurement teams. Contract terms here are formal, contractually documented, and expected to be defensible line by line in an audit.

A buyer moving from Regional Partner to Strategic is not just getting a better base price — they are entering a tier where contract overrides are expected to be actively managed, not set once and forgotten. Treating the move as a label change on the customer record, without reviewing every override on that account, is where the next dispute originates.

The net price waterfall: base, contract, volume

The way to reason about this correctly is to treat net price as a waterfall with a fixed order, not a single negotiated number. Base price comes from the tier's price list. Contract pricing applies a customer-specific override — a flat rate or a percentage discount — on top of that base. Volume discount tiers then apply based on order quantity, on top of whatever price the contract step produced. What is left after all three steps is the net price the buyer actually sees at checkout and the price finance actually invoices against.

Example: a Strategic-tier base price of EGP 340 per case, a contract override of 6% off base (EGP 319.60), then a volume tier of 5% for orders of 500+ units, bringing the net price to roughly EGP 303.62 per case. Change the tier's base price without touching the contract override, and every number downstream shifts without anyone deciding it should.

The waterfall only produces a defensible number if each step is recalculated whenever an upstream step changes — a base price update should trigger a review of every contract override built against it, and a tier reassignment should trigger the same review across the account. When the steps are managed independently — tier in one screen, contract terms in a spreadsheet, volume tiers in a third place — nothing triggers that review, and the waterfall silently reflects an outdated combination of inputs.

Where tier and contract mismatches actually come from

Mid-to-large distributors in Egypt and Saudi Arabia rarely lose track of pricing through carelessness. The mismatches are structural, and they recur in a small number of predictable patterns.

Tier reassignment is a one-field update, not a pricing event
Moving a customer from one tier to another is often a single dropdown change on the account record. Nothing about that action forces a review of the contract overrides already attached to the customer, so the overrides simply carry forward against a new base price they were never calculated for.
Contract terms live outside the system that enforces pricing
A commercial team negotiates a rate over email or in a signed contract, then someone manually enters an approximation into the pricing configuration weeks later. Nuance in the original terms — an expiry date, a SKU-specific carve-out — is easy to lose in that translation, with no system-level link back to the source agreement to catch it.
Volume tier boundaries are checked against the wrong price
When volume tiers are configured to apply against list price instead of the post-contract price, a Strategic customer with a large contract discount can end up paying a volume-discounted rate that was never intended to stack that way — either underpricing the order or triggering a dispute when the actual invoice comes in higher than the buyer expected.

The override was correct the day it was written. Nobody revisited it the day the tier changed. That gap is where the dispute lives.

One net price, computed the same way every time

The fix is not a stricter review calendar or a reminder to check overrides after every tier change. It is making tier assignment, contract overrides, and volume tiers steps in a single, deterministic calculation — rather than three settings maintained in three different places that happen to combine at invoice time.

In the Emdaad Admin Console, the pricing engine runs base price, contract override, and volume discount as one waterfall against the current state of the customer record — not a snapshot from whenever the contract was last written. A tier reassignment does not silently change what a buyer pays; it surfaces every affected override for review before the new pricing goes live. The buyer's cart shows the computed net price in real time, calculated the same way the invoice will, so nothing surfaces for the first time on a disputed bill.

A distributor that stops discovering pricing mismatches at invoice time has removed the gap between when a pricing decision is made and when it is actually reflected in what the customer is charged — the gap where every one of these disputes was living.