Urgent: Item Mass Update Flow Causing Duplicate Records Across Shopify Stores

Hello Everyone,

I hope you're doing well.

We currently working on migrating the ProductID Item Mass Update flows to GraphQL for our Shopify integration, which spans multiple stores. However, we are encountering an issue where the Item Mass Update flow is creating duplicate records for each store—this happens with both REST and GraphQL APIs.

Here’s a summary of what we have observed:

  • Lookup Criteria: We're matching the Shopify SKU with the NetSuite display name.
  • Test Scenario:
    • I removed all the existing Celigo Shopify Item ID Map records for a single item.
    • Then, I triggered the flow by editing the product and its variant in Shopify.
    • The logs show that the item was fetched during the Shopify export, but it was ignored at the NetSuite import step.

To troubleshoot further:

  • I modified the flow to fail the record at the import step by adding a dummy lookup.
  • With that change, I confirmed the record reached the import stage—but it still ended up being ignored.
  • All the required lookup criteria appear to be met.

This issue is critical, as it’s causing downstream problems in the dependent inventory flow. Could you please assist with this as a high priority?

Thanks in advance for your help.

Hello @sravaninuagesync

If you haven’t done so already, could you please submit a support ticket regarding the issue you're encountering?

Thank you!

Hi @sravaninuagesync,

I’ve gone ahead and created a support ticket on your behalf. You can access it HERE

Let me know if you need anything else!

Hi @sravaninuagesync,

I think you're on the right track but a few things to double-check:

  • Record Type: Celigo Shopify Item Id Map
  • Operation: Add or Update
  • How to find existing records: Ensure this setting is configured correctly

Common mistakes we usually encounter when building custom flows for this use case:

  • Ensure SKU is unique and not empty or null
  • Avoid applying filters in the Import orchestration/bubble during initial development—keep it open until you achieve a successful run
  • Most importantly, ensure the Data Type is set to String for the following fields (commonly missed):
  • Shopify Variant Id
  • Shopify Product Id
  • Shopify Inventory Item Id

Let me know if that works or if you can share you connection debug logs after above verification i can further help as well.

Hi Dagi,

Thanks for the response and submitting a support ticket

Hi Will,

Thank you for your response.

All existing fields were mapped correctly; however, the issue persisted. To resolve it, we created an additional custom field and set its value to true to bypass the duplication process. This approach resolved the issue.