This one's specific enough that it's worth naming directly: if you've set up custom product filters and they won't save, check what you named your custom fields and options first.
BigCommerce's own filtering settings will silently fail to save if a custom field or option is named something like Category, Brand, or Price. Those words collide with the platform's own reserved filtering logic. It's not a bug exactly, it's a naming conflict, but from the merchant side it just looks like the save button doesn't work.
This is the kind of thing that's invisible until you know to look for it, and it usually shows up after a catalog has already been imported with whatever field names came over from a distributor feed or a previous platform. Nobody names a field Category expecting it to break filtering. It just does.
This is exactly the kind of small, specific landmine we check for on every catalog we bring on, before it ever goes live, not after a customer can't filter your site correctly. We've seen this exact failure before, which is the entire advantage of working with a team that's already run into the obscure stuff instead of discovering it for the first time on your store.
This is part of a pattern of issues that consistently show up on freshly migrated BigCommerce stores.
Filters still not saving? We know exactly why.
Talk to Us →