Catalogs overview | Developer Documentation

WhatsApp catalogs and orders: availability in ChatArchitect

ChatArchitect does not support native Meta product catalogs, product-card messages, shopping carts or receipt of catalog orders through its API or ready-made integrations. Use this page to check the scope before planning a shopping workflow for a connected WhatsApp number.

Check the feature your workflow needs

Meta's catalog overview describes inventory, commerce settings, product sharing and customer orders in its own platform. Creating a catalog in Meta tools does not enable these operations through a ChatArchitect connection. This availability statement covers the ChatArchitect connection; a feature visible in a separately managed app or account needs its own supported route.

Share an ordinary HTTPS product link

For a supported messaging workflow, you can send an ordinary text message containing a link to a product page or your website. Keep the website URL and product information under the control of the responsible store or business team. Confirm the message type and sending rules for your connection before a permitted test.

Use the text-message guide for text and link handling. A preview of a web page depends on its metadata and the receiving client; it is not a guarantee of a particular display. An ordinary HTTPS link carries the customer to the website. It does not register a Meta catalog, create a native product card or establish receipt of a cart order in the CRM.

Choose a supported message

Reply within the service window or use an approved template

If the customer has written first and the 24-hour service window is active, use the supported ordinary-reply workflow in your tool. To start or resume a conversation outside that window, select an appropriate approved template and follow the message rules for the intended recipient.

The template-management guide covers creating, editing and deleting templates in wtargeted.com. The component guide helps review text, variables and supported buttons. Availability of text or buttons does not establish support for a catalog template or product carousel. Confirm any special format before building a workflow around it.

For a custom application, use the ChatArchitect send reference and approved-template list reference. They document the supported text and template send string. Do not copy a direct Meta product-message request into the ChatArchitect API.

Keep order handling in the responsible system

A customer can describe a product question or purchase request in an ordinary text conversation. The operator can follow the business's existing process in the store, CRM or help desk. Creating an order record, updating stock or marking payment requires the appropriate confirmed process in that system; receiving a text message alone does not establish those actions.

Do not expect a structured catalog-order callback from this ChatArchitect workflow. Use the incoming-text guide for a customer's ordinary text and the delivery-status guide for the outcome of your outgoing message. A sent, delivered or read result reports message state; it does not confirm an order or payment.

Check the information before sharing it

• Review the final recipient, message purpose, permission and service-window/template requirements.
• Open the intended HTTPS page and check its product, price and availability before sending the link.
• Confirm who handles the customer's reply and which system is responsible for any order or payment action.

When a product or order workflow is missing

First identify what was actually sent: ordinary text, an approved template or an unsupported native catalog format. Check the supported tool's send result and incoming conversation separately. A missing cart or catalog-order event is consistent with the scope stated above; it is not evidence that the documented text callback is broken.

For an ordinary message that did not arrive, use the webhook overview and retain the operation, connection, time and available reference for support. Confirm payment features separately for your connection; catalog support does not establish a payment integration.

Keep the source product information current

Update a price or stock change in the system responsible for the website or order. Review old prepared messages and template variables before another send. Do not assume that a previously sent text quote, a link preview, a CRM field or a queued message automatically changes when a website is updated.