The 500-product figure you see everywhere is not in WhatsApp's own documentation. The constraints that actually fill up a catalog are approval, variants and one profile.
Search for the WhatsApp catalog limit and almost every result says 500 products. WhatsApp itself does not. We checked its Business help center, including the About catalog and How to create and maintain a catalog pages, and neither publishes a maximum item count. What they do document is a set of constraints that bite far earlier than any number would.
This matters because the wrong diagnosis sends you rebuilding the wrong thing. Most shops that think they have hit a product ceiling have actually hit the approval queue, a missing country of origin, or a catalog nobody can navigate. Those have different fixes.
Short version: there is no documented cap on WhatsApp catalog items. The real limits are operational: every item needs a unique title, an image and a country of origin; every image is reviewed before customers can see it; one business profile shows one catalog, subdivided with collections. Hit a wall? Check approval status before you check the count.
The constraints WhatsApp actually documents
These come straight from the WhatsApp Business app flow. Note how many of them are about visibility rather than quantity.
| What WhatsApp documents | Detail | Why it fills up your catalog |
|---|---|---|
| Required fields | Unique title, at least one image, country of origin | An item without origin cannot be saved, so drafts pile up |
| Optional fields | Price, sale price, description, website link, product code | Price display is limited to certain countries |
| Images per item | Up to 10, plus video | Use angles instead of duplicate items |
| Image review | Every uploaded image is checked against the Business Messaging Policy | A rejected image hides the whole item |
| Approval before visibility | Items are only visible to customers once approved | Your catalog looks empty to buyers while full to you |
| One catalog per profile | The catalog is displayed on the business profile | Retail and wholesale cannot be split by catalog |
| Collections | Group items inside one catalog | The sanctioned way to subdivide |
| Hide instead of delete | Hidden items stay in the manager, marked | Seasonal stock can leave the shop window without losing its record |
Country of origin is the one that trips people up. WhatsApp's own note is explicit that you must select it when adding a new item or editing an existing one. If an item suddenly stops saving, that is usually the reason.
Why the 500 figure keeps getting repeated
Third-party tools and app-store listings quote 500, and the number spreads because it is convenient: it gives a seller a countdown. We are not saying it is invented — app behaviour changes and caps surface in the client long before help pages mention them. We are saying it is not in WhatsApp's documentation, so it should not be the number you plan a catalog strategy around.
The practical consequence is that you cannot test your way to the truth by watching for a hard stop, because the constraints above stop you first. A shop with 300 items can be visibly broken to customers while a shop with 600 is fine.
What actually makes a catalog feel full
- The approval queue. Every image is reviewed, and nothing a customer can see exists until it passes. Add forty items in one sitting and you have forty reviews in front of you.
- Rejections you have not noticed. A rejected item shows a red exclamation mark beside the image. It stays in your manager looking saved, while showing nothing to buyers.
- Variants modelled as products. No size or colour field exists, so a shirt in six sizes becomes six items. This is how a 90-product clothing shop ends up with 540 entries.
- Dead listings kept just in case. Discontinued items you hide rather than delete still need origin fields and still get reviewed.
- One catalog, many audiences. A shop selling retail and trade has to choose which price list the public sees.
When an item is rejected, do this
The appeal path is documented and most sellers never use it. Against WhatsApp's own instructions: open the rejected item, choose request another review, and give your reason. If that is refused and you have re-read the Business Messaging Policy, you can reply to request a third review.
- Check the image first. Text overlays, watermarks and price stamps are the usual cause.
- Remove anything that looks like a claim about a regulated product before appealing.
- Do not re-upload the same image repeatedly. Edit it, then request review.
- Keep a private note of which items are pending so you know what you are actually selling today.
Use collections instead of a second catalog
Collections are WhatsApp's supported answer to catalog size. They group items inside the same catalog so a customer can jump to what they want, and they are documented in create and manage collections in your catalog. Build them the way a customer shops, not the way your stockroom is laid out: bestsellers first, then the categories people ask for by name.
What collections do not solve is pricing for two audiences. A trade list and a public list in one catalog is one price list with a concealment problem. For that, turn your wholesale price list into a shareable catalog is the honest route.
How to keep a growing catalog under control
- Fold variants into the description where the choice does not change the price. Sizes and colours stated in text cost you a clarifying message and save you five items.
- Hide seasonal lines instead of deleting them. Hidden items keep their record and return with one edit, which beats re-shooting and re-submitting in six months.
- Audit by last-edited date quarterly. Most catalogs carry more dead stock than the owner expects.
- Give every item a product code. The optional field exists for this, and it is what lets you find the item again mid-chat.
- Add the ten angles before you add ten items. One item with four photos beats four near-duplicates.
When to move to a hosted catalog
The trigger is not a number. It is when the platform's shape starts deciding how you sell.
| Symptom | Built-in WhatsApp catalog | Hosted catalog link |
|---|---|---|
| Variant-heavy range | One item per variant, no options field | Options and quantities captured with the order |
| Two price lists | One catalog per profile | Separate stores, one login |
| Item changes | Image re-review each time | Edit once, live immediately |
| Found by Google | No, it lives inside the app | Yes, it is a web page |
| Order arrives as | A message describing items | An itemised order with total |
| Customer pays | Arranged separately | Arranged separately, with the order recorded |
MyShp puts no ceiling on products: unlimited products with 0% commission and no review queue between you and a live link. If you are still deciding between the two approaches, WhatsApp Business catalog vs a catalog link compares them properly.
Next steps
Before you rebuild anything, open your catalog manager and count what is actually visible to customers, not what you have saved. If that number is lower than you expected, the problem is review and required fields, and WhatsApp catalog not working: six fixes walks through it. If the count is fine and the shape is wrong, create a hosted catalog and move the variants into a real product page.
Frequently asked questions
WhatsApp does not publish a maximum number of catalog items. Its own help pages describe the fields each item needs and how items are reviewed, but state no ceiling. The number 500 is widely repeated across third-party guides and app-store listings rather than in WhatsApp documentation.
Written by MyShp Editorial Team
We write practical guides for independent sellers, home businesses, and small shops taking orders on WhatsApp.