The sales Manager of an eCommerce manufacturer/supplier wants new purchase orders placed by the retailer to be synced to NetSuite. This is to ensure approval of the orders and pass along approved orders to downstream teams/departments for fulfillment and invoicing.
Generates the purchase orders (EDI transaction 850) from the trading partner source to NetSuite as sales orders. This is a batch flow that gets the purchase order transactions on a scheduled basis from the trading partner source. In integrator.io, the transaction is transformed from EDI JSON to NetSuite JSON using the source bubble.
The flow looks for the corresponding order in NetSuite that matches the purchase order ID. By default, the flow uses the purchase order ID, trading partner, and ISAID field details on the NetSuite sales order to store the purchase order ID and trading partner ID.
- If an order is found in NetSuite, the flow ignores the purchase order and the ignore count is shown as 1 on the Flow Dashboard.
- If the order is not found, the flow creates the sales order in NetSuite with the default status as “Pending Approval”. The success count is shown as 1 on the Flow Dashboard.
You can change the default status of the sales order to be created in NetSuite using the order status mapping.
Important
- Customers and items must already be synced to NetSuite.
- Map shipping and payment methods between source and NetSuite.
Export source: Trading partner source
Import destination: NetSuite
Built-in import: Post NetSuite sales orders (add) – adds or ignores to generate the sales orders to NetSuite.