1. Choose the Correct Import Profile
Go to Import / Export > Import
Click Add new import job
Select the
tier_pricingprofile from the dropdown
This will hide irrelevant options such as:
Target Store
Field delimiter
Column mapping
These are pre-configured based on the profile.
2. Prepare Your File
Download the example file provided in the interface. Your import file must exactly match the column structure and header names in the sample.
Typical required columns include (as per example template):
SKUCustomer GroupQtyPriceReset Existing Tier Prices(Yes/No)
Note: The legacy fields such as tier_price_website, tier_price_group, tier_price_qty etc. from older documentation are no longer applicable or required. The import logic now relies on structured rows, not delimited field sets within a single product row.
Example file:
sku | website | customer_group | tiers | delete current tiers |
EXAMPLE-SKU-001 | * | * | 200:6,95/500:5,95 | No |
EXAMPLE-SKU-002 | * | * | 200:6,95/500:5,95 | Yes |
3. Resetting Existing Tier Prices
To clear existing tier prices for a SKU before adding new ones, use the Reset Existing Tier Prices column:
"Yes": All existing tiers will be removed before applying the new ones"No": New tiers will be added or updated without removing existing ones
Important validation rule:
If multiple rows share the same SKU, the value in
Reset Existing Tier Pricesmust be consistent across all of them. Mixed values (e.g., one row "Yes", one row "No") will result in a validation error.
Allowed values:
"Yes"(case-sensitive, must be exact)Variants such as
"yes","YES"are allowed"Ja"or other translations are not accepted
The same applies to "No".
4. Upload and Validate
Once the file is ready:
Upload the CSV or Excel file manually or provide a URL
The system will automatically validate the structure and contents
✅ On success: You can save or run the import
❌ On error: A clear message will indicate what needs to be fixed
5. Scheduling (Optional)
If importing via a URL (Google Sheet or hosted file), you can schedule the import:
Supported for recurring updates (e.g. daily syncs)
Not available for manual uploads
Frequently Asked Questions
Q: Can I still use the old method with tier_price columns in the base product import?
A: Yes, tier pricing updates are still supported in the global profile using legacy fields, but we recommend migrating to the tier_pricing profile for improved structure and error handling.
Q: Can I assign tier prices to specific customer groups?
A: Yes. The Customer Group column supports both default and custom groups. These must match the exact names used in your store.
Q: What happens if the file structure is incorrect?
A: Validation will fail, and you will not be able to proceed until the file matches the expected structure.