WhatsApp Catalog Inventory Sync

Q: Do I need WhatsApp Business API to use catalogs?

Yes. Catalogs are only available on WhatsApp Business API, not the consumer or regular Business app. You'll need to register a business account, verify your phone number, and integrate via a provider (Meta's own Business Suite, Orin, Twilio, Infobip, or similar).

Q: How often can I update my catalog?

There's no official limit on updates, but WhatsApp recommends not pushing changes more than once per hour to avoid rate-limiting. For most teams, daily or every 4–6 hours is practical and sufficient.

Q: Can I show different prices to different customers?

Not natively in the catalog. All customers see the same catalog. If you need per-customer pricing (wholesale vs. retail, loyalty discounts), handle that during the checkout or invoice stage, or create tiered product listings in the catalog.

Q: What happens if a customer buys something out of stock?

WhatsApp doesn't prevent it. You'll receive the order, see that stock is unavailable, and need to contact the customer to cancel or backorder. Mitigate this by syncing inventory frequently (every 2–4 hours if volume is high) and being clear in your product descriptions about stock status.

Your customers are already on WhatsApp. They're asking about product availability, pricing, and delivery times in the same app they use to message their family. Meanwhile, your inventory lives in a spreadsheet, your prices are in an accounting system, and your sales team is copy-pasting product details into chat threads. WhatsApp catalogs fix this—but only if you actually connect them to real data. What WhatsApp catalogs do (and don't do) WhatsApp Business API lets you upload a catalog—a browsable product list that appears directly in chat. Customers tap through product images, descriptions, and prices without leaving WhatsApp. They tap "Add to Cart," you get notified, and the order details land in your inbox. What it doesn't do: automatically sync to your live inventory, update prices when costs change, or integrate with your payment processor. Those gaps are where most teams fail. They upload a catalog on day one, prices change on day two, and suddenly customers are ordering products at yesterday's price. The core problem: WhatsApp catalogs are static by design. Your inventory and pricing are dynamic. Without a sync strategy, your catalog becomes outdated noise. Three layers of sync you need to build 1. Inventory to catalog (what's live, what's out of stock) When you mark a product out of stock in your system, it should disappear or gray out in your WhatsApp catalog within minutes. Customers shouldn't browse something you can't sell. How to do it without custom code: If you use a spreadsheet or light inventory tool: Export your catalog weekly (or daily if you move volume) in JSON format that matches WhatsApp's schema. Store it in a Google Drive or cloud folder. Use Zapier or n8n to watch that file, and when it changes, push the update to WhatsApp Business API. This works for small catalogs (under 500 SKUs) and slow-moving inventory. If you use Shopify, WooCommerce, or a native e-commerce platform: Many have native WhatsApp connectors (Shopify's WhatsApp Sales Channel, for example). Connect once, and your catalog syncs on a schedule—usually daily or when you manually trigger it. Check your platform's app marketplace first. If you use a unified messaging platform: A platform like Orin that connects WhatsApp with your broader business stack can sync inventory directly from your accounting or CRM system. This is faster than Zapier for high-frequency updates and lower-latency for real-time stock changes. The key: pick a sync cadence that matches your inventory volatility. If you sell 50 units a day and restock weekly, daily syncs are enough. If you sell 500 units a day across multiple channels, sync every 2–4 hours. 2. Pricing in real-time (no stale rates) Prices should flow from your accounting or pricing system into WhatsApp. If you raise prices, discount a tier, or run a promotion, your catalog should reflect it immediately—or at least the same day. How to do it: Spreadsheet-first teams: Keep your pricing in a single Google Sheet or Airtable base. That's your source of truth. Export to WhatsApp catalog format, upload weekly (or whenever you change prices). Automations watch the sheet for edits and retrigger the export. Accounting software: If you use an invoicing tool that tracks unit prices and customer-specific rates , export that pricing list to your WhatsApp catalog builder. Don't duplicate pricing in two places—one is your system of record, the other is derived from it. Dynamic pricing (bulk discounts, volume tiers): WhatsApp catalogs don't natively support "buy 100+ and pay $5 per unit." You'll need to either (a) list tiers as separate products, or (b) show a base price in catalog and clarify volume discounts in your chat greeting. When a customer orders, capture quantity and apply the right rate during checkout. 3. Order capture and handoff (chat to fulfillment) A customer browses your catalog, adds items to cart, and presses "Send." What happens next? The order details land in your WhatsApp Business inbox, but they need to flow into your fulfillment system, CRM, and payment processor—ideally without manual copy-paste. How to close the loop: CRM integration: Connect your CRM to WhatsApp so that incoming orders create deals or line items automatically . Customer name, product SKU, quantity, and price should flow in. This keeps your pipeline clean and prevents duplicate data entry. Payment capture: WhatsApp itself doesn't process payments. You'll send a payment link (Stripe, Razorpay, Wise, or your processor) via WhatsApp or follow up with an invoice. Make the payment link as frictionless as possible—one click, mobile-optimized, same country currency if you're in Southeast Asia. Fulfillment routing: Once payment clears, trigger your fulfillment workflow. If you use Shopify or WooCommerce, an order should appear in your fulfillment queue. If you use a spreadsheet or basic system, a Zapier or n8n automation can email your warehouse team or add a row to a fulfillment sheet. The most common failure point: