Integration challenges with large number of Variants
For my current Squarespace site I have a fairly large number of items with many variants and variant options. Currently I am using SKU as the unique identifier for the integration. The issue is that the SKU is a random number for most items which makes it very difficlut to search for items in Quickbooks Online. I was in contact wiht support and the integration does not support syncing variant option attributes. The suggestion was to put some coding for the SKU. This was a "1980's solution" before relational databases existed and is not a recommended practice as it quickly becomes unmanagable. For now I have no choice and I will need to rename the SKU’s in Squarespace so that I can quickly find them in QuickBooks. This leads me to my first question
- Is there an easy way to rename the SKU values in Squarespace on the next integration cycle not create a large number of duplicate items in Quickbooks?
Going forward, from what I see in Squarespace each product has a unique “ProductID” and “Variant ID”. If there are multiple Variants, the Variant ID value is unique across all products in the Squarespace instance. Is it possible to add the following as an option/enhancement:
- Allow for variant option values to come across to Quickbooks Online
- Make the integration unique ID/key based on the "Variant ID". That way if the SKU or any attribute on the product changes it will not impact the integration and have the SKU
-
Official comment
Hi Pete, thank you for your feedback.
To answer your first question, if you are looking to rename your SKU values in Squarespace, then in order to prevent a duplicate item being created in QuickBooks you will also need to manually update your item SKUs in QuickBooks so they will match up on the next sync. I do recognize that this isn't a very elegant solution. Sorry.
As for utilizing the "Product ID" and "Variant ID" attributes from Squarespace, the issue here is that these values are system-generated by your specific Squarespace instance. Often the main use case of our integration is to allow businesses to match up the same items being sold across multiple sales channels. E.g. You might have 2 Squarespace stores, or an eBay listing for the same items. In these scenarios we cannot rely on Product/Variant IDs as they would never match between systems.
We are actively discussing internally how to better improve the way we handle product variants/combos/partial items etc within the QuickBooks system, but in the meantime our recommendation around how you structure SKUs aligns with that of Squarespace as well.
Hope this helps, if any further questions please don't hesitate to get in touch with our team via qbo-integrationsupport@intuit.com.Comment actions
Please sign in to leave a comment.
Comments
1 comment