Best Software for 2025 is now live!

Order Sync Flows issues Realtime and Scheduled creating duplicate orders

Here is the scenario: Realtime order sync used to miss some order syncs and we were unable to detect from Shopify end. The reason being the Shopify orders were synced with SO number from NetSuite. We would not know about this until the Customer opened a support ticket enquiring about the product shipment. So the solution was to enable the scheduled order sync flow so that this would pickup all the Shopify orders and ignore the ones already created and create the missed ones. This solution is working well, however we had further issues during the high velocity order times. Due to some glitch in NetSuite/Celigo the orders were created by real time flow did not have eTail IDs. Later the Scheduled order flow kicked in and created duplicate orders. This led to duplicate fulfillment and shipping of products. This was a revenue loss to the company.
2 comments
Looks like you’re not logged in.
Users need to be logged in to answer questions
Log In
Carlos V.
CV
NetSuite Business Systems Analyst, PMP
0
A time offset of a few milliseconds is needed to ensure the records do not overlap.
Looks like you’re not logged in.
Users need to be logged in to write comments
Log In
Reply
Rico A.
RA
Introducing iPaaS to the world.
0
Hi - I checked back with our support team, it looks like they had isolated this to a NetSuite-specific bug (#609066) that adversely impacted one of your NetSuite configurations. Is this your understanding as well? Our understanding is that this resulted in custom fields not being written to the NetSuite transaction and thus, when you executed the scheduled instance of the order flow, it created a 2nd order within NetSuite. We consulted with NetSuite to obtain a fix for the issue you faced and hope that this hasn't recurred. It's challenging to diagnose problems when the connected endpoints have sudden issues but I hope our team was able to address this for you. Please let me know otherwise.
Looks like you’re not logged in.
Users need to be logged in to write comments
Log In
Reply