catalog nodes: Catalog nodes (link, message, single, multi, carousel) belong in one shop journey—not five disconnected flows. See why. Read how. Start here.
catalog nodes is the canvas job jewellery D2C should ship this week. Sending a website URL when the catalog could show products in chat? Wrong trigger or no Catalog single wastes spend and nights.
Skip it if you only blast lists. jewellery D2C needs a chat path, not a campaign.
Stay on this jewellery D2C job: what to wire, what to delete, and the recovery—not a tour of every palette icon.
WAPilot implementers who sit in jewellery D2C reviews would rather ship a thin v1 than hoard unpublished nodes.
Connect catalog in product settings first (Guides). Intro text, then catalog message or carousel. That is enough setup talk for jewellery D2C before the first heading.
this node (link, message, single, multi, carousel) belong in one shop journey—not five disconnected flows. jewellery D2C should treat that sentence as the job, not a slide title.
jewellery D2C already saw this fail: keyword “shop” sent a 40-item carousel; phones crawled The recovery was category list first, then a small multi-product node
Sources: Meta’s messaging limits plus send-messages. Official Cloud API only—jewellery D2C on a grey gateway is another product.
this step (link, message, single, multi, carousel) belong in one shop journey—not five disconnected flows. On the canvas you place Catalog message, Catalog single, Catalog multi, Catalog carousel, Send payment link. jewellery D2C teams finish one job, then use Catalog single when the customer sends a photo or a rant.
This is not a campaign. Canvas setup for jewellery D2C: WhatsApp Flow Builder.
In this series — Part 4 of 6 (Integrations). Previous: Meta CAPI. Next: send payment link. Series start: Google Sheets node.
Order: trigger, hello, Connect catalog in product settings first (Guides)., then Catalog single. That is v1 for jewellery D2C.
In a jewellery D2C thread (2026), the failure was concrete: keyword “shop” sent a 40-item carousel; phones crawled. The rewrite that stuck was category list first, then a small multi-product node. Repeat that, rather than adding decorative palette icons.
jewellery D2C only needed Catalog message, Catalog single, Catalog multi, Catalog carousel, Send payment link on the happy path. Day-one order: Connect catalog in product settings first (Guides). After the hello: Intro text, then catalog message or carousel.
Ask buy vs help; payment link or Assign Agent. Do that before you add another Condition. jewellery D2C already tried the pretty version.
The adult move: Do not dump the whole catalog on “hi”. After that, Test products that are in stock. Catalog single remains the escape when the answer is messy. See also WhatsApp drip sequences.
Attributed example, from a WAPilot jewellery D2C workspace (2026): keyword “shop” sent a 40-item carousel; phones crawled. category list first, then a small multi-product node
jewellery D2C also split keywords so campaigns and this canvas could not greet the same inbound twice.
Rule sources: Meta message templates, send-messages (the window), messaging limits. This jewellery D2C path cannot mint session time. Catalog single does not reset it.
How we know: WAPilot implementation plus inbox on official Cloud API—human handover, Flow Builder, Flow Builder. jewellery D2C here matches those queues and Meta’s public docs, using Catalog message, Catalog single, Catalog multi, Catalog carousel, Send payment link.
One sentence? Use human handover. A week of follow-ups? Flow Builder. Branches and Catalog single stay on the canvas for jewellery D2C.
Do not park jewellery D2C reminders at local 1am. Delay until morning beats a raw +24h from a midnight chat after Catalog message.
Walk the false branch. A jewellery D2C path that only works on perfect taps will strand the first typo after Intro text, then catalog message or carousel.
A typical jewellery D2C publish went wrong because keyword “shop” sent a 40-item carousel; phones crawled. Changing the graph to category list first, then a small multi-product node stopped the screenshot pile-up.
Palette for this job: Catalog message, Catalog single, Catalog multi, Catalog carousel, Send payment link. If a node is not in that list, it waits for v2. Start with this: Connect catalog in product settings first (Guides). Then: Intro text, then catalog message or carousel.
Plan days, not minutes, for rating at jewellery D2C. A new customer message can reopen session quickly. Turning the canvas off is not a fresh clock.
WhatsApp catalog is Cloud API specific. Instagram/Facebook flows lose some commerce nodes—plan a simpler menu there.
No. The window can close while Delay is counting for jewellery D2C. Plan a template for that later bubble after Do not dump the whole catalog on “hi”.
No. Same customer, same business thread for jewellery D2C. Do not wait for a reset that never arrives after Catalog single.
Recap: Catalog nodes (link, message, single, multi, carousel) belong in one shop journey—not five disconnected flows. Test catalog nodes on a real phone, then start a free trial once someone at jewellery D2C owns the inbox.
ads to booking flow: Ads → catalog or booking: paid chat that sells the thing in the ad—slot or product—then human if needed. See why. Read how. Start here.
Read MoreStart automating your WhatsApp marketing today with WA-Pilot. Join thousands of businesses already growing with our platform.
Start Free Trialassign ads leads: Assign and tag ads leads: source label in the flow, Meta ad routing in Team Assignment, then sub-flow for the product. See why. Read how.
Read MoreCAPI in ads flow: Meta CAPI in an ads flow: fire Lead/Purchase after chat qualify so Ads Manager sees the WhatsApp truth. See why. Read how. Start here.
Read More