Botpress for Ecommerce: Shopify, WhatsApp and Order Actions

Botpress can run a store's shopping assistant, but the commerce work lives in Hub integrations, not in the core builder. The Hub lists three Shopify integrations, plus BigCommerce, Magento 2, Stripe payment links and Klaviyo, while WhatsApp, Instagram and Messenger are channels on the same plan ^[1]. Billing runs per conversation. The Free plan covers 100 conversations with WhatsApp and webchat included; Plus costs $189 a month billed monthly or $150 a month billed annually for 250 conversations a month. Our read: a strong fit for product answers and chat-based order help, if someone on the team can wire integrations. Peak season is the real cost question.

Shopify: pick the integration by the job

The three Shopify listings do different work. The products sync, maintained by the Botpress Growth Team, writes every store product into a knowledge base as an article and keeps it current through Shopify webhooks. It needs the store's original myshopify.com domain, because custom domains are not supported. That covers questions such as which cleanser suits dry skin or whether a jacket comes in navy. It does not read orders. A store that wants the agent to see carts or purchases needs one of the other two listings.

The Conversy integration lists customers and orders, creates a Shopify cart and returns a payment link, lists smart collections and emits an Order Paid event tied to the conversation. The Simply Great Bots integration also emits events, but they are not linked to a conversation. That difference matters. A paid-order event that knows which chat produced it lets the agent follow up in the same thread, while an unlinked one only tells you a sale happened. Separately, Botpress's changelog says that since October 2026 its Shopify Admin and Storefront integrations can connect with your own app's client ID and secret instead of OAuth.

Getting the chat window onto the storefront is a separate step. The Shopify integrations move data; the shopper-facing window is Botpress's webchat, which needs a published bot and is covered in our website chatbot guide. Botpress's own Shopify post concedes that building flows, configuring integrations and troubleshooting can overwhelm non-technical teams and often call for a developer. Take that at face value. Studio handles simple flows without code, but a cart-and-payment flow touches APIs.

BigCommerce, Magento 2 and the catalog behind product answers

The BigCommerce integration, maintained by the Botpress team, syncs store products into a table named bigcommerce_products_Table, updates it when a product is created, changed or deleted, and runs on demand through the syncProducts action. It needs a Store Hash and an API Access Token from a store-level API account with read-only access to Products and to Information and Settings. The Magento 2 integration from the Growth Team retrieves products, checks stock by SKU and syncs products into a table in batches for large catalogs. It asks for four OAuth 1.0a credentials plus a Botpress Personal Access Token, and product reviews also need Magento's Reviews API module.

Tables and knowledge bases behave differently, and the choice shapes both cost and accuracy. A table holds structured rows: price, size, stock. Every table has a hard limit of 20 columns, and rows are capped per plan at 1K on Free, 100K on Plus and 500K on Team. The storage add-on costs $40 a month on Plus or Team and adds 100,000 rows. Botpress's docs name knowledge bases as usually the biggest AI cost driver in a project and suggest a Find Records card on a table for questions you already know.

For recommendations, Botpress's guide puts product data into knowledge bases as webpages, databases, documents or spreadsheets, each document up to 50 MB. Shopper data such as preferences or purchase history comes in through a webhook connected to analytics, a CRM or the store itself. That split is sensible. The catalog answers what exists, while the webhook supplies who is asking, so a returning buyer can get suggestions shaped by earlier orders rather than the bestseller list.

Upside Drinks, a Montreal marketplace for alcohol-free drinks, shows the pattern in practice. Its bilingual agent, in English and Quebec French, was built with the Botpress delivery team. A morning script pushes catalog files and nutrition sheets through the Botpress API, and Shopify shipping rules are read live each time the agent runs. Order questions go to the store's existing support widget, opened in the browser with no backend integration. Upside reports the agent resolved 93% of shopper conversations over two months ^[2].

Orders, refunds and payments the agent can act on

Botpress says its retail agents connect to the store and the helpdesk through OAuth and handle where-is-my-order questions, returns, refunds, address changes and subscription changes under the merchant's policy rules ^[3]. Its AI-actions page describes checks of order date, refund policy and customer history against rules the team defines before a refund goes out. Approval thresholds are configurable, so ambiguous or high-value cases wait for a person. Treat these as Botpress's descriptions. The real reach depends on which integration exposes your orders: Conversy lists them, while the products sync does not.

The Stripe integration creates payment links and subscription links, finds or creates customers, and responds to failed charges, failed invoice payments, failed payment intents and subscription updates or cancellations. It needs a Stripe Secret Key or a Restricted Key, and since September 2026 several bots can share one Stripe account without conflicts. The Klaviyo integration creates, updates and retrieves profiles and subscribes users to email or SMS marketing. It needs a published bot and a private API key with full access to Profiles and Subscriptions. A shopper who asks to hear about new flavors can be subscribed inside the same chat.

When the agent hits its limits, Botpress says the human receives the full conversation, the order data already pulled from the commerce stack, and a summary of what the AI tried. New workspaces hand off to Botpress Desk, which every plan includes, though routing and assignment need Team. Stores keeping their current helpdesk can connect it instead; our customer support guide walks through both routes.

WhatsApp, Instagram and Messenger for shoppers

WhatsApp is a channel on every plan, Free included. Setup needs a published bot and a Facebook account, and the bot cannot send messages until Meta verifies the business. Botpress cannot speed that up. The WhatsApp Playground lets you test while you wait. Shipping notices and other first messages need an approved template, and your backend can trigger one through the Webhook integration and a Start Conversation card. Native carousels and cards arrived in May 2026, which suits product browsing. Choices of one to three show as buttons and four to ten as a dropdown. The full setup is in our WhatsApp chatbot guide.

Instagram needs a published bot and a professional account, and a playground lets you test there first. Messenger needs a Facebook page. Its Start DM Conversation from Comment card lets the bot answer a comment on a product post and continue in private messages. If you connect your own Meta app instead of the guided setup, the bot works only for that app's admins, developers and testers until Meta approves it. Since August 2026, satisfaction prompts are skipped on all three Meta channels outside Meta's 24-hour messaging window.

What peak season does to a conversation bill

A conversation is any exchange with at least two messages from the shopper in the billing month. Anonymous sessions each count separately, which matters for stores whose shoppers browse without logging in, and a chat that spans two months counts in both. At 95% of the quota a 100-conversation pack is added automatically, and that auto-recharge cannot be turned off . Tests in the emulator count against the same conversation quota, and the AI operations in those tests draw on your AI usage too. These prices apply to workspaces created after mid-May 2026.

Run the season through it. A store on Plus that normally sees 500 conversations pays $384 a month billed monthly, by our arithmetic. If November doubles that to 1,000, by our arithmetic the month costs $709 billed monthly ($189 a month plus 8 packs of $65 per 100 extra conversations), or $670 at the annual rate. By the FAQ's 95% rule, the real bill can be one pack higher, and at 1,000 it likely will, so budget one pack more. Packs stay on until you remove them in billing settings, so each pack keeps billing $65 a month into December unless someone acts. Unused pack conversations expire at month end. Team's base becomes cheaper than Plus with packs above 1,350 conversations a month billed monthly, or above 1,150 billed annually.

Seats are the other seasonal trap. Botpress's e-commerce post says conversation pricing carries no per-seat cost, so seasonal agents do not raise the bill. The price part holds. The headcount part does not: Free and Plus include 3 seats, and unlimited seats start on Team. A store adding holiday staff to the inbox outgrows Plus on people before it does on volume.

Where Botpress fits a store's stack

Botpress suits a store that wants one agent answering product questions from a synced catalog, reaching shoppers on WhatsApp, Instagram and the site, and acting on orders through Conversy, Stripe or its own APIs. It asks for real integration work, and on Shopify the order-aware pieces come from third parties rather than Botpress itself. A small catalog can start on Free. Busy stores should watch two lines: packs that are added automatically at 95% of the quota and stay after a peak, and the 3-seat cap that pushes holiday teams toward Team.