As of last week the new items I am adding to my Square Online inventory are not getting the default fulfillment methods automatically applied. I already have configured the default item fulfillment in Website settings > Item preferences > Fulfillment methods to default to Shipping and Pickup, but as of last week these are no longer automatically getting applied.
Was there a change recently that impacted this? Thanks for your help.
@rhythmicequations Do you have an example order ID we can take a look at?
@josh-square the issue is with inventory items fulfillment methods not syncing to Square Online. Here is an item-id from my inventory library: BLOH3D54AYHFNAGPFWG5VZXO.
From the library page, if I right click this item and click “update fulfillment methods” I see the default fulfillment options aren’t configured.
But when I open the inventory item and navigate to “edit online fulfillment methods” from the inventory item page, I can see the default fulfillment methods are set for this item.
Unfortunately, in my webstore my items are appearing as “Unavailable” unless I set the fulfillment method from the library page (1st option above). If I don’t the items appear unavailable.
This just started happening sometime last week.
@josh-square here is a view of the fulfillment options for item BLOH3D54AYHFNAGPFWG5VZXO. You can see the online fulfillment methods are not set.
Here is a view of the fulfillment options for item BLOH3D54AYHFNAGPFWG5VZXO when I double click the inventory item and select “Edit online fulfillment methods” they are set correctly, but the item shows unavailable.
Thanks for clarifying @rhythmicequations! Since this is not an issue related to Square’s Developer platform, I’d recommend you get in contact with Square Customer Support for assistance here. If you’d prefer a forum-format, you can use the Square Seller Forums.
@josh-square I already opened a case 4 days ago and haven’t received a response. The case # is 117291643. In the case auto-reply there was a recommendation to check out the developer forums. So I’m honestly feeling a little confused at this point. Would appreciate some level of support instead of tossing me back and forth.
@rhythmicequations Sorry for the confusion! It sounds like you submitted a developer support request. For these questions that aren’t related to Square’s developer platform, you’ll be better assisted by Square’s more (non-developer) customer support team, linked above.
I am having the exact same issue. Is there any chance you’ve determined some kind of workaround to fix the items that are showing as Not Available?
@basil_software unfortunately not . I have just been manually adding the fulfillment methods for the last several weeks, very frustrating. I have a support case open which I just shared your post with them as well. Maybe they will finally see that I’m not the only user affected and try to find root cause. @josh-square I know you aren’t the support team, but any help you can provide here would be appreciated. You are the only person inside Square who can at least help us pull levers / escalate this internally. We really need some help over here.
@rhythmicequations are you adding items directly into square or are you using a 3rd party integration?
@josh-square I have the exact same issue as @rhythmicequations . Items that are being pushed into Square since the 21st do not have any online fulfillments defined. I am using the API to upload catalog items and prior to the 21st I didn’t have any issues with items uploaded to square. I don’t see any change to the API documentation to suggest that I would need to somehow set these values so I’m at a loss as to how to actually fix the issue.
My customers are obviously frustrated by this issue and I have no idea how I can actually address it because nothing changed on my side. Can you point me in the right direction?
I am also using the Square API to add items. @basil_software
@josh-square I’ve used the both the php sdk and the ruby sdk to push new items to square and they both end up with the same issue. Which seems to me to prove that anyone using the API will have this issue.
For Ruby:
Ruby version: 3.3.0
Square Ruby SDK version: 45.0.2.20260122
For PHP:
PHP version: 8.1+
Square Php SDK version: 45.0.0.20260122
Here’s the data being sent:
catalog_object = {
type: ‘ITEM’,
id: ‘#test-item-123’,
present_at_all_locations: false,
present_at_location_ids: [LOCATION_ID],
item_data: {
name: ‘Test Product’,
variations: [
{
type: ‘ITEM_VARIATION’,
id: ‘#test-variation-123’,
present_at_all_locations: false,
present_at_location_ids: [LOCATION_ID],
item_variation_data: {
name: ‘Default Variation’,
sku: ‘1234567890’,
pricing_type: ‘FIXED_PRICING’,
price_money: { amount: 1999, currency: ‘USD’ },
sellable: true,
track_inventory: true,
stockable: true,
}
}
]
}
}
I can provide more details if that will help.
Hey folks, thanks for the additional info here — sorry, I didn’t realize you were creating these items via API specifically! I’m working on reproducing this on my own account.
Just to confirm, is the online fulfillment method the only thing that’s being updated when you’re making these items available manually, or are there other updates on top of that (e.g. menus and categories)?
@josh-square All I do is open the item and then save it. It looks like the page will create those on it’s own and when I push save, the online fulfillment methods are created for the item and the item becomes available online. Or if I set those manually from the List view of the items, that works as well.
Thanks for confirming! It looks like this is happening due to item visibility being powered by Channels. Since items created via the Catalog API do not have channel assignments, they’ll show as unavailable in Square Online. Unfortunately these fields are currently read-only; the only way to work around this right now is to manually update the items in Dashboard as you’ve been doing.
I definitely understand that the manual work is a painful experience, and we’ve surfaced this feedback to the engineering team! We’ve put in a request to make these fields writeable, but I do not have any information right now on if/when that can be implemented.
Thanks for the info @josh-square. I am seeing Channels is in Beta release. Any consideration to rollback until this issue is mitigated or a writable field exists in Channels? This manual workaround is quite terrible, I add several hundred items a day. I’ve had several of my customers reach out to me about my items showing unavailable on the site. It’s costing me money and I’m sure others too. This could have been coordinated better, communicated better, and impact better assessed proactively rather than reactively. Considering the $ I pay this platform in fees I expect a resolution, not a workaround. Please
@josh-square thanks for the information and the escalation on this issue. I have a competitor that’s claiming that their implementation using the same APi somehow isn’t affected by this issue. Is there any chance that’s actually true?
@rhythmicequations This is not something that will be rolled back, as Channels were part of a broader change with how visibility is handled in Square. I definitely hear you on the pain of this though, especially with the volume of items that you’re adding, and I’m communicating that to our teams internally as well.
@basil_software This change should have happened across the board, so I don’t think that’s true.
