Wix Stores can run a catalog in the tens of thousands, and a custom front end can make that catalog quick to browse and search. It also has hard limits, and a large store runs into them unless they are planned for from the start. These are the ones we plan around on every big build, what each one means in practice, and what to check before you commit your store to Wix Headless.
The limits at a glance
| Limit | What it means for you |
|---|---|
| 50,000 products per site | Hidden products count toward it |
| 1,000 categories | Total across the whole category tree |
| 4 category levels | Anything deeper has to become a filter |
| 100 products per bulk removal call | Large cleanups happen in batches |
| Rate limits on bulk jobs | Send too fast and Wix answers with HTTP 429 |
| Media storage per site | Photos for a huge catalog may not fit |
50,000 products, hidden ones included
The product cap counts every product in the store, not just the ones shoppers can see. That catches stores that hide sold items to keep their pages around. In a business with steady turnover, such as used parts or one-of-a-kind stock, hidden products pile up quietly until the store can’t take new ones.
How we plan for it:
- Count the real number. Include drafts, hidden items, sold-out items and anything you mean to keep.
- Decide what happens to a sold item. Either remove it from the store, or keep a lightweight “sold” record outside the product catalog if those pages bring in search visitors.
- Leave headroom. If you are near the cap and adding stock every week, you have months to sort this out, not years.
- Use options where they fit. A part sold in five sizes can be one product with a size option instead of five products, as long as the items really differ only by that option.
1,000 categories, 4 levels deep
Large parts catalogs tend to want deep category trees. Wix allows four levels and 1,000 categories in total. Most catalogs fit once categories and filters each do their own job: categories for how people browse, filters for how they narrow down.
A four-level branch looks like this:
Level 1: Auto Parts
Level 2: Brakes
Level 3: Brake Pads
Level 4: Ceramic Brake PadsFront or rear, brand, condition and vehicle fit then become filters on that page, not a fifth and sixth level. A brand doesn’t need its own category either; a brand page can be built from a filter. Sketch the tree in a spreadsheet before the build and count the entries at each level. Our guide on how to organize a large parts catalog goes deeper on structure.
Bulk calls of 100 and rate limits
Wix’s bulk removal call handles 100 products at a time, so clearing 10,000 stale listings takes 100 calls. Wix also rate-limits bulk API jobs. Send requests too quickly and Wix replies with HTTP 429 (“too many requests”) until you slow down.
Any import or sync for a big store has to be built for that:
- send changes in batches, with a pause between them
- back off and retry when a 429 comes back, instead of failing
- record progress, so a job that stops can pick up where it left off rather than starting over
- after the first import, sync only what changed (new, edited, sold), not the whole catalog every day
If your products come from an eBay store or an inventory system, this sync is most of the technical work. Our eBay and inventory integration page covers how we set those up.
Media storage
A Wix site’s media storage is finite, and photos for tens of thousands of products, with several images each, can exceed it. One way around this is to serve product photos from the source’s own image servers, such as the images already attached to the listings in a feed, instead of copying every file into Wix. The trade is that the site depends on that source: if a listing’s images are removed there, they disappear from your site too. Check that the source allows this use before planning around it.
Other details that show up on big catalogs
- Product pages render on request. On Wix’s headless hosting, pages built from one template (every product page, every category page) must be rendered when a visitor asks for them. Pages generated ahead of time at those addresses return a 404 there.
- The first load after a release can be slow while servers start. Loading the main pages yourself right after each release means a shopper isn’t the first visitor.
- Sitemaps need their own plan. Wix controls
/sitemap.xmlon headless hosting, so a custom sitemap lives at another address. The sitemap standard allows 50,000 addresses per file, so a large store uses a sitemap index that points to several files. That custom sitemap also has to be added by hand in Google Search Console.
When Wix Headless is a good fit for a big catalog
- the catalog is under the cap with room to grow
- the category tree fits in four levels and 1,000 entries, with filters doing the rest
- the owner wants Wix’s dashboard for orders, payments and customers
- the products come from somewhere else (eBay, a supplier feed, an ERP) and sync on a schedule
- the store needs custom search, filters and page design that a template can’t give
That last point is the reason to go headless at all. Our Wix Headless development page explains what that build involves.
When it isn’t
- the catalog is already over 50,000 products, or will pass it soon
- browsing really needs five or more levels that can’t be flattened into filters
- every sold item has to stay in the store as a product, and turnover is high
- the photo library is too big for Wix’s storage and can’t be served from anywhere else
In those cases a platform built for very large catalogs may suit you better, and we would rather say so before the build than after.
What to check before you commit
- Export your full product list, including hidden, draft and archived items, and count it.
- Estimate how many products you add, and how many sell or retire, each month.
- Draft the category tree in a spreadsheet and count the entries at each level.
- List every filter shoppers will need: brand, size, condition, fit, price.
- Count photos per product and estimate their total size, and note where they are hosted today.
- Estimate daily changes (new listings, price edits, sales), because that sets the size of each sync.
- Confirm the Wix plan: a custom domain needs a premium plan, and so do payments.
- Import a small slice, a few hundred products, end to end before running the full catalog.
Your next step
Send us a product export, or a link to your current store with a rough product count, through our contact page. We’ll check it against these limits and tell you plainly whether Wix Headless fits, and what the build would need to handle. To see how these projects run, read about our Wix Headless development service.
