AI Chatbot for Retail

How online and multi-location retailers answer hours, availability, orders and returns in chat.

A retail chatbot answers the questions shoppers ask before and after buying: store hours and locations, whether an item is available, where an order is, and how returns work. The useful ones answer from the retailer's own pages, catalogue and e-commerce platform rather than a script, and hand over to a person when they cannot. Vatdi does this from a website widget, starting on a free plan.

Last updated

Retail Stores Challenges Vatdi Solves

Store hours, directions and "is it in stock" questions arrive by phone and email all day and are answered one at a time

"Where is my order" is the most repeated support question and needs someone to look it up

Returns and exchange rules are asked about far more often than they are read

Seasonal peaks multiply questions while the team stays the same size

Shoppers in other languages get no answer at all

Nobody is available at night or on weekends, when shoppers are still browsing

How Retail Stores Use Vatdi

Store hours, locations and services answered from your own location pages

Product availability shown as cards with price and sale price, stock when your platform holds it

Order status by order number plus email or phone, live from the e-commerce platform

Returns, exchanges, sizing, gift card and loyalty questions answered from your policies and FAQs

Handover to staff inside agent hours, with missed handoffs counted

Leads captured with a 1 to 5 trust rating when a shopper wants a follow-up

What a retail chatbot does, online and in multi-location retail

Retail support splits into two kinds of business with overlapping questions. An online retailer gets product, shipping, order and returns questions. A multi-location retailer with a website gets those plus "are you open on Sunday", "which branch is nearest" and "do you have this in the Leeds store". A retail chatbot is worth having when it can answer most of both lists from data the retailer already has.

Question typeOnline retailerMulti-location retailerWhere a grounded bot gets the answer
Store hours and locationsRareConstantYour store-finder and contact pages, crawled or pasted as URLs
Product availabilityConstantConstantCatalogue sync from the e-commerce platform; stock only if the platform holds it
Order statusConstantCommon for click-and-collectLive order lookup through the platform plugin, by order number plus email or phone
Returns and exchangesConstantConstant, plus "can I return online orders in store"Your returns policy page or PDF
Sizing and fitCommonCommonSize charts and fit notes in the knowledge base
Gift cards and loyaltyCommonCommonGift card terms and loyalty FAQ pages

The mechanism behind "grounded" is retrieval-augmented generation: for each question the bot searches your synced catalogue and knowledge base first and writes only from what it finds, so it does not invent a branch, a price or a returns window. What is a RAG chatbot explains it; the customer-service chatbot ranking compares tools built for support desks.

The retail use cases in detail

  • Store hours and locations. The bot answers "are you open on bank holiday Monday" and "which store is closest to SW1" from your location pages. Keep one page per store with address, hours, phone and services (click-and-collect, returns desk, fitting), and the bot has what it needs.
  • Product availability. "Do you have the 32-inch in stock" is answered from the catalogue sync with a product card showing price, sale price during a sale, and a link. Stock appears on the card only if you turn it on and your platform maintains it.
  • Order status. The shopper gives the order number plus the email or phone on the order and the bot reads the status live from the platform. Available through the plugins for WooCommerce, OpenCart, PrestaShop, Magento, Shopware, Joomla and Drupal Commerce; not on Shopify. How to track orders with a chatbot has the flow.
  • Returns and exchanges. The bot quotes your policy as written: window, condition, who pays postage, refund timing, whether online orders can be returned in store. Exceptions go to a person.
  • Sizing and fit. Size charts per category and fit notes ("this brand runs small") turn "will a medium fit me" into an answer instead of a return.
  • Gift cards and loyalty. Balance checks are usually a link to your gift card page; terms, expiry, how points are earned and redeemed are answered directly from the FAQ.
  • Coupons. When a shopper hesitates on price, the bot can mention a coupon you have configured, with its conditions, when it fits the conversation.

Everything above works in the shopper's language: 95+ languages are detected automatically, with a fallback you choose. How the bot chooses which products to show is covered in conversational product recommendations.

What to load into the knowledge base: a retail checklist

The catalogue arrives through the platform plugin (or a crawl and CSV upload on other sites). The rest is a one-afternoon job. Sources can be a website crawl, pasted URLs, PDF, DOC, DOCX, CSV, TXT or Markdown uploads up to 10 MB each, manual text, FAQ import from CSV or Excel, and AI-generated FAQ suggestions you approve.

  • One page per store: address, opening hours including holidays, phone, parking, services offered.
  • Shipping: zones, costs, delivery windows, cut-off times, click-and-collect timing.
  • Returns and exchanges: window, condition, exclusions, refund method and timing, in-store return rules for online orders.
  • Sizing: charts per category, measuring guide, brand-specific fit notes.
  • Product care and warranty: washing, assembly, warranty length and claim process.
  • Payment: methods, instalments, gift cards (purchase, redemption, expiry), price-match policy if you have one.
  • Loyalty programme: how to join, how points accrue, how to redeem, tier rules.
  • Accounts and orders: changing an address before dispatch, cancelling, applying a coupon.
  • Accessibility and services: wheelchair access, personal shopping, alterations, repairs.
  • Top 30 questions from last month's email inbox, as an FAQ CSV.

Knowledge item caps are 100 on Free, 500 on Starter and unlimited on Grow. Load policies first, store pages second, FAQs third; policies remove the most handovers per item. How to train a chatbot on your data covers file formats and common mistakes.

A two-week rollout plan

DayTaskDone when
1Create the account, install the platform plugin or paste the script, run the catalogue syncThree product cards show the right price, image and link
2Load policies, store pages and the FAQ CSV from the checklistTen test questions answered correctly, including one the bot should refuse
3Set widget appearance (brand auto-detect, then adjust), hide it on checkout, set agent hours and quick repliesWidget matches the site on desktop and mobile
4Invite the team (unlimited teammates, per-page roles), test handover and the email and browser alertsA test handover lands as "Needs you" in the inbox
5Go live on product, category and policy pages onlyFirst real conversations arrive
6 to 7Read every transcript; add missing answers to the knowledge baseRepeated gaps closed
8Enable order lookup if not already on; test with a real order number and a wrong emailCorrect status; refusal on mismatch
9 to 10Translate widget labels for your second language; test a conversation in itReply arrives in the visitor's language
11 to 12Review the 0 to 10 quality grades and the advice attached to the lowest ones; fix content, not promptsNo grade below 6 for a fixable reason
13Set the KPI baseline from the overview and feedback reportsNumbers recorded
14Extend the widget to the home page and blog; decide on Starter or Grow if the conversation cap is closeLive site-wide

Two weeks is enough because there are no flows to build; the bot answers from content, so the work is content review. Details of each setting are in the docs.

KPIs to track

KPIWhat it showsWhere to read itRule of thumb
Questions answered without handoverHow much of your support the bot absorbsInbox states: conversations that reached Resolved with no handoverShould rise week on week as the knowledge base fills; if flat, read transcripts
Missed handoffsTimes a shopper asked for a person and nobody picked upTracked and counted per conversation; visible in the inbox as MissedEvery miss is a content or staffing gap; aim for zero inside agent hours
Lead trust ratingQuality of contacts the bot capturedLeads report, 1 to 5 automatic rating, editable, CSV exportFollow up 4s and 5s the same day
Conversation rating and per-answer thumbsWhether shoppers found the answers usefulFeedback reportInvestigate any thumbs-down on a policy answer immediately; it is usually a wrong or outdated page
Quality grade0 to 10 per conversation with plain-English adviceEvery conversationSort ascending once a week and fix the causes
Conversations per month vs plan capWhether you are about to hit the limitUsage forecast reportMove to Grow (unlimited) before a promotion, not during it

Add-to-cart and order value for chat-assisted sessions are measured in your store analytics, not in the chatbot; compare sessions that opened the widget with sessions that did not. Reports on Vatdi (overview, leads, feedback, insights, usage forecast) are on every plan, including Free; see features.

Seasonal peaks

Retail demand is not flat, and neither is the question volume. Three things to do before the peak rather than during it:

  1. Move to a plan without a conversation cap. Free stops at 15 conversations a month and Starter at 150. Grow at $7.49/mo has no cap, and AI replies inside a conversation are never capped on any plan. Switch two weeks before the campaign.
  2. Load the seasonal content. Extended returns windows, order-by dates for delivery before a holiday, gift-wrap options, gift card delivery times, and extended store hours. Remove them afterwards so January shoppers are not told December rules.
  3. Cover the handover hours. Extend agent hours for the peak, and check the missed-handoff count daily. Outside agent hours the widget tells shoppers honestly that nobody is available and captures their details.

The Black Friday chatbot strategy is a step-by-step version of this with a timeline. The Baymard Institute's running average for cart abandonment is about 70%, and unanswered pre-purchase questions are one of the causes a chatbot can actually remove; it is not a cart-recovery tool and does not send follow-up emails.

Honest limitations

  • No POS integration. The bot does not connect to till systems. If a question needs the POS, it is a handover.
  • In-store stock only if your e-commerce platform holds it. Per-branch availability can be answered only when the platform exposes it to the catalogue sync and you enable stock. Otherwise the bot answers "check with the store" and offers the branch phone number from your location page.
  • Website widget and WhatsApp. No SMS, Messenger, Instagram or email channel; WhatsApp works through your own WhatsApp Business number. Retailers who need those alongside the website pair Vatdi with a messaging tool, or choose an omnichannel product such as Tidio.
  • Order lookup is not available on Shopify. Shopify stores get the widget and answers from pages, collections and policies; live order status is on the roadmap.
  • No attachments in the widget, no canned responses or internal notes for agents.
  • No upsell engine or cart-recovery automation. The bot answers what is asked and can mention a configured coupon when it fits.
  • One store per plan. A retailer with three separate websites needs three plans.

Retail chatbot solutions fall into three categories: a website widget grounded in your own data (Vatdi), an omnichannel inbox (Tidio), and a helpdesk built for a contact centre. If your retail operation is mostly a contact centre handling phone, email and social channels, a helpdesk such as Zendesk (Suite Team from $55 per agent per month on annual billing, AI agents as add-ons) or Intercom (from $29 per seat per month plus $0.99 per Fin AI resolution) is the better category, at a very different price. Prices are as of September 2026 and change; check the vendors' pricing pages. Vatdi vs Intercom sets out that trade-off.

Compliance and privacy for retail chat

Retail chat collects personal data: names, emails, order numbers, sometimes addresses. What Vatdi does with it, on every plan:

  • HTTPS everywhere; store credentials encrypted at rest; per-store data isolation so one retailer's data is never retrieved for another.
  • Chat answers are generated by OpenAI GPT-4o-mini via API, with zero-retention API mode where enabled; conversations are not used to train models. LLM call logs are kept for 90 days.
  • Order lookup requires the order number plus the matching email or phone, so a shopper cannot read someone else's order.
  • GDPR and CCPA rights: JSON data export, account and data deletion, and a DPA on request. Subprocessors are listed on the Trust page.
  • Encrypted backups with a 10-day rolling retention.

Vatdi does not hold SOC 2 or ISO 27001 certification; if your procurement requires one, say so early. AI chatbot with GDPR compliance covers what to put in your privacy notice when you add a chat widget, and security lists the technical controls.

What it costs

PlanPriceConversations / monthKnowledge itemsSynced productsBadge
Free$0 forever, no card15100200Shown
Starter$4.49/mo or $44.90/yr1505002,000Can be removed
Grow$7.49/mo or $74.90/yrUnlimitedUnlimited10,000Can be removed

Every plan has every feature: order lookup, handover, leads, languages, reports, unlimited teammates. The only paid-only capability is removing the badge. No setup fee, no contract, cancel from the billing page, annual saves about 17%. A retailer with a catalogue under 2,000 products and steady traffic fits Starter; anyone with a seasonal peak or a larger catalogue should be on Grow. See pricing and how much an AI chatbot costs for the comparison with per-seat and per-resolution pricing.

Frequently Asked Questions

A chat widget on a retailer's website that answers shopper questions automatically: store hours and locations, product availability, order status, returns and exchanges, sizing, gift cards and loyalty terms. A grounded retail chatbot answers from the retailer's own pages, catalogue and e-commerce platform, shows product cards, and hands over to a person when the question is outside what it knows.

Mostly to absorb repeated questions before and after purchase. Online retailers use them for product questions with cards, shipping and returns answers, and live order status by order number plus email or phone. Multi-location retailers add store hours, directions and click-and-collect questions from their location pages. Teams then handle only the handovers, and read the transcripts to find gaps in their content.

Only if your e-commerce platform holds per-store stock and exposes it to the catalogue sync, and you enable stock in the widget. Vatdi has no POS integration, so till-level stock is not visible to it. When per-branch stock is not available, the bot says so and gives the branch phone number from your location page rather than guessing.

Yes, through the platform plugins for WooCommerce, OpenCart 3 and 4, PrestaShop, Magento, Shopware 6, Joomla with VirtueMart or HikaShop, and Drupal Commerce. The shopper gives the order number plus the email or phone on the order and gets the live status; mismatched details are refused. Order lookup is not available on Shopify, where the bot answers from pages and policies.

Vatdi does not. It connects to your e-commerce platform for the catalogue and orders and to your website content for everything else. Questions that need the POS, such as a till receipt or an in-store return without an online order, are handed to a person. If POS integration is essential, look at helpdesk products built for retail contact centres, at a different price point.

On WhatsApp, yes: connect your WhatsApp Business number and the same assistant answers there with the same catalogue and handover. There is no SMS, Messenger, Instagram or email channel. Retailers who need those pair the website bot with a messaging tool such as ManyChat, or pick an omnichannel inbox such as Tidio, which includes Messenger, Instagram, WhatsApp and email but charges for AI answers as a separate add-on.

The widget and catalogue sync take about ten minutes with a platform plugin. A useful bot takes two weeks, most of it loading policies, store pages and FAQs and reading the first transcripts to fill gaps. There are no flows to build, so the effort is content review rather than design. The plan above gives the day-by-day sequence.

It can be, if the vendor gives you the controls. Vatdi provides HTTPS, encryption of store credentials at rest, per-store data isolation, JSON data export, account and data deletion, a DPA on request and a published subprocessor list; chat answers use OpenAI via API without training on your data. Vatdi does not hold SOC 2 or ISO 27001 certification, so check your procurement rules.

For a retailer that sells online, one that reads the live catalogue and can look up an order — Vatdi does both on WooCommerce, OpenCart, PrestaShop, Magento, Shopware, Joomla and Drupal, and answers from your pages and files on any other site. For a retailer whose questions are mainly opening hours, locations and stock at a branch, the crawl of your store-locator and policy pages covers it.

Three shapes: enterprise platforms with POS and CRM integrations, priced for it; omnichannel inboxes that add Messenger, Instagram and WhatsApp; and AI assistants trained on the retailer's own catalogue and pages. Vatdi is the third — website widget plus your own WhatsApp Business number, flat per-store pricing, free to start.

Put a retail chatbot on your site this week

Connect your e-commerce platform, load the checklist and run the two-week plan on the free plan with no card.

WhatsApp is a trademark of WhatsApp LLC, a Meta company. Vatdi is an independent product and is not affiliated with, endorsed by or sponsored by WhatsApp LLC or Meta Platforms, Inc.