The “Map Magento Websites/Customer Groups with NetSuite Price Levels” setting supports a three-level mapping. If you have set up quantity pricing for your SKUs in NetSuite, this setting allows exporting the quantity pricing in NetSuite as tier pricing in Magento 2. You can provide the mapping between Magento websites, Magento customer groups, and NetSuite price levels to create pricing tiers on a Magento SKU. Depending on how you want to add this info in Magento2, each row is a unique combination of website, customer group & price level or each row can have a single default website.
You can provide the mapping between Magento websites, Magento customer groups, and NetSuite price levels to create pricing tiers on a Magento SKU. Depending on how you want to add this information in Magento, each row could be a unique combination of a website, customer group, and price level or each row can have a single default website.
- If you do not need tier pricing, check the Sync attribute values to All Store Views box in the Settings > Product tab and run the "NetSuite Item to Magento Product Add/Update" flow. The flow imports the price from the "NetSuite price level for syncing product price" setting.
- You cannot simultaneously import attributes and sync tier pricing to all store views. If you uncheck the Sync attribute values to All Store Views checkbox, you can sync tier pricing and you cannot update tier pricing for all store views.
- When creating a mapping for a single (global) website, do not set the Magento 2 Website and Default Price Level fields in the table. Setting these fields will prevent your price levels from being applied.
- The tier pricing functionality is not supported for the bundle products.
- Do not add the "Website Id" field to the saved search results, as it can prevent tier pricing from loading.
Before you configure tier pricing
Before you configure the “Map Magento Websites/Customer Groups with NetSuite Price Levels” setting, ensure to configure multi-currency price levels and import websites to NetSuite. To understand more about the multi-currency price levels, refer here.
Configure tier pricing
Step 1: Magento2 configuration
To use tier pricing in your Magento2 account, ensure to configure the price at the website level (Stores > configuration > Catalog > Price > Website).
Step 2: NetSuite configuration
While you configure the item in NetSuite, ensure to provide price and quantity for an item.
Step 3: Configure “Map Magento Websites/Customer Groups with NetSuite Price Levels” setting
You can map NetSuite price levels to Magento customer groups of a Magento Website. Or, you can map NetSuite price levels to a Magento Website. The Magento tier pricing should be mapped appropriately in the integration app so that no errors or duplicate products get created during product syncs.
- The values in each row have to be unique.
- A website can’t have multiple default price levels.
- In integrator.io, click the Magento 2 - NetSuite tile.
- Go to Settings > Integration flows > Product > Advanced Settings > Map Magento Website/Customer Groups with NetSuite Price Levels.
- Below the column names, click each Refresh icon. This will fetch values present in NetSuite and Magento2.
-
Select either or both of the following.
- Under the "Magento 2 Website" column, select the appropriate Magento Website.
- Under the "Magento 2 Customer Groups" column, select the appropriate Magento customer group.
- Under the "NetSuite Price Levels" column, select the desired price level for the values selected in step 4.
- Under the "Default Price Level" column, select Yes if you want to set the price specified in NetSuite price level for syncing product price as the default price. This would sync the default price if no price is found for the mapped tier pricing.
- Click Save.
Step 4: Run the flow
Run the "NetSuite Item to Magento Product Add/Update" flow.
Results in different scenarios
- When you do not select any Default Price Level then the Integration App will apply the default price from the NetSuite price level for syncing product price drop-down list.
- If you select Default Price Level as “Yes” for a single website and not for another website, the Integration App processes prices according to the default price level selected for that website. For other websites, the Integration App will consider default from the NetSuite price level for syncing product price drop-down list.
- If you select Default Price Level as “Yes” for each website, the Integration App will process prices according to respective websites and their price levels.
- When you select two default price for a single website, the Integration App will generate an error.
Support multi-currency price levels
If you have websites with different currencies, you can sync combinations of NetSuite price level and currency. Each combination will be a separate tier pricing row. You can also define a unique price value at the website level per customer group. The currency in Magento2 is managed at the website level and customers and customer groups are managed at the global levels. For the customer groups, you can have a separate tier pricing row.
To understand more about the multi-currency price levels, refer to Support multi-currency price levels.
*Update to prevent tier pricing from being overwritten: “Map Magento Websites/Customer Groups with NetSuite Price Levels” setting not to replace custom scripts data
Comments
2 comments
Do not set the Magento 2 Website and Default Price Level fields in the table when you're creating mapping only for 1 (global) website. Otherwise it will not take your price levels.
Juraj Toth, Thank you for letting us know.
Added the below note in the article:
Note: If you do not need tier pricing check the "Import attributes values for All Store Views" box in the Product - advanced settings and run the "NetSuite Item to Magento Product Add/Update" flow. The flow imports the price from the "NetSuite price level for syncing product price" setting.
Please sign in to leave a comment.