WhatsApp Commerce
In-chat commerce is planned — not available in any workspace today.
WhatsApp commerce would let customers browse a product catalog, place orders, and pay inside a WhatsApp conversation. Wavy's backend has messaging, campaign, and payment-link paths, but a commerce layer that ties catalogs, orders, and in-chat checkout together has not been built. There is no catalog sync, no order object, and no in-conversation product carousel in any workspace. This page is not indexed because the capability is not live.
What does not exist
Removed from this page because it is not built.
The following were referenced in placeholder content but are not part of any live or supported commerce offering.
- In-chat product catalog — There is no Meta catalog integration, no product feed import, and no product object in the Wavy data model. A catalog page exists in the workspace UI but it is a placeholder, not a connected commerce surface.
- Order objects — There is no order model, no order status workflow, and no order-to-conversation link. The backend does not track orders as first-class entities.
- In-conversation product carousel — The WhatsApp client supports text and template sends. It does not send product or catalog messages because no catalog is connected.
- In-chat checkout — Payment links can be created and sent in a conversation, but there is no checkout flow that ties a specific product, quantity, and price into a single order-and-pay step.
What does exist
The pieces that are built — and why they are not commerce yet.
Wavy has messaging, payments, and contacts, but they are not connected into a commerce flow.
- Messaging path — The WhatsApp client can send text and template messages when configured. This is a communication channel, not a commerce surface.
- Payment links — The payments API can create links for UPI, Razorpay, PhonePe, or Stripe when a gateway key is configured. These are standalone links, not part of an order checkout.
- Contacts and segments — Contacts can be imported, segmented, and messaged. This supports marketing and support, not transactional commerce.
- Catalog UI placeholder — The workspace has a catalog route, but it is a placeholder page with no backend catalog service behind it.
The intended path
What commerce would look like when built.
If and when WhatsApp commerce is built, the intended path would connect three existing systems: the WhatsApp messaging client for sending product and catalog messages, the payments API for collecting payment, and the contacts and conversations model for tracking the customer journey. A Meta catalog would need to be registered and synced, an order object would need to be added to the data model, and the checkout flow would need to tie a product selection to a payment link in a single tracked step.
None of that integration work has been started. This page will be updated and the noindex directive removed when a commerce path reaches a configuration-dependent state — meaning the source exists, is workspace-scoped, and can be enabled with provider setup. Until then, no commerce capability should be assumed.
Questions
WhatsApp commerce — straight answers.
Can I sell products through WhatsApp using Wavy today?
No. There is no catalog integration, no order object, and no in-chat checkout flow. The messaging and payment-link paths exist separately, but they are not connected into a commerce experience.
Is the catalog page in the workspace functional?
No. The catalog route is a placeholder page. There is no backend catalog service, no Meta catalog sync, and no product data model behind it.
Can I send payment links in a WhatsApp conversation?
Yes, when a payment gateway is configured. The payments API can create links for UPI, Razorpay, PhonePe, or Stripe. But this is a standalone payment link, not part of an order-and-checkout commerce flow.
Will commerce be added in the future?
It is a planned capability. When it reaches a configuration-dependent state — source exists, is workspace-scoped, and can be enabled with provider setup — this page will be updated and the noindex directive removed.
Does Wavy integrate with Shopify or other ecommerce platforms?
No. Shopify storefront sync is listed as a planned integration for Kuber, the website and ecommerce specialist. It is not started in any workspace and is not part of Wavy's current scope.
Commerce is on the roadmap, not in the product.
Explore Wavy's available messaging, automation, and campaign capabilities today. When commerce is built, this page will say so plainly.