Does enabling Offer Cards enable a shopping cart?

No. Offer Cards present products. Adding products to a cart requires a supported store integration, the relevant action configuration and a compatible storefront.

Where does the customer complete payment?

In your store. Adding a product to the cart is not checkout, payment or confirmation of a new order.

What happens with products that have sizes or colours?

On supported integrations the customer selects the required variant through the widget controls. If the required options cannot be handled in chat, the customer may be sent to the product page instead.

Can an XML product feed add items to the cart?

No. Feed-based product cards link to your store. A feed does not provide the storefront cart integration or order lookup.

Adding products to the cart from chat

On supported stores, product cards can let customers add an item to their storefront cart without manually finding it again. The store still handles checkout, payment and the final order.

Before you start

Connect a supported store, configure product search and enable Offer Cards. Follow your platform guide for the available cart settings. Support depends on the platform, product type, required options and the website on which the widget is embedded. It is not a capability of every native integration.

Configure and test the storefront

Select your chatbot, open Settings > Actions, and inspect your platform's enabled product-search or AI product-search action. Where offered, enable its Add to cart option. The AI Actions guide explains action configuration. Install the widget on the connected storefront using Deploy.

For Ecwid, the store cart must be available on the same page, such as an Instant Site or a website with an embedded Ecwid store. Outside that context, the product page can open instead. A test in Overview is therefore not enough to verify a real storefront cart operation.

What the customer sees

See it in a conversation

Choose a variant before adding to cart

Illustrative sequence: actual cart buttons and variant pickers depend on the platform and storefront. This playback does not execute a cart operation.

ChatLab exampleIllustrative conversation

Emerald wrap dress, $79. Viscose, midi length.

Play the example or read it below. No real customer data is used.

1 / 4

Search results provide a product card with a cart control on supported stores.

Playback pauses when this example leaves the screen. This is a simulation, not a live chat. Widget controls inside the playback are not interactive.

Read the complete example

Search results provide a product card with a cart control on supported stores.
Emerald wrap dress, $79. Viscose, midi length.
The customer chooses a product and size using the supported cart controls.
Visitor: Emerald wrap dress, size 38.
Only confirm success after the storefront accepts the cart operation.
Assistant: Example result: the selected variant has been added to your store cart.
Payment and checkout remain in the store.
Assistant: Review your cart in the store to confirm quantity, price and delivery, then proceed to checkout.

This illustrative playback explains the sequence; it does not click a real storefront button or modify a cart. In the actual widget, supported product cards provide the cart controls. Products with variants may first open a size or colour selector. Required options that cannot be completed in chat, such as some personalised text fields, can require opening the product page.

Confirm the result

Test on your storefront with a simple product, a product with variants and a product requiring custom options. Verify the exact item, variant and quantity in the store cart. Check that the product-page fallback remains usable when direct cart insertion is unavailable. Do not treat a chatbot sentence saying "added" as evidence of a successful cart operation.

The final price, stock availability, delivery and payment are confirmed in the store. Cart actions do not by themselves reserve inventory or place an order.