Platform — Pricing Engine

Five layers. One net price.
Zero disputes.

The Emdaad pricing engine resolves contract overrides, volume tiers, and promotional rules in a deterministic sequence — and surfaces conflicts before the buyer sees a price, not after the invoice is disputed.

Request a Demo See the Admin Console

Five-layer resolution. ERP-sourced rules locked.
Conflicts detected before activation.

Dashboard
Commercial Rules
Pricing Engine
Audit Log
Emdaad Admin  ·  Pricing Engine
Commercial
Pricing Engine
Promotions
Assortment
Operations
MOQ & Packs
Order Rules
Reports
Audit Log
Price History
Price Resolution — Juice Box 250ml (case/24)  ·  Al Rayyan Group  ·  Strategic
Search SKU…
# Layer Source Value Applied Status
1
Base Price List
Standard segment · SPL-2026
ERP-synced SAR 54.00 / case Active ···
2
Contract Override
CTR-ARG-2026 · ERP-sourced
ERP-locked SAR 48.50 (−10.2%) Applied ···
3
Volume Tier Break
≥ 500 cases · Admin config
Admin config −5% → SAR 46.08 Applied ···
4
Promotional Override
Q2 KSA Strategic · 1 Apr–30 Jun 2026
Admin config −3% → SAR 44.70 Applied ···
5
Conflict Resolution
System · Checked at resolution time
System No conflict detected Clean ···
Net Contract Price — All 5 layers resolved
Conflict-free · Audit entry logged · Visible to buyer at checkout
SAR 44.70 / case
Layer Summary
Juice Box 250ml · Al Rayyan Group
Base list (Standard) SAR 54.00
Contract (−10.2%) −SAR 5.50
Volume (≥500 cases, −5%) −SAR 2.43
Promo Q2 KSA (−3%) −SAR 1.38
Conflict check ✓ Clean
Net Contract Price
SAR 44.70
5-layer stack · Conflict-free
How It Works

Every price is the result of a defined sequence — not a guess.

Net price is not calculated at checkout. It is resolved in advance, layer by layer, with ERP-sourced rules locked and manual overrides versioned. Every price the buyer sees in the portal is the outcome of this sequence — applied in priority order, logged, and auditable.

Layer 01
Base Price Lists
ERP-synced
The starting price for every SKU is determined by the customer's segment. Emdaad supports Standard, Growth, Regional Partner, Strategic, and Enterprise tiers — each carrying its own base list with separate unit economics. The correct list is applied automatically at order submission based on the customer segment assigned in the platform.
A Riyadh FMCG distributor operating on the Regional Partner list sees SAR 54.00 per case of Juice Box 250ml. A Strategic-tier buyer in Cairo on the same SKU starts at SAR 49.00 — the base list difference is resolved before any contract override is applied.
Layer 02
Contract Overrides
ERP-sourced · Locked
Per-SKU bilateral contract prices synchronized directly from the ERP — Dynamics 365, SAP, or Oracle. When a contract override exists for a customer and SKU combination, it replaces the segment base price entirely. ERP-sourced fields are marked locked in the console; they cannot be edited manually and will not drift from the agreed contract. Buyers always see their negotiated rate.
A Riyadh food distributor's Strategic-tier buyer sees SAR 48.50 per case instead of the standard SAR 54.00 — the contract override is applied automatically on order submission, sourced from the bilateral agreement in Dynamics 365.
Layer 03
Volume Tier Breaks
Admin configurable
Quantity thresholds that unlock automatic reductions, applied on top of the contract price. Tiers are configured per SKU, per product category, or per customer segment — and are evaluated at order submission based on the line quantity. Multiple tiers can exist for a single SKU with increasing discount steps. The buyer sees the tier applied in the price breakdown before confirming the order.
An Egyptian food service distributor ordering 600 cases of cooking oil triggers the 500-case volume tier break, reducing the per-case contract price by an additional 5%. At 1,200 cases, a second tier applies at 9%. Both thresholds are visible in the buyer portal before the order is placed.
Layer 04
Promotional Overrides
Admin configurable
Time-bounded discounts layered on top of the contract price and volume tier. Each promotional rule carries an explicit start and end date — activation and deactivation are automatic, with no manual intervention at period end. Stackability and exclusivity are defined per rule: a promotion marked exclusive will not combine with another promotional override targeting the same buyer and SKU. Scope is set by segment, account, SKU, or category.
A Ramadan Bundle Deal applying −12% to all dairy SKUs for Modern Trade buyers activates on 15 April and expires on 15 May automatically. A separately configured Q2 Key Account Incentive at −8% is marked exclusive — these two rules cannot stack, and the conflict engine resolves the overlap before either buyer sees a price.
Layer 05
Conflict Resolution
System
When two rules target the same SKU and buyer simultaneously — two exclusive promotional overrides, or a promotional override that conflicts with a stackability constraint — the engine detects the conflict before the rule is applied. The configured priority order determines which rule wins. The losing rule is excluded and logged. The resolution is recorded in the audit trail with timestamps, rule IDs, and the outcome. Nothing is approximated; nothing is silently dropped.
Two active promotional rules compete for Halloumi Cheese 500g for a Key Account buyer in Cairo. The engine flags the overlap, applies the rule with the higher configured priority, excludes the second, and writes an audit entry — all before the buyer's portal reflects any price. The conflict log is available to commercial and finance teams without a support request.
Conflict Resolution

Conflicts surface in the console — not in the buyer's inbox.

01
Detected before activation
When two pricing rules target the same SKU and buyer simultaneously, the engine identifies the conflict at the point of rule validation — not at order submission, and not at invoice. The conflict is flagged in the console before either rule is allowed to take effect on a live order.
02
Priority order applied, not guessed
Each promotional rule carries a user-configured priority order. When a conflict is detected, the engine applies the rule with the highest configured priority and excludes the competing rule. The outcome is deterministic — the same conflict resolves the same way every time, on every order, for every buyer the rules target.
03
Logged with full context
Every conflict resolution is written to the audit log: which rules competed, which buyer and SKU were affected, which rule won, which was excluded, what the resulting net price was, and when the resolution occurred. The log is searchable by rule ID, SKU, customer, or date range — no export required.
04
Disputes eliminated at source
Pricing disputes that used to appear as invoice corrections — after goods were received and payment was expected — are eliminated before the order is placed. The buyer sees one net price at checkout. That price is what appears on the invoice. There is no gap between what was shown and what was charged.
Conflict Detected — SKU-0204 · Halloumi Cheese 500g 2 rules competing
Buyer: Al Meera Group  ·  Segment: Key Account  ·  Checked: 2026-05-16 14:22:07
Priority 1 · Applied PRO-0041
Q2 Key Account Incentive
1 Apr – 30 Jun 2026  ·  Exclusive  ·  Key Account segment
−8%
Winner
Priority 2 · Excluded PRO-0097
Ramadan Bundle Deal
15 Apr – 15 May 2026  ·  Exclusive  ·  All dairy SKUs
−12%
Excluded
Both rules are exclusive — they cannot stack. Priority 1 rule applied.
PRO-0041 applied  ·  PRO-0097 excluded  ·  Net promotional: −8%
Audit Entry
2026-05-16 14:22:07 UTC  |  CONFLICT_RESOLVED
SKU: SKU-0204  Buyer: AMG-0007  Rules: PRO-0041, PRO-0097
Applied: PRO-0041 (Q2 KA, −8%)  Excluded: PRO-0097
Net promotional: −8% · −SAR 0.87/unit
ERP Integration & Audit

ERP-sourced rules are locked. Every override is logged.

ERP Lock
Contract prices and base lists synchronized from Dynamics 365, SAP, or Oracle are marked as ERP-sourced in the platform and cannot be edited in the Admin Console. The lock indicator is shown on every ERP-sourced field — padlock icon, greyed edit button, source attribution. The source of truth remains in the ERP; there is no risk of a console edit creating a pricing divergence between what the ERP records and what buyers see.
Manual overrides created in the console — promotional discounts, one-off exceptions, tier adjustments — are clearly distinguished from ERP-sourced data by a separate indicator. They are excluded from ERP sync. Commercial teams can configure overrides with approval workflows without touching ERP records or requiring ERP access.
Audit Trail
Every manual override is versioned. The audit record shows who created the override, when it was created, what the previous value was, when it was approved and by whom, and when it expires. Finance teams and auditors access the full trail directly from the console — no support request, no data export, no waiting for IT to pull a log.
For ERP-sourced fields, the audit log records each sync event: which field changed, what the previous value was, which ERP entity triggered the update, and when it propagated to the platform. The complete sync history is searchable by SKU, customer, date, and field — available to IT and finance without elevated permissions.
Price Rule Configuration — Halloumi Cheese 500g · Al Meera Group Synced from Dynamics 365 · Last sync: 09:14 today
Contract Override — KA-2026
Bilateral contract · ERP-sourced · CTR-AMG-0007
SAR 10.88 / unit ERP-locked
Edit
Promotional Override — Q2 Key Account
Manual · Admin config · PRO-0041 · Expires 30 Jun 2026
−8%  (on contract price) Active
v2 · Khaled A. · 14 May
Edit
Buyer Experience

The buyer sees one number. The console shows how it was built.

Before any order is submitted, the buyer portal displays the net price — final, after all five layers. No estimates, no working rates. For items where the price has changed since the last order, the portal flags the change in amber before checkout, with the previous price shown alongside the new one. There are no surprises at invoice.

Buyer Portal — Gulf Retail Partners
Price on this item has changed since your last order — previously SAR 12.80
Halloumi Cheese 500g
SKU-0204  ·  P0024  ·  Chilled
In Stock
Net price
SAR 10.03
per unit
Strategic Account Vol. tier applied Q2 promo active
Add to Order
Admin Console — Price Breakdown · SKU-0204
Net Price Calculation
Halloumi Cheese 500g · Gulf Retail Partners · Strategic
Layer 1 Base price list (Strategic) SAR 12.80
Layer 2  ERP-locked Contract override (−15%) −SAR 1.92
Layer 3 Volume tier (≥240 units, −5%) −SAR 0.54
Layer 4 Promotional override (Q2 KSA, −3%) −SAR 0.31
Layer 5 Conflict resolution ✓ Clean
Net contract price SAR 10.03
Buyer portal display ✓ SAR 10.03 shown at checkout
Price change flag △ Previously SAR 12.80 — flagged
Who Uses This

Two teams. One pricing engine. Different views of the same truth.

Commercial Director  /  VP Sales
Controls what buyers pay and why.
The Commercial Director owns the segment price lists, approves promotional rule activations, and sets stackability policy. Every promotional override moves through a draft-to-active workflow — the commercial approver is the final gate before a rule touches a live order. Conflict logs give a direct view of where competing rules overlapped and how the engine resolved them, so policy adjustments are made on evidence rather than guesswork. No ERP access is required for any of this configuration.
When a buyer's purchasing director calls to challenge a price, the Commercial Director can pull the full resolution audit for that order in under a minute — which layers applied, which rules fired, which conflicts were resolved, and what the net price was at the moment of order submission. The dispute is resolved before it becomes a credit note.
IT Director  /  ERP Owner
Owns the integration, not the pricing decisions.
The IT Director is responsible for confirming that ERP-sourced rules — contract prices, base lists, and MOQ data — are propagating correctly from Dynamics 365, SAP, or Oracle into the platform. The integration sync dashboard shows the last-synced timestamp, field-level status, and any sync errors for each ERP entity. ERP-locked fields in the platform cannot be edited by the commercial team, so there is no drift between the ERP contract record and what buyers see.
When finance or auditors need to verify a pricing decision, the complete log is accessible without a data extraction request — ERP sync events, manual overrides, conflict resolutions, approval timestamps, and version history are all indexed and searchable from the audit trail. No elevated permissions required, no report to schedule.
ERP Connectivity

Connected to your ERP. In sync within 60 seconds.

Microsoft Dynamics 365
ERP / Finance
SAP
SAP S/4HANA
ERP
ORC
Oracle Fusion
ERP / SCM

ERP sync latency < 60 seconds  ·  Idempotent  ·  Event-driven  ·  Full audit trail

Price it right. Before the order moves.

Talk to our team about how the Emdaad pricing engine maps to your existing ERP and contract structure. We'll show you a live resolution against your segments and SKUs.

Request a Demo See the Admin Console