Tiered pricing data for catalog upload is described in this topic, which also includes a sample template.
Catalog Upload - Tiered Pricing
Full or Delta Load Accommodated
Tiered Pricing may be a full or delta load.
Tiered Pricing Delta Upload Behavior
Suppliers may provide a Tiered Pricing upload file consisting of only the items that need to be updated. The behavior of a delta upload is as follows:
- If the sku does not exist in the system or is empty a warning should be generated and the line should be skipped
- If the sku does exist, the tiered pricing data is added for the item.
-
For each valid sku in the file:
- if the product has existing tiered pricing
- replace the existing tiered pricing with the pricing in the upload file
- For example, if a SKU A has 4-tiered pricing associated to it and the file has 2 tiers, the 2 tiers in the file will now be associated to the item, replacing the 4.
- if the product does not have existing tiered pricing, the tiered pricing in the file is added to the product
- if the product has existing tiered pricing
- A change report and an error report file is generated for Tiered Pricing Upload.
Tiered Pricing Upload Template
Tiered Pricing Support for Catalog-Based Pricing
The Tiered Pricing Catalog file supports multiple prices for the same SKU. Different prices may be associated with different catalogs.
Each unique price/catalog combination will have its own line in the Tiered Pricing Catalog Upload file.
Users are shown the pricing for the catalog mapped to their Content Group. When a User has access to multiple catalogs, the lowest price is displayed.
The following use cases illustrate scenarios for catalog-based pricing.
| Use Case | SKU | Price | Catalog | Result |
|
1 SKU, 1 catalog |
123 |
1.00 |
US |
SKU "123" will be uploaded to catalog "US". If the product was tied to different catalogs, it will be removed from those catalogs and will be associated to the catalog "US" |
|
1 SKU, Multiple catalogs |
123 |
1.00 |
EU|NA |
SKU "123" will be uploaded to catalog "EU" and "NA". If the product was tied to different catalogs, it will be removed from those catalogs and will be associated to the catalog "EU" and "NA" |
|
1 SKU, No catalog |
123 |
1.00 |
NULL |
If no value is specified for 'catalogs', SKU "123" will be uploaded to the lowest Catalog ID. If the product was tied to different catalogs, it will be removed from those catalogs and will be associated to the the lowest Catalog ID. |
| 1 SKU, 2 prices, Multiple catalogs requires multiple rows in the Common Fields file, one for each unique price/catalog combination |
123 |
1.50 |
US |
SKU "123" will be uploaded to catalog US with the price of $1.00"EU" and "NA". If the product was tied to different catalogs, it will be removed from those other catalogs. |
|
123 |
2.00 |
HI|AK |
SKU "123" will be uploaded to catalog "HI" and "AK" with the price of 2.00. | |
|
123 |
3.00 |
NY |
SKU "123" will be uploaded to catalog "NY" with the price of 3.00. |
Tiered Pricing Fields Details
| Column Name | Description | Required | Sample Value |
| part_number | Product SKU | Yes |
A22055FC1 |
| from_qty | The lowest quantity for tiered price | Yes |
5 |
| price | The tiered price value | Yes |
12.99 |
| catalog | The catalog id for the price | No |
HI |
Tiered Pricing Validation and Change Reports
The table below provides details on the validation and change reports generated based on file status.
|
File Status |
Reason (If Status is Failed) | Validation Report is Created | Change Report is Created |
|
Failed |
A file of the same type is being processed by the system | ||
| Failed | File failed validation | Y |
|
| Failed | File failed to be updated due to system issues | Y |
|
| Processed Successfully | Y |
Y |
Comments
0 comments
Article is closed for comments.