Here's a scenario I kept running into during testing. A customer opens the chat widget, types "show me hiking boots under $100," and gets a list of matching products with images, prices, and descriptions. Good so far. Then they pick one. "I like the second one, the waterproof pair in size 42." And then... nothing useful happens. The chat says something like "Great choice, you can find it on our store." The customer has to leave the conversation, navigate to the product page, find the right size in a dropdown, and click Add to Cart.
That gap between "I want this" and "it's in my cart" is where purchases die. Every extra click is a chance for the customer to get distracted, reconsider, or just give up. I built Emporiqa's product search to handle the discovery side well. But discovery without action is only half the job.
The Drop-Off Nobody Talks About
Most chat tools treat product recommendations as the finish line. The assistant finds the product, shows it, and considers its work done. But the customer's intent hasn't been fulfilled. They said "I want this." The response should be "Done, it's in your cart." Instead, they get redirected to a product page where they have to repeat the selection process manually.
For stores with product variations (sizes, colors, configurations), this gets worse. The customer already told the chat which variation they want. Sending them to a product page to re-select that variation is redundant work. And redundant work costs conversions.
How Cart Operations Work
Here's how it works: the assistant tells your store what to add, and your store's own cart system handles it. The assistant never touches the cart directly. It never calls store APIs, never manages cart state, and never goes anywhere near payment processing.
- The customer says "add the waterproof hiking boots to my cart, size 42"
- The assistant confirms the product exists and checks availability
- Your store's cart system adds it — all your rules (promotions, stock limits) still apply
- The customer sees a confirmation in the chat with an updated cart total
The store owns the entire cart implementation. Emporiqa just passes structured data: which product, which variation, what quantity, what action. The store decides how to execute it.
Six Supported Actions
Customers can do all of this through natural language in the chat:
- Add to cart: "Add this to my cart" or "I'll take two of those"
- Remove from cart: "Remove the hiking boots"
- Update quantity: "Change the quantity to 3"
- Clear cart: "Empty my cart"
- View cart: "What's in my cart?"
- Go to checkout: "I'm ready to check out"
The assistant handles context from the conversation. If the customer was just looking at a product and says "add it," it knows what "it" refers to. If the product has variations and the customer hasn't specified one, it asks which variation they want before proceeding.
Platform Support
The plugins for Drupal Commerce (setup guide), WooCommerce (setup guide), Sylius (integration docs), Magento 2 (integration docs), and PrestaShop include cart operations out of the box. No custom code needed.
Conversion Tracking: Closing the Loop
Every cart action from a chat session is tracked as a conversion event. When a customer adds a product to their cart through the chat, Emporiqa records it: which product, what quantity, the price, whether it succeeded. If the customer initiates checkout, that's recorded too.
The final piece is purchase completion. Two paths feed this data back:
- Confirmation page: Your store's order confirmation page sends a purchase notification back to Emporiqa. This ties the purchase back to the chat session that started it.
- Server notification: Your store sends a purchase notification with the order ID and total.
With both cart events and purchase events linked to the same chat session, you get full attribution. The dashboard shows which chat conversations led to cart additions, which led to checkout, and which completed as purchases. You can see the funnel: sessions with cart activity, cart-to-checkout rate, checkout-to-purchase rate, and total revenue attributed to chat.
What Cart Operations Don't Do
No in-chat checkout
When a customer says "checkout," the widget redirects them to the store's checkout page. The assistant does not process payments, collect shipping addresses, or handle any part of the checkout flow. This is intentional. Stores want control over their checkout experience. It's where they apply discount codes, upsell, and handle tax calculations. Processing payments inside a chat widget would also create security and PCI compliance problems that aren't worth solving when the store already has a working checkout.
No cart persistence across sessions
The assistant doesn't maintain its own cart state. It delegates to the store's cart system, which handles persistence however the store has configured it (cookies, database, session). If the store's cart clears when the browser closes, the assistant can't override that.
No abandoned cart follow-up
If a customer adds products to their cart through the chat and then leaves without purchasing, Emporiqa does not send follow-up emails or SMS. The conversion events are recorded and visible in the dashboard, but there's no automated recovery workflow. That's a different product category.
Cart must be enabled per store
Cart operations aren't on by default. The store admin enables them in the dashboard and the plugin must be installed on the site. If the plugin isn't set up, the widget tells the customer to visit the product page directly.
Why This Approach
Every e-commerce platform handles carts differently. Instead of trying to manage your cart from the outside, Emporiqa passes the customer's request to your store and lets your platform do what it does best. Your promotions, stock rules, and checkout flow all work exactly as before.
Getting Started
If you're already using Emporiqa with one of the supported plugins (Drupal Commerce, WooCommerce, or Sylius), cart operations work after you enable them in the dashboard. The plugins handle everything out of the box.
For custom platforms, your developer writes a small integration. See the documentation for details.
To see the full attribution chain in action, ask your developer to enable purchase tracking on your order confirmation page. That connects the last dot between chat, cart, and completed purchase.
Want to see cart operations working with your own products? Create a free Emporiqa account with up to 100 products and test the full flow: product search, add to cart, checkout redirect, and conversion tracking. No credit card required.
