Hi Square Developer Community,
I am looking for clarification on the intended Square Catalog API behavior for variation-level location_overrides, specifically around sold_out and track_inventory.
We are seeing some variation location overrides returned like this:
{
"location_id": "LOCATION_ID_EXAMPLE",
"sold_out": true
}
In this example, sold_out is present, but track_inventory is not included.
We are trying to understand the correct way for an ordering integration to interpret this response.
Could someone clarify the expected behavior?
-
If Square sends
sold_out: truefor a variation at a specific location, should that variation be treated as unavailable for ordering at that location, even iftrack_inventoryis missing or false? -
Is
track_inventoryonly meant to indicate whether inventory counts are being tracked, or should it also control whethersold_outis honored? -
If
sold_out: trueis present buttrack_inventoryis omitted or null, should integrations still treat the variation as sold out? -
For an item with multiple variations, if only one variation has
sold_out: true, should only that variation be unavailable while the other variations remain available? -
Are there any cases where Square would return
sold_out: truebut still expect an ordering integration to allow that variation to be purchased?
We want to make sure our ordering behavior matches Square’s intended API behavior for location-specific variation availability.
Any official guidance or documentation links would be appreciated.
Thank you.