Zopping
Get a token

Pricing tiers

Quantity- and segment-based pricing — different price/discount as quantity rises, optionally scoped to a customer group. The advanced companion to Manage stock & prices.

Read model in this version. Pricing tiers are resolved and returned with product/cart data — there isn't a dedicated tier-management endpoint in the API yet. Tiers are configured at the store level (admin) and surface on reads; this guide explains how to consume them correctly.

How a tier is defined

Each tier rule covers a quantity band and overrides price:

FieldMeaning
minQty / maxQtyQuantity band (inclusive; maxQty: null = unbounded)
mrp / discountPrice for that band
customerTagIdOptional — restricts the tier to a customer tag/segment
tierIdIdentifier for the rule

Reading tiers

Tiers come back on a variant's storeSpecificData (pass storeId):

curl "https://zopping.com/api/catalogue-service/product?organizationId=<org-id>&storeId=<store-id>&productId=100" \
  -H "Authorization: Bearer $ZOPPING_TOKEN"
{
  "storeSpecificData": [
    {
      "storeId": "<store-id>",
      "mrp": 100,
      "discount": 10,
      "pricingTiers": [
        {
          "tierId": 1,
          "minQty": 1,
          "maxQty": 10,
          "mrp": 100,
          "discount": 10
        },
        {
          "tierId": 2,
          "minQty": 11,
          "maxQty": null,
          "mrp": 85,
          "discount": 15
        }
      ]
    }
  ]
}

Applying a tier

Pick the rule whose band covers the line quantity — the first matching minQty ≤ qty ≤ maxQty wins (an open maxQty: null is the top band). In the example, 15 units resolves to tier 2 (mrp 85, discount 15). The cart APIs apply this automatically; replicate the same banding if you compute prices yourself.

Going further

Reference: Catalog · Inventory.