Commerce · Catalog

A catalog that matches your store, always

WhatsApp commerce only works when the catalog is current. SabNode Catalog Sync mirrors your Shopify, WooCommerce, Stripe or Google Sheets product feed into the WhatsApp Business catalog — with inventory, pricing, images and variants updating in near real time, plus a rollback log when something breaks.

  • Two-way sync with Shopify, WooCommerce, Stripe
  • Updates push within 60 seconds of a store change
  • Inventory, price, variants and images covered
  • Rollback any sync run from the history log
The problem

A stale catalog burns brand trust

WhatsApp commerce promises a frictionless path from chat to checkout, but only if the catalog is right. The moment a customer taps a product in chat, sees a price that has changed, an image that no longer matches, or a "buy" button that leads to an out-of-stock item, your conversion rate collapses and your support load doubles. Every operator who has tried to maintain a WhatsApp catalog manually knows the pain: edit a product in Shopify, remember to update WhatsApp Manager, forget half the time, get yelled at by a customer the next day.

It gets worse with variants and bulk SKUs. A fashion brand with 600 SKUs across colours and sizes cannot manually sync. A grocery operator with daily price changes cannot manually sync. Stripe-only sellers using Payment Links have no native WhatsApp catalog at all, despite running their entire checkout through it. The result is that WhatsApp commerce becomes a "we will reply with options" workflow — slow, agent-heavy and no better than email.

A working catalog sync is operational glue, not a feature. It needs to push inventory changes within seconds, handle variants and image URLs properly, validate Meta's catalog rules before submission, and provide a rollback when a bad sync run nukes your live catalog at 3pm on a Saturday. Anything less is a liability disguised as automation.

What it is

Catalog Sync, in depth.

SabNode Catalog Sync is a two-way bridge between your source of truth (Shopify, WooCommerce, Stripe, Google Sheets) and the WhatsApp Business catalog attached to your WABA. When a product changes in the source — a price, an image, an inventory count, a variant added — we detect the change via webhook or scheduled poll, transform it into Meta's catalog schema, validate it against Meta's rules and push the update. Typical end-to-end latency is under 60 seconds for webhook-supported sources.

Variants are handled properly. A Shopify product with three sizes and four colours becomes 12 catalog items in WhatsApp with the right naming, SKU mapping and pricing. Inventory is respected — items going out of stock are flagged unavailable so they stop appearing in catalog messages and product flows. Images are mirrored to a CDN-backed origin to keep load fast inside the WhatsApp client.

Sync runs are auditable. Every run logs which products changed, what fields, what Meta returned and how long it took. If a run pushes a bad update (a wrong price, a broken image URL), one click rolls back to the previous catalog state. For high-stakes catalogs we support a review mode where changes queue for human approval before they hit WhatsApp.

The catalog is not a dead asset. Once synced, products are available to the Flow Builder, AI Studio, broadcasts and the orders module. A customer can ask "do you have this in red?" in chat, an AI agent can pull the variant from the catalog and send the product card with a Buy Now button. Sales close in chat, payments go through Razorpay or Stripe, and the order syncs back to Shopify automatically.

Capabilities

Everything you get with Catalog Sync.

7 capabilities
01

Webhook-based real-time sync

When Shopify, WooCommerce or Stripe pushes a product or inventory webhook, SabNode picks it up and updates WhatsApp within seconds. No polling lag, no nightly batch — what changes in the store changes in chat almost immediately.

02

Variants and SKU mapping

Shopify variants, WooCommerce attributes and Stripe SKUs are normalised into Meta's catalog schema. Each variant becomes its own catalog item with proper naming, inventory and pricing, so customers can pick the right size or colour in chat.

03

Inventory awareness

Out-of-stock items are flagged unavailable so they do not appear in catalog messages or product flows. Restocks flip the item back to available automatically. Saves agents from manually checking inventory before sending a product card.

04

Image and media CDN

Product images are mirrored through a CDN-backed origin so they load fast inside the WhatsApp client, especially on low-bandwidth Indian or African networks. Broken image URLs in source data are surfaced as validation errors before push.

05

Meta rule validation

Before push, every product is validated against Meta's catalog rules — title length, description length, price format, image aspect ratio, prohibited categories. Failures are surfaced with the specific rule that broke, not a generic error.

06

Rollback and history

Every sync run is logged with a diff of what changed. If a run pushes a bad update, one click rolls the catalog back to the previous state. For high-stakes catalogs, review mode queues changes for human approval before they hit WhatsApp.

07

Google Sheets fallback

For sellers without an e-commerce platform, the catalog can be defined in a Google Sheet with a structured schema. Edits to the sheet sync to WhatsApp on a schedule or on demand. Great for grocery, services or low-SKU operators.

Use cases

Built for the way teams actually work.

D2C
Case 01

600-SKU fashion catalog

A D2C fashion brand syncs 600 SKUs from Shopify, including size and colour variants. New arrivals appear on WhatsApp within a minute, sold-out items vanish from the catalog, and agents send product cards in chat that reflect real inventory without manual checks.

E-commerce
Case 02

Daily-price grocery catalog

A grocery operator syncs 1200 SKUs with daily price changes from a Google Sheet. The catalog updates each morning, customers see today's mango price, and the cart-recovery flow reflects current pricing rather than yesterday's figure.

SaaS
Case 03

Stripe payment links as a catalog

A B2B SaaS sells add-on services via Stripe Payment Links. SabNode maps each link to a WhatsApp catalog item with pricing and description, so the sales team can send a product card in chat that opens directly to the Stripe checkout.

Healthcare
Case 04

Pharmacy chain inventory

A pharmacy chain syncs over-the-counter medicine inventory per outlet. WhatsApp catalog reflects branch-level stock so chat orders only show items actually available at the customer's nearest store, reducing returns and refunds.

EdTech
Case 05

Course catalog for an edtech

An edtech platform syncs its course catalog (with cohort start dates and seats remaining) from a Google Sheet. AI agents recommend the right course in chat based on the learner's interest and route them to a Razorpay payment link.

How it works

From signup to first send in minutes.

Catalog Sync is included on every SabNode workspace. No separate billing, no extra setup — flip it on from your workspace settings.

  1. 01

    Connect a source

    Authenticate Shopify, WooCommerce, Stripe or paste a Google Sheet URL. The platform fetches your product schema and previews how it will map to Meta's catalog format.

  2. 02

    Map fields

    Visually map source fields (title, price, image, SKU, inventory) to WhatsApp catalog fields. Set rules for variants, currency formatting and image fallback.

  3. 03

    Run a dry run

    Trigger a dry run to validate every product against Meta's rules. Errors are listed per product with the specific rule that failed and a suggested fix.

  4. 04

    Push to WhatsApp

    Push the validated catalog to your WABA. Subsequent webhook events from the source update the catalog in near real time without further setup.

  5. 05

    Monitor and rollback

    Watch the sync log for runs, diffs and Meta responses. If a run pushes bad data, rollback to the previous state in one click. Set up alerts on validation failures.

Plays well with

Works with the tools you already ship on.

ShopifyWooCommerceStripeRazorpayGoogle SheetsMetaBigCommerceZapier
Frequently asked

Questions about Catalog Sync.

Can't find what you're looking for? Talk to our team.

How does inventory sync work for variants?
Each variant (size, colour, flavour) becomes its own item in the WhatsApp catalog with an explicit inventory count or availability flag. When Shopify reports a variant going out of stock, we flip availability on that specific catalog item within seconds, so product cards in chat reflect what customers can actually buy right now.
What if Meta rejects a product?
Pre-push validation catches most rejections (title length, image format, prohibited categories) before they reach Meta. If Meta still rejects on the API side, the rejection reason is surfaced in the sync log with the specific Meta rule that failed and a one-click action to either edit the source product or skip that item from sync.
Can I keep some products out of WhatsApp?
Yes. Filter rules let you sync only certain product types, collections, vendor tags or active products. You can also flag individual products as excluded directly in SabNode without touching the source. Useful when WhatsApp catalog is for B2C SKUs while your Shopify also contains B2B-only items.
Does this support Stripe-only sellers who do not have a real catalog?
Yes. We treat Stripe Products and Payment Links as catalog items. Each Stripe product becomes a WhatsApp catalog entry with its price and image, and the catalog item links to the Stripe checkout URL. Sellers running purely on Stripe get a WhatsApp catalog for free.
How do you handle multi-currency stores?
Shopify and WooCommerce multi-currency setups are mapped to a primary catalog currency per WABA. If a customer is in a different country, the AI agent or flow can quote the price in their local currency, but the catalog itself is single-currency per WhatsApp Business account, which is a Meta constraint, not ours.
How fast is "real time" actually?
Webhook-based sources (Shopify, WooCommerce, Stripe) typically push to WhatsApp in 5–30 seconds end to end, including Meta's ingestion time. Google Sheets uses a 60-second poll for changes. If you need sub-second updates for things like flash-sale price changes, get in touch — we have a custom push channel for high-velocity catalogs.
What does rollback restore?
Rollback restores the catalog to the state captured before a specific sync run. That means products, prices, images, availability and variants. It does not roll back orders or downstream events — those are immutable. We recommend dry-running large changes and using review mode for catalogs where a bad sync would be expensive.
Commerce · Catalog

Ship catalog sync into production this week.

No credit card. No sales call required. Spin up a workspace, plug in a number, and your team is live in under an hour.