...
| Property | Mandatory | Examples | Description |
|---|---|---|---|
| SKU code |  | 701423-L31 | SKU code that corresponds to SKU in PIM Note this relationship is weak, which means SKU code does not necessarily have corresponding SKU that exists in PIM |
| Quantity | | 1 | Price record activation quantity (quantity tier). For example quantity of 1 means that list/sale prices are available for given SKU when 1 or more items are in cart. Quantity 10 would mean that customer has to add at least 10 items of this SKU to activate this price |
| List price | | 9.99 | The price of 1 unit of SKU for given quantity tier It is recommended to align list price across all price records for SKU in a given period |
| Sale price |  | 8.99 | Sale price of 1 unit of SKU for given quantity tier. Should be less than list price Sale price is optional |
| Valid from | | 01-Jan-2016 23:59 | Activation time of this price record. Optional and can be left blank, which indicates that record is active from beginning of time. |
| Valid to | | 10-Jan-2016 23:59 | De-activation time of this price record. Optional and can be left blank, which indicates that record will be always active after it had activated. |
| Tags | | xmas summer2016 | Tag can be used by business user to group together price records belonging to a specific price campaign, such as Christmas or Summer sales |
...
| Property | Examples | Description | ||||||
|---|---|---|---|---|---|---|---|---|
| Policy | COST_Main VIP | Policy allow to mark given price record with special access. This is very effective to hide prices from common customers (e.g. only VIP customers should see this price) or all customers (e.g. keep track of internal prices such as "buy in" or "cost" prices, which set basis for price rules
| ||||||
Fulfilment centre
| Main | Limits this price only to items ordered from specific fulfilment centre.
| ||||||
Price upon request
| true | Hides the price in frontend so that customers cannot see it. This allows to make the product visible without disclosing the actual price.
| ||||||
Offer price
| true | Allows to display list price as sale price (i.e. visually styled as sale price)
|
...
Base list prices provided by price records with list price at quantity 1, no sale price and no from/to time to indicate that it is always available. It is recommended to keep single base list price record for each SKU available in shop to ensure default price is always available.
Warning Products with a base price will not appear in frontend unless specified as "Showroom" in the inventory record - Sale prices provided by price records with list price and sale price at quantity 1 and may optionally define from/to time period. There can be many sale price records with different from/to periods, even when timeframes overlap. The platform will automatically deduce best customer value sale price for current point in time for current customer.
- Multi buy prices following the same rules as sale prices and allow to take them one step further by also checking the current quantity in customer shopping cart to provide bulk discounts. Major difference in multi buy price record is that quantity tier is greater than one.
Cost (or buy in) prices that use
policy naming convention (e.g. COST_Main), which allow to track the cost of the product to the business and are useful for automatic price generation and reportingTextbox Body COST_[fulfilment centre code] Info Cost prices are automatically resolved and saved with placed orders enabling generation of profit/loss reports and aiding any other audit, export or reporting function - Special prices that use a mixture of policy and fulfilment centre configurations to provide special prices available to a specific customer niche.
...
Adding SKU price requires SKU code and list price (currency and shop are automatically used from current view). Note that SKU code does not necessarily needs to match the existing SKU data. If the SKU code does correspond to an existing SKU data the table with price records will display SKU name, otherwise the SKU name will remain blank. "Quantity" represents the quantity tier of given SKU. "List price" represents the base price for a SKU, whereas "Sale price" (which is optional) represents discounted list price. "Valid from" and "Valid to" define price record active period. If left blank the platform assumes that record is always available.
...
| Warning |
|---|
Price that are entered into price list can be either NET (without tax) or GROSS (including tax), which depends on the tax configuration. It is up to business to decide which "mode" will suit best for price management. See taxation documentation, which explains this topic in detail. |
...
It is anticipated that most of the price list management will be done via import/export facility automatically. In case of manual management manual import/export facility will also be useful when managing prices for large catalogs.
...