An issue has been detected where legacy order records are being unintentionally updated by Shopify, falsely flagging them for re-entry into the current processing queue through the integration app.
While we work directly with Shopify to permanently resolve this issue, we have provided a temporary workaround to avoid further disruption to your order records. See below for further details on the issue as well as step-by-step instructions to implement the workaround.
Flows impacted:
- Shopify order to NetSuite order (cash sale or sales order)
- Shopify order cancellation to NetSuite cancellation (add)
- Shopify fulfillment to NetSuite fulfillment (add)
- Shopify refund to NetSuite refund (add)
For orders not previously synced via the integration app (orders manually synced prior to the implementation of the IA):
The integration app will identify and process the transactions as new orders, leading to duplicate and false records in NetSuite.
For orders previously synced via the integration app:
The integration app will identify these as duplicate transactions and will not allow them to be synced. However, this backlog in the IA may lead to a bottleneck in the NetSuite queue, resulting in latency in processing transactions.
Workaround: Add an input filter to the import bubble that appears after the Shopify export, to restrict the already processed old orders. For example, take a look below for the Shopify order to NetSuite order (cash sale or sales order) flow.
To resolve the issue:
- Go to integrator.io and navigate to the Shopify - NetSuite integration app tile.
- Go to Flows > Order.
- Click Shopify order to NetSuite order (cash sale or sales order) flow.
- In the Post orders to NetSuite import, click +.
- Click the Filter icon.
- Click Add rule.
- In the fields dropdown list, select record.created_at.
- In the filter operator dropdown list, select is greater than or equals.
- In the value textbox, enter the date from when you want to sync the orders. For example 2023-12-01 (YYYY-MM-DD).
Important: Ensure that the input filter for the 'record.created_at' field is configured to have a sufficiently extensive period, thereby minimizing the risk of overlooking recent orders or updates to existing orders. For instance, if an input filter is implemented to exclude entries after the ''record.created_at' of December 5th, an order created on December 3rd and subsequently updated would fail to sync due to the constraints of the input filter. To overcome this issue, it is advisable to set the ''record.created_at' filter starting from December 1st. This approach aims to broaden the time frame considered by the filter, effectively excluding only those orders that are significantly outdated and were incorrectly updated from Shopify.
- Click save & close.
Once the above configuration is set, in the next run, the flow will exclude the older records, and ensure that the latest records are synced.
Comments
Any updates on this issue?
Holly Pacheco We have identified that the issue originates from the Shopify API, which is not responding as expected to our API calls. Consequently, a workaround has been provided to address this problem.
Thanks!
Please sign in to leave a comment.