Ignore Archived Shopify SKUs within Shopify Product Id to NetSuite Item Mass Update Flow??
Does anyone know of a way to "Ignore" archived Shopify SKUs when running the Shopify Product Id to NetSuite Item Mass Update flow?
Since there are items setup in Shopify that are not setup in NetSuite, I receive an error for each of these items every time this flow runs. It would be nice to eliminate the SKUs from being considered in the Export stage of the flow.
Any help is greatly appreciated. Thanks!
1
Comments
Hello Bryn Harvey
This is Khaisar from Celigo team. Please allow me to answer your question.
We do have an Advanced Setting in the Integration App "Sync inventory levels for both published and unpublished Shopify items" under "Inventory" section. By unselecting this setting, the flow will automatically ignore the "Archived" Items.
Can you please check this once and let us know if this is working for you.
Thanks,
Hi Khaisar,
The client actually isn't actually syncing inventory levels back and forth from NS to Shopify, they are only using the Shopify Product Id to NetSuite Item Mass Update flow to create the cross references between the items in Shopify and the items in NetSuite. I was just wondering because every time the flow runs it creates an error for the handful of items that are in Shopify, but not in NetSuite, and it's frustrating. I built a separate standalone flow to export the product ID and status from shopify and store the status into a custom field on the "celigo shopify item id" custom record in NetSuite; and I was going to try to use that, but I haven't had a chance to yet. Any feedback is greatly appreciated.
Thank you,
Bryn Harvey
Hello Bryn Harvey
The setting I referred in my previous is actually related to the flow "Shopify Product Id to NetSuite Item Mass Update flow". It's just logically grouped under "Inventory" section, but it affects the Product ID mass update flow.
Having this setting unselected, the flow only picks the Item ID details of "Active" items and ignore the "Archived" items.
Hope this answers your query. Please review and let me know for any further queries.
Thanks You !!
I've tested this solution and I don't think it is correct.
Hello Cory Anderson
Thanks for the feedback. I have reviewed this again, yes you are correct. Basically Shopify handles a different parameter i.e., "Status" using which we can filter the Active, Draft & Archive products.
However with the setting we currently have in our IA, the parameter handled is different i.e., "published_status".
We will consider this as a product enhancement request and assign to our PM team to further review.
However, I would recommend here to build a simple Custom flow as similar to the existing IA flow, but just to add the "Status" parameter on top of the existing URI we have.
I am also adding Shopify help doc which I referred to
https://shopify.dev/docs/api/admin-rest/2023-04/resources/product
Please review and let us know for any further queries
Thanks,
Has there been any updates to be able to do this within the built in flow yet? Or is it possible to have someone from support add a filter in the relative URI to not allow archived products to avoid making an additional flow?
The Shopify Product ID to NetSuite Item Mass Update flow does not have a built-in feature to ignore archived Shopify SKUs. However, you might be able to achieve this by modifying the criteria of the flow or the saved search that the flow is based on.
Here's a potential workaround:
1. In NetSuite, create a custom field for items that indicates whether the item is archived in Shopify. This could be a checkbox field that is checked when the item is archived.
2. Update the saved search that the flow is based on to exclude items where this custom field is checked. This can be done in the Criteria tab of the saved search.
3. Run the flow. It should now ignore the archived items.
Please note that this solution requires that the archived status of items in Shopify is kept in sync with the custom field in NetSuite. This could potentially be achieved with another integration flow.
In case the above is not helpful, please create a ticket with support and the team will further take it up.
Please sign in to leave a comment.