70.22 %
Around 70 percent of online shopping carts are abandoned
average across 50 separate cart abandonment studies collected by the Baymard Institute
The shop assistant is instructed to answer from your product catalogue rather than from general world knowledge: what is not in there, it is not supposed to name.
This page shows the assistant for shops on Shopware CE. It answers from your catalogue. What is not in there, it does not name. It finds and compares items and suggests add-ons. It looks up price and stock in the shop. It only changes the cart once the customer agrees.
Request a free demo Call: +49 5123 9579000
It searches and compares items, suggests accessories that are on file, looks up price and availability in the shop when asked, and the order status where you connect your own inventory system in the Custom package, and assembles a cart in the chat. Every step that changes something is first shown as a proposal in the conversation and only runs once the visitor confirms it. In the Pro package the basis is Shopware in the Community Edition.
Visitor:I am looking for an espresso machine under 500 euros, preferably in black.
Assistant:One machine in the catalogue fits that price range. Whether the black version is in stock right now is not in there — I have looked it up in the stock system.
Visitor:Is there matching accessory for it?
Assistant:One descaler set is on file for this machine. There is nothing else, and what is not in the catalogue I do not suggest either.
Visitor:Both in black to the cart, please.
Assistant:I am putting that down as a proposal. It only runs once you confirm, and the wording you are reading now is stored for that and not regenerated later.
Assistant:Confirmed and executed: two items, total 468 €. The whole cart was recalculated with the current price from the shop, not just the new line. The link to the shop carries a random pickup token — it sits in the address and nowhere else in the transcript.
Ask it yourself, Assistant of this website
Automated assistantIn an online shop a single open question often decides whether an order goes through or the cart is left behind: Does this product fit my need? Is the version in stock? How long is delivery? Anyone who finds no answer leaves — around 70 percent (Baymard Institute) of online shopping carts are abandoned. The shop assistant starts there without inventing the answer: it answers from a product catalogue that your shop hands to XICBOT, shows hits as product cards in the transcript and changes the cart through the cart assistant. What is missing from the catalogue is looked up in your systems or stays open. Nothing is guessed.
70.22 %
Around 70 percent of online shopping carts are abandoned
average across 50 separate cart abandonment studies collected by the Baymard Institute
The shop assistant carries six tasks today. For day-to-day operation one distinction matters more than the number: which answer comes from your product catalogue, which needs read access into another system, and which changes something and therefore requires the visitor's confirmation.
The assistant searches the full text of your catalogue's titles and descriptions and orders the hits by the question, not by the order of the database. It gives the reason why an item fits and says so when the selection is not enough for a comparison, instead of inventing a second item.
On availability the catalogue carries only a yes or no and a delivery time in days. Quantity, version, restocking date and location are not in there — they come from read access into your inventory system (Custom package). If you do not enable it, the assistant says that it has nothing on file rather than estimating a figure.
Instead of a wall of text the assistant shows product cards with title, price, rating and button inside the transcript. The price is formatted on the server: otherwise the browser would show a different figure depending on the visitor's language setting than the one used for the calculation.
Through the cart assistant the assistant puts together a cart in the chat, adds to it, changes and clears it and enters a voucher code; the cart is held by XICBOT and uses the live price from your shop. “Continue” leads into your shop; the link there carries a random pickup token that does not appear in the transcript. Through a read-only pickup address at XICBOT your shop can fetch the cart with that token; your shop connects this pickup through an integration of its own, and XICBOT creates no order, no customer account and no checkout.
Where is my order? The assistant answers this from your inventory system connected in the Custom package — but unlike a price enquiry, by default only after explicit confirmation. The call fetches a personal record, and the confirmation is the point at which the visitor sees which order number goes to which system before it leaves.
Accessories and “customers also bought” are read from the references filed against the item in the catalogue. If nothing is filed there, nothing is suggested: an invented add-on would be a product statement your shop does not honour.
A limit that is not glossed over here: a proposal that the visitor neither confirms nor declines does not stay open indefinitely. If no agreement comes within the time allowed, it counts as expired and can no longer be confirmed — nobody has declined it, and anyone who wants to carry on gets a new proposal.
A shop assistant that only gives information merely postpones the work. One that acts with nobody watching is a risk. That is why both sides are kept apart here, under different rules: reading is bound to the catalogue, acting to a permission and to the visitor's confirmation.
The catalogue is not scraped but handed over: your shop sends the items to an interface, up to 500 per call, and every item carries its identifier from your shop. A second run of the same file therefore creates no duplicates but reports back what is new and what has changed. We set up the handover from Shopware; the product itself only knows the interface.
Through enabled tools the assistant carries out real operations, but only those you have created and only in the form you have defined. Every call moves through fixed states: proposed, confirmed, executed or declined, plus expired, failed and timed out. Which further systems can be connected is shown under tool control.
Outbound, every call takes a single path, and it is narrowly drawn: the target is checked beforehand, the response is cut off after a fixed deadline and a fixed size, the call does not follow a redirect, and it is not retried. A target system that stays silent or redirects therefore produces a visible error in the conversation and not an invented answer.
Visitor:Do you also carry the LatteOne milk frother?
Assistant:That one is not in your catalogue. I will give neither a price nor a delivery time for it, not even an approximate one.
Visitor:And how long do I have to return something?
Assistant:There is a section from your uploaded documents on that. I will reproduce it and add the source, rather than phrasing the period from memory.
Visitor:And if there is nothing in there?
Assistant:Then I say exactly that and offer a handover to a person. The question is additionally recorded as a gap and reported to your system so that it can be filled in.
8 of 8
questions without a basis declined instead of guessed
eight questions deliberately outside the material; the wording of every answer is in the measurement file
Question, channel and time are there before a conversation is opened.
One switch shows the answers that were left without a covered statement.
A test conversation checks the answer against your own catalogue before a customer reads it.

The path runs through six steps, and their order is not a matter of taste: without a catalogue the assistant has nothing to say, without defined tools nothing to do, and without a test conversation nobody has seen the wording a customer will later read.
In the free first conversation we sort your cases into the three classes that later determine the setup: what is answered from the catalogue, what needs read access into another system, and what changes something and therefore has to be confirmed. This split drives the effort, not the number of products.
Your shop sends the items to the catalogue interface, up to 500 per call, each with its identifier from your shop. Back comes how many items are new and how many have changed. Title, description, features and references are limited in length so that a product card does not turn into a table.
For each target system we create a tool: stock lookup, order status from the connected inventory system (Custom package), cart pickup, handover to a person. That defines what the tool may read, which target it reaches and whether it runs without asking back. Tools that write never get that approval — it is part of the contract every build form has to fulfil.
Shipping, returns, payment methods, complaints: none of that is in the catalogue but in your documents. We store them as documents, the assistant usually quotes from them with a source and stays bound to the excerpts. If it finds nothing there, it is instructed to say precisely that rather than guess.
The assistant is embedded in your shop with a loader script; the chat window sits in its own frame and loads only once your shop has finished loading. A new assistant starts as a draft. In the test conversation you read the answers against your real items before a customer sees them.
After going live, operation, hosting in Germany, maintenance and data protection stay with us. Conversation analytics shows what was actually asked; every answer left without a citation appears as its own row in the gap list. That becomes the next round: fill in missing item data, add a document, sharpen a tool.
What is needed from you is manageable but not nothing: someone who supplies the catalogue and someone who can answer questions about the target systems. Without both, an assistant stays where most chat windows are — talking about your range in general instead of answering from it.
We connect a test assistant to an excerpt of your catalog and show how advice, product card and cart work together in the same chat.
Two effects carry the cost. The first is relief: questions about availability, version, delivery time and order status repeat every day, are answerable from the catalogue and, for order status, from a connected inventory system, and still tie up working time. The second is the shorter path to completion: information, accessories and cart sit in the same window, especially on a phone screen where every change of page is a point of exit. How strongly either works in your shop we do not state in advance — the assistant measures it: after going live you see which questions came in, which it answered and which it had to hand over.
An assistant does not replace people — it relieves them. The shop assistant takes on the recurring product and delivery questions so your team has time for advice and the tricky cases. That a language model can be wrong is not argued away here but built in: hard statements in an answer are checked afterwards against the source material, whatever is not found there is replaced by a placeholder, the visitor receives the correction as its own message, and the case then appears in the list of uncovered statements. A handover to a person remains available within the conversation.
from 149 € per month net
Minimum term: none, cancellable monthly
All prices net, plus VAT Source: XICBOT price list, as of 11 September 2026
The Pro package suits the shop assistant: operation from 149 € per month net plus a one-time setup from 2,900 € net (catalog connection to Shopware CE, individual training, product cards, cart and conversation analytics). The entry point as a pure website assistant (Start package) begins at 49 € per month net, individual tool control at 4,900 € net setup. You will find all packages in detail under pricing. Every project starts with a free initial consultation and a demo. Ongoing services are booked individually and can be cancelled monthly; there is no minimum term.
The left-hand column does not describe a badly maintained shop. It describes a shop where the answer does exist but sits somewhere other than the question — in the catalogue rather than in the visitor's head, in the order system rather than on the product page.
The last row is the most important and the least conspicuous. What is not in the catalogue usually stays unanswered — and ends up in the gap list. That turns a lost question into a task: you see which detail is missing from the range, instead of suspecting that something is missing.
Not every reading call runs silently along in the right-hand column: reading the delivery status from the connected inventory system is set to confirmation by default, and the visitor sees beforehand which order number goes out with it.
Which cases the assistant handles specifically in retail is shown on the assistant for online shops page. Beyond product advice it can also read and control other systems in the Custom package — from inventory to ticketing, described under tool control.
What the Examples Show and What They Do NotThe journeys above describe the way of working in retail, not a measured result. What a shop assistant can do for your range depends on catalogue maintenance and connection, and only shows on an excerpt of your own catalogue.
What this means in retail is covered in more depth in the guide: AI chat assistant for online shops describes the typical use cases, guided selling in chat shows how questions turn into a matching item, and agentic commerce explains why machine-readable product data is becoming more important.
The questions that come up most often before a shop project are about origin and limit: where does a statement come from, and what happens when it is nowhere on file.
Yes. We connect the assistant to your shop based on Shopware in the Community Edition. It takes catalog, variants, prices and availability from the shop, syncs them on a schedule and can perform real actions via the cart assistant. Hits are shown as a product card with image, price, delivery time and action, at most six per answer; sold-out items do not appear. The visitor reads every cart change as a proposal beforehand and confirms it themselves; each line item allows at most 99 units. “Continue” then leads into your shop through an address with a random pickup token; for the finished cart to be waiting there, your shop needs an integration of its own. Because Shopware is an open system, your shop stays in your hands and can be extended flexibly.
From your Shopware catalog. We train the assistant on your own shop data so that its answers are bound to these sources instead of being freely invented. What is taken over is title, image, price, variants, availability, delivery time, rating and promotional prices; the catalogue is synced with the shop on a schedule. The assistant queries price and availability of a named item in the shop at the moment of the answer; if the shop cannot be reached, it names the last synced state as such. What is missing from the catalogue the assistant does not name. When it shows a product, it does so via a product card with title, price, rating and button directly in the chat.
It puts together a cart in the chat that sits with XICBOT, not in your shop; checkout and payment stay in your shop. The cart tool type knows six kinds of change — set, add, update, remove, clear and coupon — with at most 99 units per position. In the chat this becomes a card with line items, total and a shipping line. Every change writes and therefore requires confirmation: the proposal stands in plain text, only the click executes it, and a one-time key prevents a second click from changing anything twice. The total is calculated with the current price from your shop or, if it cannot be reached, with the last synced price and its date; shipping costs and the free-shipping threshold come from the rules you store with the assistant. “Continue” opens your shop's stored address with a one-time pickup key that lets your shop fetch the cart from XICBOT through a read-only pickup address, provided it integrates that pickup itself. No order, customer account or checkout is created in the shop by this. More under cart assistant.
Yes. Besides the single recommendation, the assistant can contrast two products directly — price, key features and rating side by side — and suggest matching accessories as a bundle or complementary items in the sense of customers also bought. A comparison needs two items: if only one remains, it is shown on its own instead of faking a comparison. At most six hits are shown per answer, and only what is in your own catalogue is found — not even via a reference from another card. Which card types and suggestions appear is defined together for your assortment.
You store valid codes and running promotions on the cart tool, up to twenty promotions per tool, along with shipping costs and the threshold for free shipping. When the assistant applies a code, exactly one place calculates the cart, so what is displayed and what is handed over cannot drift apart. If a code does not fit, the guest gets a notice instead of a silent discount. Validity ends at the end of the stated day in German time and not in the time zone of the database. The voucher is not redeemed here: the code stays with the cart, and whether the discount is granted is your shop's decision. More under cart assistant.
It relieves support, it does not replace it. Recurring questions about availability, variants and delivery time are answered directly in the chat, including outside your business hours — and, as instructed, only from your knowledge base: sourced answers name their source, and figures, prices and deadlines that are not there are replaced with a notice. It gives the order status only once your inventory system is connected in the Custom package, and by default asks in the chat before looking it up. Cases that need people, such as complaints or special requests, are handed to your team: the conversation is marked as handed over, the request becomes an enquiry in your account, and your team is notified without the visitor having to repeat their details. That leaves your staff time for the demanding matters.
Through tools with a clearly set kind and approval mode. For order status there is a shape of its own that reads through the connection to your inventory system in the Custom package: it changes nothing, yet by default still asks for confirmation, because it is a personal matter. Alongside it are shapes for stock lookup and price lookup, which run without asking back, and a shape that changes an order and therefore works as a write with confirmation. Further adapters, also in the Custom package, cover calendar, CRM and ticketing. What the assistant may call is up to you: it is offered only what is active, and a tool that does not exist for this assistant ends as a failed call rather than as an invented answer. More under tool control.
Not in what you have set: your settings, your sources and your approvals belong to your assistant and stay as they are when the product changes. New tool types arrive as their own adapter file, without anything being rearranged on an existing tool; the model is offered only what you have entered and switched to active anyway. If a default behaviour changes that you never touched, the changelog states what applied before and what applies now. The widget parts also carry a version name derived from their content, with an integrity check: an unknown version is rejected instead of being silently replaced by another one.
The Pro package suits the shop assistant: operation from 149 € per month net plus a one-time setup from 2,900 € net for catalogue connection, training, product cards, cart and conversation analytics. Operation covers hosting in Germany, care, updates and data protection. Pro contains ten seats, five assistants, 50 knowledge sources and 2,000 documents with an allowance of 3,000,000 tokens per month. The cart handover returns an address of your shop with an attached pickup token; checkout and payment stay in the shop. All packages are listed under pricing; every project starts with a free initial consultation. All services can be cancelled monthly; there is no minimum term.
Yes, provided your inventory system is connected; that connection is part of the Custom package. The order_status type reads the order status through the connection to your inventory system and by default still asks for a confirmation in the chat, because it is a personal matter; the inventory_status type reads stock and runs without a query. Whatever the external system returns is filtered down to the result fields named in the adapter, text fields to 600 characters, lists to 20 entries; a reply without a confirmation field counts as a contract breach, not as a result. A change to the order runs through order_change, which writes and therefore requires confirmation. Deadlines and the process for a return are answered from your knowledge base; a disputed case is not decided by the assistant but handed over together with the conversation.
If your question is not among them, it usually sits at the interface to your own shop — catalogue fields, order system, permissions. The documentation describes the setup in detail; everything else we clarify in the first conversation, on your shop.
In the First Conversation
We sort your most frequent customer questions into three groups: answerable from the catalogue, answerable with read access to the shop or, in the Custom package, to a connected inventory system, and steps that change something and are therefore confirmed in the conversation. This shows which package fits and which details are still missing from the catalogue, before anything is commissioned. You read the answers against your own items before a customer does.
Tell us briefly about your shop — range, Shopware version and what the assistant should take on: advise, sell, answer delivery status through a connected inventory system (Custom package) or recommend accessories. You receive a clear assessment and, on request, a free demo with a test assistant for your shop. You can reach us by phone at +49 5123 9579000.