How to fix Zapier test reporting negative quantities when quantities are sufficient in Square?

Hey ​@Meeting Greeb,

The error indicates that you can’t send negative value. Try sending 1 instead of -1 in quantity to adjust the inventory to see if it fixes your issue. Hope it helps!

Hi there ​@Meeting Greeb 👋

Did setting it to 1 instead of -1 as Sparsh suggested do the trick? 

Let us know how it went, want to make sure you’re all set! 

Hi there!

Thank you both, I was able to find the problem—the table wanted to list Wix SKUs and Square Catalog IDs and the table I initially created listed the same SKU code for both (seems intuitive, yes?).

I’m a little concerned as to how this Square Catalog ID/ Wix SKU configuration will work since 1. they are different ID’s and 2. the Square Catalog ID seems to only represent the product page, not the multiple variants that have individual SKU’s. I haven’t been able to find any material on this, so any further information would be greatly appreciated!

Hey ​@Meeting Greeb,

I think you will have to use Lookup Tables to match the Wix SKU to the correct Catalog Object ID. Here is a helpful article about creating Lookup tables- https://help.zapier.com/hc/en-us/articles/8496305146765-Create-lookup-tables-in-Zaps. Hope it helps!

Sorry for the delay in my reply here ​@Meeting Greeb. Great job on getting to the bottom of what was causing the issue! 🙌

Sparsh is correct, if it’s after the Catalog Object ID not the SKU then you’d need to create a lookup table to automatically convert the SKU value into the corresponding Catalog Object ID, since there’s no “Find Product” action available for Square. 

That said, if you’ve got a large number of products you might want to try using an API Request action to search for the product by it’s SKU to get it’s Catalog Object ID. Looks like Square’s Search catalog items endpoint would be the one you’d need to use for that: https://developer.squareup.com/reference/square/catalog-api/search-catalog-items. It’s a bit more advanced but you can ask Copilot to help build it for you, and I’d be happy to lend a hand if you get stuck.

Keep us posted on how it goes! 🙂

Sparsh and Sam,

Thanks so much for your insight. I previously had a look up table, but the Zapier customer rep I was speaking to said I didn’t need the table so it has been removed. I was told that I needed Variant IDs and after importing and testing on a specific item, it worked! However it is only working with the items that have ONE variant and not multiples. Squares set up gives the option of including a variant even if an item doesn’t have multiple variants, ie we are selling a single type of Rose Bush that is 16”. That 16” can still be added as a variant and has a Variant ID. If I try testing an item that doesn’t have any type of variant, it still doesn’t work—the same with testing an item with multiple variants. 

I’ve tried reformatting the table, but that doesn’t seem to work. I’m not sure if it is a formatting issue, or if I’m not calling the right columns in my table.

If the above sheds any perspective, please let me know!

Warmly,

Sarah

Happy to help ​@Meeting Greeb! 🤗

It’s odd that it’s only working for items with a single variant but fails for items with no variants or multiple variants. 🤔 I’d have thought that if you’ve got the SKUs for each variant in one column and the corresponding variant ID in another, then the Zap should be able to look up the correct row based on the SKU and pass the correct variant ID to the Change Inventory action. 

Can you share a screenshot of how you’ve got the table setup so we can see the current format of it? 

Sam,

My thoughts exactly! That is why I wondered if it was a formatting issue in the end, but Co-Pilot ended up using the exact format when I asked it to help me solve the issue. Here is the current layout:

And here is the format Co-Pilot used:

It may have just been trying to follow my formatting in the end. 

I did try an experiment where I laid out all of the variant codes into separate Variant 1, 2, 3, etc fields… but that didn’t seem to work either! I wonder if it could actually work if in the Zap itself I could identify those fields in the Catalog Object section?

Those new columns weren’t populating when I was running my experiment and now they are! I might give it a shot. 

Thanks so much!

To be clear—the new formatting I was thinking could work holds all of the values needed on one line horizontally, Original Bendable Coir Pole VS Plant Hanger: Light and Airy!

Thanks so much for sharing those helpful screenshots ​@Meeting Greeb.

With the formatting of the table to have each variation on a single record I’m not sure that’s the best approach, since the Zap would then need a way to determine which variant ID it should pick from the record. You could potentially use an AI action to determine which variant ID to select, but the name of the variant isn’t listed it’s just Variant 1, Variant 2, Variant 3 in the columns. So you’d then need some sort of list of the variant names and their corresponding IDs in order for the AI to know which to output.

And with the other format, if you’ve just got one record per variant then it should just search for the SKU and whichever record matches that would only contain the ID that corresponds to that specific SKU. 

Those new columns weren’t populating when I was running my experiment and now they are! I might give it a shot. 

Excellent! I’m so glad the values for the columns are now populating correctly. Please do give it a try and let us know if it works!