Workaround needed on max. 128 elements per metafield

Technical Q&A

Topic summary

A large catalogue store with 2,500+ SKUs has hit the 128-element limit on a product metafield used for their advanced filtering system. This limitation is blocking their ability to expand their product catalogue further.

Proposed workarounds:

  • Split the single metafield into multiple metafields and update the filtering logic to query across all of them
  • Build a custom app that stores the data in an external database (Prisma, Supabase, etc.), though this requires development resources

Status: The issue remains unresolved, with the store currently unable to grow their catalogue until a solution is implemented. Images show the filtering interface and the Dutch-language error message about the element limit.

Summarized with AI on October 27. AI used: claude-sonnet-4-5-20250929.
1

Hi,

We’re a large catalogue store with 2.500+ SKU’s and in our store we have an advanced filtering system to help customer find the correct product. These filters use product metafields to categorise products.

Olaf2_0-1749547899632.png
Olaf2_0-1749547899632.png2521×744 216 KB

However, we have now reached the limit of 128 elements for a particular metafield that we are using.

Anybody else facing the same issue and know about a workaround or alternative solution? At this moment we’re stuck with growing our catalogue, so any help is much appreciated.

Olaf2_0-1749546753970.png
Olaf2_0-1749546753970.png1137×183 13.3 KB

Sorry it’s in Dutch

Thanks.

Olaf

2

Hi,

I think one option would be to split the one metafield into multiple metafields. Then adapt your filtering logic to read from multiple metafields.

Another option would be to build a custom app that stores data in an external database (like prisma, Supabase, etc…). This, however, will require some coding knowledge or hiring a developer.

Hope that helps.