WhatsApp Storefront: From Catalog to Checkout in Chat

It is 9 pm on a Tuesday: a shopper taps your number from an Instagram story, asks one question, opens a product card you sent, adds two items to a cart, pays through a link, and gets a confirmation — all without leaving the chat. That is a WhatsApp storefront doing quiet, profitable work while your website waits for traffic that never comes.

This guide is for the people who run that loop: what a storefront on WhatsApp is, how the free native catalog compares to a full storefront, and how to move an order from "interested" to "delivered" without drowning your team.

TL;DR

• The native WhatsApp catalog is a free product list attached to your profile — fast to set up, but weak on carts, payments, inventory, and analytics.
• A full storefront adds product pages, shareable links, a real cart, and checkout, with orders captured server-side so automations fire the moment someone buys.
• Merchandising in chat rewards short product cards, clean collections, and visible prices — not walls of text.
• Order operations run as a loop: confirm, collect payment, fulfill, update the customer — then start the next conversation.
• Chat-commerce beats a website for repeat purchases, high-consideration sales, and small-to-medium catalogs; it loses on huge catalogs and search-driven discovery.

How selling inside WhatsApp actually works

Every WhatsApp selling setup, from a kirana store to a D2C brand, is built from the same three moves: show products, collect choices, confirm the order. What separates a scrappy catalog from a real storefront is how much of that loop lives inside the chat versus on a page behind a link — and, crucially, who keeps the records.

The catalog layer

The catalog is WhatsApp's native product list. Each item gets a name, image, price, description, and optional link, and the whole list hangs off your business profile where anyone can browse it. In supported markets, shoppers can select multiple items and send them to you as a single order message. It costs nothing and takes an afternoon to set up, which is why it is where most small sellers start — and where a surprising number of them stall.

The storefront layer

A storefront moves browsing and checkout onto mobile-first product pages that you link to from chat. The customer still lives in WhatsApp — product cards, questions, payment nudges, and receipts all arrive as messages — but the store itself is structured, and the order is captured server-side the moment it is placed. That last detail is the whole game. An order that lands in a database instead of a chat bubble can trigger a confirmation template, tag the contact in your CRM, assign the chat to the right agent, and feed your revenue numbers. Platforms like Whaterakt offer these storefronts on top of the official WhatsApp Business API, so the store and your shared team inbox share one view of the customer.

The native catalog: what it does well, where it stops

Start with the catalog anyway, because free and native is a hard combination to beat for validation. If twenty catalog browsers a week turn into five orders, you have proof of demand; if they do not, you have saved yourself a build.

What it does well

• Zero cost and near-zero setup — items go in from the Business app in minutes.
• Always attached to your profile, so every conversation has a passive shop in the background.
• Multi-item orders arrive as one structured message in supported markets, instead of ten separate "I want 2 of this" texts.
• Forwardable — a happy customer can share your catalog into a group chat, which is distribution you did not pay for.

Where it stops

• One catalog per number, capped around 500 items as of writing — check current limits before planning a big migration.
• No inventory sync: sell out of something and the catalog will happily keep offering it until you edit it by hand.
• Variant handling is cosmetic at best; sizes and colors usually become separate line items and separate confusion.
• The "order" is a message to a human, not a checkout — no payment capture, no order state, no receipt.
• Analytics are thin: you cannot see which products were viewed, added, or dropped.

None of these are fatal on day one. They become fatal at scale, which is the honest way of saying the catalog is a brochure, not a store.

Upgrading to a full storefront

What the storefront adds

The upgrade is less about looks and more about data. Product pages give each item a permanent, shareable URL you can drop into any chat, campaign, or ad. The cart persists across sessions instead of evaporating with the conversation. Checkout collects payment through your gateway or UPI flow. And every step — view, add to cart, purchase — becomes an event you can act on rather than a scroll you hope happened.

How orders get captured

The flow looks like this: a shopper taps a product card in chat, lands on the product page, checks out, and the order event fires into your commerce platform. From there automation takes over — confirmation template, CRM update, team assignment — and, when someone abandons instead of buying, a recovery sequence. That last one is worth its own deep dive in our WhatsApp cart abandonment playbook.

Merchandising in a chat window

Chat compresses attention to one screen and one thumb. Merchandising that works in a browser aisle often dies in a thread, so adjust accordingly.

Product cards that earn the tap

• One strong image per card — the product in use beats the product on white, more often than not.
• One line of benefit, not a spec dump; the specifications belong on the product page.
• Price visible up front. Hidden prices filter out some buyers, but they also annoy the rest and slow every conversation down.
• A link to the full page for anyone who wants detail without a conversation.

Collections beat one long list

A hundred items in a single scroll is not a catalog, it is a punishment. Group products into collections of five to ten — by use case, season, or price band — and feature one collection per message. Rotate the featured collection with your campaigns, and use broadcast campaigns with approved templates to push a collection to a segment without messaging the whole list.

Prices, offers, and "DM for price"

Show prices wherever you can. If a category genuinely needs quoting — custom work, bulk tiers — say so plainly and give a starting range so you filter inquiries before they reach your team. For offers, anchor against the regular price rather than floating percentage discounts, and keep bundle logic simple enough to explain in one sentence.

Order operations: confirm, pay, fulfill, update

Storefront or not, the order loop is where chat sellers win or lose their margins. Run it as four steps and time each one.

1. Confirm fast. Reply within minutes during business hours: restate the items, the total, the delivery window, and any clarifying question. Speed here sets the tone for everything after.
2. Collect payment. Send a payment link or UPI option while intent is warm — every hour between "yes" and "paid" leaks orders. The mechanics deserve their own treatment in our WhatsApp payments guide.
3. Fulfill with context. Assign the order, pack, and ship, keeping notes in a shared inbox so the next agent who picks up the chat knows what was promised and when. This is the quiet argument for a team inbox over one overworked phone.
4. Update proactively. Send approved utility templates at each milestone — confirmed, shipped, out for delivery, delivered. Customers who are updated rarely chase, and customers who never chase cost less to serve.

When chat-commerce beats a website — and when it doesn't

Chat-commerce wins when the conversation is part of the product. That covers more ground than people expect.

• Repeat purchase and replenishment: the customer already has the thread; a two-line nudge with a product link beats a funnel.
• High-consideration purchases: jewelry, appliances, travel, B2B services — anywhere questions close sales.
• Small-to-medium catalogs: up to a few hundred SKUs, merchandised well.
• Local delivery and services: where the buyer wants a human, a time, and a total, in that order.

It loses, honestly, in three cases: catalogs so large they need search and filters; businesses whose growth engine is search-driven discovery, where a website compounds and a chat does not; and self-serve returns or exchanges at a volume that would swamp a human inbox. Plenty of D2C brands run both — the website as the front door, WhatsApp as the conversion and retention engine — and feed the chat with click-to-WhatsApp ads when they need new blood.

FAQ

Is selling through a WhatsApp storefront allowed by WhatsApp?

Yes, when it runs on the official WhatsApp Business API or the Business app's native commerce features. What risks bans is unofficial bulk tooling that violates the platform's terms — the same rule that applies to any WhatsApp commerce, storefront or not.

Can customers pay without leaving WhatsApp?

It depends on your country and setup. Native payments inside WhatsApp exist in some markets, while most sellers today send payment links, UPI details, or QR codes in chat. The checkout on a full storefront can also capture payment directly.

How many products can the native catalog hold?

The catalog supports up to about 500 items as of writing, though limits change over time. Verify the current number on WhatsApp's Help Center before committing to it as your only store.

Do I need the API to run a storefront?

You need only the Business app catalog to start. You need the API — usually through a platform like Whaterakt, whose storefront and inbox features are built on it — once you want automation, multiple agents, order events, and analytics.

How do I get traffic to the storefront?

The usual suspects, adjusted for chat: click-to-WhatsApp ads, links in bio and packaging, QR codes at the counter, and broadcasts to opted-in contacts. The storefront converts; traffic is still your job.

Can I run a website and a WhatsApp storefront together?

Yes, and many brands do exactly that. Treat the website as the catalog and discovery layer, and WhatsApp as the channel where questions get answered, carts get recovered, and repeat purchases happen.

A WhatsApp storefront is not a smaller website; it is a different machine — one where the conversation is the storefront and every order leaves a thread you can serve from. Start with the catalog to validate, upgrade when the manual work starts costing sales, and run order ops like the loop they are.

When you are ready for the full version — storefront, shared inbox, and automation on one platform — Whaterakt's plans start with a free tier.