Price File Structure and Requirements
Price file is an .XLSX file with a single sheet that contains information about plan and product prices. Depending on the import mode, the file must contain different columns. This section explains the files structure for each import mode and additional requirements that are checked during import.
File structure for direct match
In this import type, a single row in the imported file updates a product fee or subscription period fee price in a specific plan.
The table below explains what fields are necessary for this import type. Additionally, you can download a sample file:
|
Column name (bold columns are used for price entry identification) |
Comment | Value format | Mandatory | Used as identifier |
|---|---|---|---|---|
| Service plan ID | Integer | Mandatory | Yes | |
| Subscription period | An integer value with month(s) or year(s), for example:
1 month(s) 1 year(s) |
Mandatory | Yes | |
|
MPN |
Manufacturer Part Number |
Mandatory, one of these must be provided: MPN or Product ID. If both Product ID and MPN is specified, Product ID will be used. If it is not correct, MPN will not be considered and an error will be displayed. Important: For prices set for a subscription period, both MPN and Product ID values must be set to: period. |
Yes | |
|
Product ID |
Integer | Yes | ||
|
Fee type |
Available resource fee types:
Available period fee types:
|
Mandatory | ||
|
Lower limit |
Used in tiered and volume pricing to define minimum resource amount for the price level. | Mandatory (only for tiered- and volume-pricing models) | ||
|
Rating attribute |
Used in volume pricing to define additional discount level. | Mandatory, used only for plans offering Adobe products with 3 year-commit agreement and Adobe consumables. | ||
|
Price level hint |
Used in volume pricing to define additional discount level. | |||
|
Price effective date |
The date, when the price comes into the effect | 12/4/2024 | Mandatory. If not provided, the price becomes effective immediately after the import. | |
|
Price currency |
Currency in ISO 4217 format | Mandatory | ||
|
Wholesale price |
The price effective for direct resellers. | A number with 4-digit precision. For example: 3.5000 | Mandatory: A wholesale, or retail price, or both must be specified. Learn more Additional requirements. | |
|
Retail price |
The price effective for direct customers. | |||
|
Recommended wholesale price |
The price that will be default for the direct resellers of your direct resellers. Your direct resellers can change it for their sales. |
Optional. Requires that the recommended prices feature is enabled. | ||
|
Recommended retail price |
The price that will be default for the direct customers of your direct resellers. Your direct resellers can change it for their sales. |
|||
| Wholesale SKU | The SKU that corresponds to the wholesale price. | Optional. Requires that the SKU feature is enabled. | ||
| Retail SKU | The SKU that corresponds to the retail price. |
File structure for template-level match
A price entry in the imported file updates all prices with the same MPN, billing period, and subscription period in all plans of a service template or product line.
The table below explains what fields are necessary for this import type. Additionally, you can download a sample file:
|
Column name (bold items are used for price entry identification) |
Comment | Value format | Mandatory | Used as identifier |
|---|---|---|---|---|
| Service template ID | Integer | Mandatory | Yes | |
| Billing period | An integer value with month(s) or year(s), for example:
1 month(s) 1 year(s) |
Mandatory | Yes | |
| Subscription period | An integer value with month(s) or year(s), for example:
1 month(s) 1 year(s) |
Mandatory | Yes | |
|
MPN |
Manufacturer Part Number | Mandatory | Yes | |
| Vendor ID | Mandatory | |||
|
Fee type |
Available resource fee types:
Available period fee types:
|
Mandatory | ||
|
Lower limit |
Used in tiered and volume pricing to define minimum resource amount for the price level. | Mandatory (only for tiered- and volume-pricing models) | ||
|
Rating attribute |
Used in volume pricing to define additional discount level. |
Mandatory, used only for plans offering Adobe products with 3 year-commit agreement and Adobe consumables. Must be used only for tiered- and volume-pricing model. |
||
|
Price level hint |
Used in volume pricing to define additional discount level. | |||
|
Price effective date |
The date, when the price comes into the effect | 12/4/2024 | Mandatory. If not provided, the price becomes effective immediately after the import. | |
|
Price currency |
Currency in ISO 4217 format | Mandatory | ||
|
Wholesale price |
The price effective for direct resellers. | A number with 4-digit precision. For example: 3.5000 | Mandatory: A wholesale, or retail price, or both must be specified. Learn more Additional requirements. | |
|
Retail price |
The price effective for direct customers. | |||
|
Recommended wholesale price |
The price that will be default for the direct resellers of your direct resellers. Your direct resellers can change it for their sales. |
Optional. Requires that the recommended prices feature is enabled. | ||
|
Recommended retail price |
The price that will be default for the direct customers of your direct resellers. Your direct resellers can change it for their sales. |
|||
| Wholesale SKU | The SKU that corresponds to the wholesale price. | Optional. Requires that the SKU feature is enabled. | ||
| Retail SKU | The SKU that corresponds to the retail price. |
File structure for account-level match
A price entry in the imported file updates all prices with the same MPN, billing period, and subscription period in all plans of the account.
The table below explains what fields are necessary for this import type. Additionally, you can download a sample file:
|
Column name (bold items are used for price entry identification) |
Comment | Value format | Mandatory | Used as identifier |
|---|---|---|---|---|
| Billing period | An integer value with month(s) or year(s), for example:
1 month(s) 1 year(s) |
Mandatory | Yes | |
| Subscription period | An integer value with month(s) or year(s), for example:
1 month(s) 1 year(s) |
Mandatory | Yes | |
|
MPN |
Manufacturer Part Number | Mandatory | Yes | |
| Vendor ID | Mandatory | |||
|
Fee type |
Available resource fee types:
Available period fee types:
|
Mandatory | ||
|
Lower limit |
Used in tiered and volume pricing to define minimum resource amount for the price level. | Mandatory (only for tiered- and volume-pricing models) | ||
|
Rating attribute |
Used in volume pricing to define additional discount level. | Mandatory, used only for plans offering Adobe products with 3 year-commit agreement and Adobe consumables. | ||
|
Price level hint |
Used in volume pricing to define additional discount level. | |||
|
Price effective date |
The date, when the price comes into the effect | 12/4/2024 | Mandatory. If not provided, the price becomes effective immediately after the import. | |
|
Price currency |
Currency in ISO 4217 format | Mandatory | ||
|
Wholesale price |
The price effective for direct resellers. | A number with 4-digit precision. For example: 3.5000 | Mandatory: A wholesale, or retail price, or both must be specified. Learn more Additional requirements. | |
|
Retail price |
The price effective for direct customers. | |||
|
Recommended wholesale price |
The price that will be default for the direct resellers of your direct resellers. Your direct resellers can change it for their sales. |
Optional. Requires that the recommended prices feature is enabled. | ||
|
Recommended retail price |
The price that will be default for the direct customers of your direct resellers. Your direct resellers can change it for their sales. |
|||
| Wholesale SKU | The SKU that corresponds to the wholesale price. | Optional. Requires that the SKU feature is enabled. | ||
| Retail SKU | The SKU that corresponds to the retail price. |
Additional requirements
During the import, price configuration is validated. If the configuration is not valid, you will see an error explaining what is needed to be fixed.
One of the most complex validation rules is related to price combinations. The table below lists price combinations and their validity.
| Wholesale price | Retail price | Recommended wholesale price | Recommended retail price | Configuration validity |
|---|---|---|---|---|
| Specified | - | - | - | Valid |
| - | Specified | - | - | |
| Specified | Specified | - | - | |
| Specified | - | Specified | - | |
| Specified | - | Specified | Specified | |
| Specified | Specified | - | Specified | |
| Specified | Specified | Specified | - | |
| Specified | Specified | Specified | Specified | |
| - | - | - | - | Not valid |
| - | - | Specified | - | |
| - | - | - | Specified | |
| - | Specified | Specified | - | |
| - | Specified | - | Specified | |
| - | - | Specified | Specified | |
| - | Specified | Specified | Specified |