Sync orders and customers from NetSuite to Magento 2
The Business sellers that use Magento 2, often sell their products in multiple channels. Most of the Magento B2B and B2C customers create and track the sales order or customer data in the ERP system. In this scenario, the orders either are tracked in NetSuite, not logged-in at all, or manually written to Magento 2. As a merchant, you can sync the NetSuite order and customer data to Magento 2 using the NetSuite order to Magento 2 order (add) and the NetSuite customer to Magento 2 customer (add/update) integration flows.
Note: The NetSuite order to Magento 2 order (add) and the NetSuite customer to Magento 2 customer (add/update) integration flows are available only in the premium edition of the Integration App.
For more information, refer to Sync NetSuite orders and customers to Magento2.
New fields and mappings added to the “Magento 2 customer to NetSuite customer Add/update” flow
As we now have the new integration flow to sync the customer from NetSuite to Magento 2, the existing Magento 2 customer to NetSuite customer Add/Update flow. The flow is further enhanced to check the Is Updated Via Celigo checkbox (on the NetSuite customer record > eTail tab) to make sure that the customer is not synced again using the Magento 2 customer to NetSuite customer Add/Update flow.
The following mappings are added to the Address sub-list to make sure for all the synced customers, the Magento 2 Website ID and Magento 2 Instance ID values are written back to NetSuite.
Export field (Magento 2)
Import field (NetSuite)
Address: Magento 2 Website ID
Address: Magento 2 Instance ID
The Magento 2 customer to NetSuite customer Add/Update flow now writebacks the values to the newly added fields on the NetSuite customer record:
- Magento 2 instance ID
- Magento 2 website ID
On the “Celigo Magento 2 Customer Id Map” record in NetSuite, the flow syncs the values in the Customer ID, Magento 2 Instance, Magento 2 Instance ID, and Magento 2 Website ID fields.
Display dependent flows on the Integration App user interface
You can now find the dependent flows on the Integration App user interface that was previously available only in the backend code. These flows are either auto-triggered or run in sequence by one of the existing integration flows. You can’t schedule, enable, or run the dependent flows. Following are the dependent flows:
- Magento 2 product ID to NetSuite item (update)
- Magento 2 order to NetSuite order Add (on-demand sync)
For more information, refer to Understand the Magento 2 - NetSuite Integration App dependent flows.
Sync cart-level discounts correctly without any variance when an item price is 0
If your Magento 2 order has multiple line items and one of the item’s price is “0,” the Magento Order to NetSuite Order Add flow now syncs the discount correctly based on the option selected in the Bring Magento cart level discounts into NetSuite as setting (Settings > Order section > Discount tab). considers the discount as cart-level, instead of the product-specific (line-level) discount. The flow also ensures to sync the order without any variance to NetSuite.
Filter categories based on the selected Magento 2 instance while syncing the item or matrix group to Magento 2
If your integration app has multiple Magento 2 accounts connected to a single NetSuite account, the NetSuite Item to Magento Product Add/Update flow now syncs the category IDs correctly as per the selected Magento 2 account while syncing the item or matrix group.
Example: If you have two Magento accounts - A and B, if you run the NetSuite Item to Magento Product Add/Update flow from account A, the category IDs are synced only belonging to A to Magento 2. Previously, it used to sync from both A and B accounts, irrespective of which account you run the flow from.
Sync Magento 2 bundle products to NetSuite with correct discount lines on the sales order
If dynamic pricing is enabled in your Magento 2 account, the Magento Order to NetSuite Order Add flow syncs the discount lines correctly to the NetSuite sales order without any variance.
Import mappings are updated from “name” type to “internal ID” type
Some of the import mappings that caused errors are updated from the “name” type to the “internal ID” type for the flows of the following Integration App sections:
Consider the “summary type” column in the saved search during item sync to Magento 2
The NetSuite Inventory to Magento Inventory Add/Update flow now considers the “summary type” column of the saved search selected in the NetSuite Saved Search for syncing inventory levels setting (Settings > Inventory) during item sync to Magento 2 without any script related errors.
The “Add orders created after” setting not remove the paging filter from the order relative URL
In the Add orders created after setting (Settings > Order section > Order tab), when you delete the values or enter new values, now the setting value change does not affect the paging filter or any other parameter in the export URI, only the date filter parameter is updated accordingly.
Information: Any updates to the sandbox environment are supported only on-demand basis.