Need-X.com

Catalog & Pricing

One price, resolved the same way every time

A fixed precedence order — never whichever rule was saved last

The pricing engine walks a documented six-level precedence chain and stops at the first active, matching rule. Two rules at the same level with overlapping validity windows are rejected at save time, not left to resolve randomly at checkout.

Shop the catalog

Available products

Published from the Admin Portal's catalog manager. Add items to your cart, then checkout directly or raise a quotation request instead.

Precedence order

Highest to lowest priority

  1. 1

    Region override

    A destination region legally requires a different price (e.g. duty-inclusive).

  2. 2

    Quote-locked price

    This line converted from an accepted RFQ — the quoted price wins, period.

  3. 3

    Business contract

    A negotiated rate specific to this buyer's account.

  4. 4

    Promotion

    A time-boxed discount on this product or category.

  5. 5

    Tier base price

    The buyer's tier (Small/Medium/Large) has its own base rate.

  6. 6

    Catalog list price

    The default — always present, always the fallback.

Same SKU, different context

How the price actually resolves

Buying contextRule appliedUnit price
Large-tier buyer, EU region, no active promoTIER_BASE₹34,199.00
Large-tier buyer, converting an accepted RFQ quoteQUOTE_LOCKED₹32,299.00
Any buyer, active 15%-off promotion this weekPROMOTION₹33,199.00
Buyer shipping to a region with a compliance surchargeREGION_OVERRIDE₹36,399.00

Illustrative SKU: 200-count nitrile glove case. Same catalog list price (₹34,199.00), four different buying contexts, four different — correct — outcomes.

Versioned publishing

Every catalog write creates a new product version; publishing flips a single pointer. Rollback means re-pointing, not repairing data — so it's O(1) and safe under pressure.

Bulk upload with real feedback

CSV uploads run through a validation queue with per-row pass/fail results and a quarantine table for failures — never a bare "row 4032 failed" with no explanation.

Volume breakpoints

Within a precedence level, the best-matching minimum-quantity breakpoint wins — so a 500-unit order and a 50-unit order on the same promotion can land on different, both-correct prices.

Want to see your own pricing rules modeled this way?

Request a demo