Passer au contenu principal / Skip to main content
← All articles
Connected commerce2 min read

When promotions meet negotiated pricing.

Contract pricing, volume discounts and promotions can overlap on the same product. Their priority order needs to be clear before anyone writes code.

Generated conceptual composition: on a warm ivory stone surface, a precision satin-aluminium mechanical component rests beside three layered cards in matte graphite, brushed aluminium and translucent amber acrylic.
Define the priority order between contract pricing, volume discounts and promotions before coding the rule.

A customer already has a negotiated price on an item. A promotion starts on that same product just as their order reaches a volume-discount tier. Which amount should appear in the cart?

There is no universal rule. Depending on your commercial agreements, a promotion may override a contract price, combine with it or simply not apply to that account. Dates, quantities and product families can all shift the outcome.

Set a priority order everyone explains the same way.

Before writing a single line of code, the precedence rules need to be spelled out. Sales, management and operations should all arrive at the same expected price using the same criteria.

Putting those rules side by side also helps clean house: it quickly separates the exceptions that still make business sense from legacy rules that are hard to justify.

Deciding which price applies in the cart
  1. Check account termsClarify whether contract pricing or account discounts exclude promotional campaigns.
  2. Set thresholds and datesDefine how volume tiers and promotional windows override or sequence one another.
  3. Validate against the ERPTest real edge cases so a rule update inside the ERP does not create silent mismatches.

Illustrative sequence. Actual precedence always depends on your commercial agreements and how pricing is integrated.

Test edge cases and track changes over time.

In Boutik, pricing logic can be adapted to how your business actually operates. The integration then needs to be checked against representative cases: an active contract, a promotion starting, a quantity break crossed or an agreement reaching expiry.

That verification also needs to keep pace with change. Adding a new pricing rule in your ERP can require an adjustment elsewhere depending on how rates are calculated and passed between systems.

Where to start clarifying your pricing rules

  • ✓ Gather a few recent orders where your team still had to verify the price manually.
  • ✓ Confirm in writing whether promotions override, stack with or skip contracted customer rates.
  • ✓ Prepare a short test set covering active contracts, volume tiers and expiring promotions.
Explore the Boutik foundation ↗

AN IDEA WORTH SHARING

Keep the conversation going.

Share on LinkedIn (new tab) ↗Share on Facebook (new tab) ↗Share on X (new tab) ↗