Read and override product pricing per customer — GSV, listed price, with effective date ranges
| Field | Description |
|---|---|
productId | The product this price applies to |
customerRef | The customer this price is for |
name | The pricing type (see below) |
value | The price amount in plan currency |
startDate / endDate | Effective date range |
name)| Value | Description |
|---|---|
GrossSalesValue | Gross selling price per unit (carton) to the customer |
GrossSalesValuePerKg | GSV expressed per kilogram |
ListedPrice | The official listed/catalogue price before trade deductions |
ListedPricePerKg | Listed price per kilogram |
GrossSalesValue as the primary revenue driver.
ListedPrice is used to compute trade expense deductions.
POST /product-values to inject a price override for a specific plan. This is the programmatic equivalent of a price event in SIMCEL — useful for automating annual price list updates or testing pricing scenarios.
planId. The same product–customer pair can have different prices across plans, allowing you to test the financial impact of price changes scenario-by-scenario.Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The workspace ID to query master data from
Filter by product ID
Filter by customer reference
Filter by pricing type
GrossSalesValue, ListedPrice, GrossSalesValuePerKg, ListedPricePerKg Filter to prices valid on a specific date (ISO 8601). Returns records where startDate ≤ asOf ≤ endDate.
Maximum number of records to return (max 500)
x <= 500Number of records to skip (for pagination)