Prices
Price Specification Use Cases
Extenda Retail recommends always having a
SALES
Price Specification for all Items. This ensures POS and other systems can sell the Item and calculate margins, even if the correct sales price is not yet available.
Create a Sales Price
How to
- Ensure your service has the required API access rights (role with
Create
verb). - Create the JSON payload as described in mandatory requirements:
- Set
PriceType
toSALES
- Set the correct
businessUnitGroupId
orbusinessUnitId
- Set the correct
taxRuleId
- Set the correct
value
(sales price incl. taxes) - Set the correct
itemId
- Set
validFrom
date/time - Set the correct
currencyId
- Set
- Set headers:
Authorization
header with a valid token- Optional:
Correlation-Id
header
- Set
Content-Type
toapplication/json
- Use the
POST
endpoint. - On success, you receive
202 - Accepted
.
Create a Purchase Price
Purchase Price Specifications are needed for logistics and replenishment integrations. See Ordering Option API.
How to
- Ensure your service has the required API access rights (role with
Create
verb). - Create the JSON payload as described in mandatory requirements:
- Set
PriceType
toPURCHASE
- Set the correct
businessUnitGroupId
orbusinessUnitId
- Set the correct
taxRuleId
- Set the correct
value
(purchase price from supplier) - Set the correct
itemId
- Set the correct
orderingOptionId
- Set
validFrom
date/time - Set the correct
currencyId
- Set
- Set headers as above.
- Use the
POST
endpoint. - On success, you receive
202 - Accepted
.
Create a Lowest Historical Price
A LOWEST_HISTORIC_PRICE
Price Specification is legally required in many countries for advertised price reductions.
This is only mandatory when the Item is part of an advertised price reduction (not for markdowns or loyalty promotions).
How to
- Ensure your service has the required API access rights (role with
Create
verb). - Create the JSON payload as described in mandatory requirements:
- Set
type
toLOWEST_HISTORIC_PRICE
- Set the correct
businessUnitGroupId
orbusinessUnitId
- Set the correct
taxRuleId
- Set the correct
value
(sales price incl. taxes) - Set the correct
itemId
- Set
validFrom
date/time - Set the correct
currencyId
- Set
- Set headers as above.
- Use the
POST
endpoint. - On success, you receive
202 - Accepted
.