WhatsApp Business catalog not updating in the customer's view: what it means and how to fix it

If the WhatsApp Business catalog does not update in the customer's view, this is what is happening: you already changed the price, the photo, or removed a product, but the person messaging you still sees the previous version. It is not an error that breaks the account or leaves you without service: WhatsApp keeps working, messages go in and out. The problem is that the catalog your customer sees does not match the one you have loaded. In most cases it is fixed from the phone or from the Meta panel, without touching a single line of code. In others, the old catalog is not the cause but the symptom that you are editing in a different place from the one being displayed. Below is how to tell one case from the other and what to do in each one.

What it means exactly for the catalog not to update

A WhatsApp Business catalog is a list of products with photo, name, price, description, and link. That list lives in one place (your business account, your commerce manager, or your e-commerce platform) and is displayed in another (the customer's chat, your profile, the messages you send with attached products). When those two places get out of sync, the problem appears: the customer sees a photo you already changed, a price you already raised, or a product you no longer sell.

Take a concrete case from the food industry: you change the price of the milanesa napolitana in your point-of-sale system, but the WhatsApp catalog still shows last week's value. A customer orders through the chat, confirms the old price, and when the bill arrives there is a difference. It is not a code error or an API message: it is a mismatch between what is published and what is displayed. That is why you will not find an error number that identifies it: what you see is the consequence, not the failure.

Why it appears: the most common causes

Before touching anything, it is worth understanding where the catalog the customer sees comes from. Almost always the problem starts in one of these five places.

• You are editing in one catalog and the customer sees another. Many accounts have more than one catalog associated (an old test one, one left over from a previous integration). If you edit the one that is not connected to the number, the change never arrives.
• The catalog is fed by an external source that was not updated. If you uploaded the products from a spreadsheet, a CSV, or an e-commerce platform, the WhatsApp catalog shows what that source had the last time it synced. Changing the price in WhatsApp does not change the source, and the next sync can revert everything.
• The product was left in draft or pending status. A product that is loaded but not published is not shown to the customer. If you created it and do not see it on the other side, check the product status, not the entire catalog.
• The customer has the chat open with the old version. WhatsApp caches part of the content on the phone. If the person had the catalog open before the change, they may keep seeing the previous one until they refresh or re-enter.
• You are looking at the wrong view. The catalog the customer sees in the chat is not always identical to the one you see in your admin panel. They are two views of the same data, and sometimes one updates before the other.

If the catalog comes from an external source, the order of operations matters: first the source is updated, then it is synced, and only then do you check what the customer sees. Doing it the other way around is the number one cause of a change 'not saving'.

How to fix it step by step

These steps can be done by the business owner or someone on the team without technical knowledge. There is no need to touch tokens or webhooks. If at any step you run into something you don't understand, note where it happened and continue with the next one: many times the problem gets resolved further along.

1. 1Confirm which catalog is connected to the WhatsApp number your business uses. Go to Meta's commerce manager and check which one appears as the catalog linked to your WhatsApp Business account. Write down its exact name.
2. 2Open that catalog, not another one. If you have several, open the one you wrote down in the previous step. Verify that the product you want to change is there and not in a sibling catalog.
3. 3Check the product's status. If it says draft, pending, or rejected, publish it or fix what Meta requires. An unpublished product is not shown to the customer, even if you see it in your dashboard.
4. 4If the catalog is fed by an external source (spreadsheet, CSV, e-commerce platform), update the source first and then force the sync from the commerce manager. Do not edit the product directly in WhatsApp if it is going to be synced again: the next sync overwrites your change.
5. 5Save and wait. Changes are not instant. Propagation time varies by case and is not guaranteed by Meta. Do not repeat the change three times in a row: that can create duplicate versions.
6. 6Ask another person (or another phone of yours) to open the chat with your number and look at the catalog. Do not look at it from your own phone with the session open: the local cache may show you the old version.
7. 7If after this the customer still sees the previous version, ask them to close the chat, exit WhatsApp, and open it again. In many cases the problem is the customer's phone cache, not your catalog.
8. 8If none of the above changes what the customer sees, take a screenshot of what you see in your dashboard, another of what the customer sees, and write to Meta support with both. At that point it is a case to escalate.

How to prevent it from happening again

An outdated catalog is almost always a process problem, not a tool problem. These practices greatly reduce how often it happens.

• Define a single source of truth. If the catalog is fed by a spreadsheet or your e-commerce, every price or stock change is made there, not in WhatsApp. Editing in two places is the fastest way for them to get out of sync.
• Close old or test catalogs. An orphan catalog that is still linked is a trap: sooner or later someone edits the wrong one.
• Check product statuses after every bulk upload. Products left in draft are not shown and often go unnoticed until a customer asks about something that 'is not there'.
• Test the catalog from a phone that is not yours. Keep a test device on hand to verify how a real customer sees it.
• Note when you make big changes (prices, season, product removals) and check the catalog the next day, not at the moment. That way you detect the lag before the customer does.

When the real problem is something else and the catalog is only the symptom

There are situations where the catalog doesn't update because the problem is in another layer. If you already followed the steps and the customer still sees the old version, check these possibilities before starting over.

• The customer is looking at an old message, not the catalog. If you sent them a product attachment weeks ago, that message keeps the photo and price from that moment. The updated catalog doesn't change messages that were already sent. For that, you need to send a new one.
• The problem is with the business account, not the catalog. If your WhatsApp Business account has any restriction or pending verification, some catalog features may not reflect properly. In that case the catalog is the symptom and the problem is the account.
• The number the customer is using isn't the one you think. If you have several numbers (sales, support, branches), the customer may be looking at the catalog of another number. Confirm which number they wrote to you from.
• The catalog is fine and what's failing is the customer's view. If your dashboard shows the correct version and several customers see the correct version but only one sees the old one, the problem is that phone's cache. Don't touch the catalog.
• You're editing on a platform that doesn't sync with WhatsApp. If you uploaded products to your own system or a third-party tool that isn't connected to the WhatsApp catalog, those changes will never appear. Verify that the connection exists.

What you should NOT do

When the catalog doesn't update, the natural reaction is to touch everything. That usually makes the problem worse. Avoid these three things.

• Don't delete and recreate the product several times. Each attempt can leave overlapping versions and make it harder to know which one is the right one.
• Don't switch catalogs without checking what's connected. If you disconnect the active catalog, the customer may stop seeing products altogether.
• Don't assume the problem is WhatsApp. Most of the time the mismatch comes from the external source or from editing the wrong catalog.

How this relates to replying on WhatsApp

An outdated catalog generates questions: 'is this price still valid?', 'do you have stock?', 'can you send me the new photo?'. If the business receives many messages on WhatsApp, those inquiries pile up and someone has to answer them one by one. Tools like Wando, which suggest replies with AI on the official WhatsApp API, help the team avoid wasting time answering the same thing over and over, but they don't replace reviewing the catalog: if the data is wrong at the source, no automatic reply fixes it.

Summary to resolve it today

• Confirm which catalog is connected to the correct number.
• Check that the product is published and not in draft.
• If there is an external source, update it first and then sync.
• Verify from another phone, not from yours.
• If the customer still sees the old version, ask them to close and reopen the chat.
• If nothing changes, escalate to Meta support with screenshots of both views.