70.22 %
Around 70 percent of online shopping carts are abandoned
average across 50 separate cart abandonment studies collected by the Baymard Institute
Cart in the conversation, on into the shop
The Cart Assistant That Leads Into the Shop
The assistant does not talk about the cart, it puts one together. The tool knows six kinds of change — set, add, update, remove, clear, voucher — and anything outside that list does not quietly fall back to “set".
In plain language
The cart assistant helps people shop in the chat. It builds a cart together with the customer. It uses the prices from your shop. It checks whether a voucher fits. It also shows the shipping costs. Every change to the cart is a proposal first. The cart only changes when the customer clicks. Then it takes the customer to your shop.
Request a free demo View all prices
- Answers with a source reference
- Loads only after your consent
- No minimum term, cancellable monthly
Every change starts as a proposal the visitor confirms in the chat; only the click carries it out. The whole cart is calculated with the live price from your shop; if the shop does not answer, the price from the last sync applies and the assistant states when that was. The cart is held by XICBOT, not by your shop: “Continue” leads to your shop's address with a pickup token, and 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 the binding invoice is issued by your shop.
- 1.3 s
- to the first character of the answer, median
- XICBOT, own measurement series of 11 September 2026
-
Visitor:My voucher code is not being accepted.
-
Assistant:The code is valid but requires a minimum order value. Your cart is below it, 4.80 € are missing.
- Cart read · code checked · minimum order value not met
- Source: voucher rule, minimum order value field
-
Visitor:Then add the small pack.
-
Assistant:My proposal: add one pack, apply the code. Confirm it and I will carry it out — nothing changes before that.
- Proposal stored · state open · cart unchanged
-
Visitor:Yes, go ahead.
-
Assistant:Done. The cart has been recalculated and the discount sits on it. Whether the shop honours it at checkout is the shop's decision — the code is part of the cart.
- Cart updated · code applied · handover address ready
Ask it yourself, Assistant of this website
Automated assistantWhat the Cart Assistant Handles
In an online shop the most expensive point lies between “I like it" and “bought": around 70 percent of carts are abandoned. The figure does not say why — it only says how expensive the point is. The cart assistant starts where a question stays open: is my voucher valid? What does shipping cost? From when is it free? It does not only answer that, it changes the cart in the conversation and leads into the shop via “Continue”. This extends the shop assistant and the product cards by the part that writes instead of informs.
What the assistant does falls into two classes: describing and executing. Reading and calculating runs without a query. Changing the cart never runs without the visitor's click, and that is not a setting anyone can remove: every writing kind is hard-set to confirmation when the tool is created and when it is updated, no matter what the request asks for. Which further tasks make sense in retail is set out on the assistant for online shops page.
Puts Together the Cart and Changes It
The tool knows six kinds of change: set, add, update, remove, clear and voucher. An unknown kind does not quietly fall back to “set", it comes back as an error. A line item carries at most 99 pieces; a larger quantity belongs in a quotation, not in the chat.
- Six kinds of change, no silent substitute for an unknown one
- At most 99 pieces per line item
- Exactly one open cart per conversation
Calculates With the Live Price From Your Shop
After every change the whole cart is recalculated against the articles stored in your tenant, and with the price your shop on Shopware Community Edition states at that moment. The price is only read there if your package includes the shop connection; without it, or if the shop does not answer, the cart uses the price from the last sync and states when that was. A product that is not there ends the call with a message instead of inventing a price. The assistant holds no price or stock truth of its own; it holds a calculation resting on your data.
- Subtotal, discount, shipping and total all come from a single place
- An article without a catalogue entry ends the call instead of being estimated
- The interface does no calculating of its own, so no second discount appears there
Applies Vouchers and Says Where the Limit Is
A code the visitor names is checked strictly: kind as a percentage or a fixed amount, value, minimum order value, validity to the end of the named day in German time. What does not happen: the voucher is not redeemed here. The code stays with the cart; whether the discount is granted is your shop's decision.
- Percentage or fixed amount, value and minimum order value are all checked
- Validity ends with the named day in German time, not an hour earlier
- A code that no longer holds drops off the cart at the next calculation
- Redemption happens in the shop, not in the chat
Shows Shipping Costs and the Threshold
The calculation returns the shipping costs, the free-shipping threshold and the amount still missing to reach it. If no amount is given, that means one of two things: there is no threshold, or the cart is empty. It does not mean the threshold has been reached. A threshold without stored shipping costs is rejected at setup, because it promises the visitor something they already have.
- Shipping costs, threshold and missing amount stand in the same result
- No missing amount means: no threshold, or an empty cart
- A threshold without shipping costs is rejected at setup
Leads Into the Shop, With a Pickup Token
The cart is not completed here: no order, no customer account, no checkout. “Continue” leads to your shop's address with a random pickup token attached. Through a read-only pickup address at XICBOT your shop can fetch the cart with that token; for the items to sit in the cart there, your shop connects this pickup through an integration of its own. The token stands in that address and nowhere else: not in the transcript, not in what goes back to the model, not in the operator view.
- One random token per handover, valid for exactly one cart
- The token stands in the address and nowhere else
- Your shop completes the order, not the conversation
Writes Nothing Without Confirmation
Without confirmation only what is read-only and explicitly set to automatic will run. A call requiring confirmation ends in the state “proposed" and executes nothing. What the visitor reads before the click is stored in that form and not regenerated later — otherwise it would be impossible to tell afterwards what she clicked on.
- Writing tools never receive the “automatic" path
- A proposal simply sits there and changes nothing until the click
- Two simultaneous clicks execute the call exactly once
What the assistant does not bring along is your catalogue: articles, shipping rules and the voucher list come from your tenant, the prices from your shop. What is missing there is missing in the conversation — audibly so, not guessed at.
Limits
What the Cart Assistant Cannot Do
A page that only lists capabilities helps with no decision. The points below are in the code, not in the brochure. Knowing them tells you whether the assistant suits your own shop — and where a human is still needed alongside it.
- The assistant holds no price or stock truth of its own. It calculates with the live price from your shop, or else with the last sync and its date; what binds is what your shop states at checkout.
- The voucher is not redeemed here. The code is part of the cart your shop can fetch, and the shop decides on the discount.
- A missing amount to the shipping threshold that is not stated at all means “no threshold or empty cart", not “reached".
- A proposal expires after a limited time. After that a click carries out nothing, and the call ends in the state “expired" rather than “rejected" — nobody rejected it.
- A failed outbound call is not repeated. There is no second attempt, redirects are not followed, and the deadline is fixed at eight seconds.
- At most five tool calls run per answer. The sixth is recorded as capped rather than silently dropped, and once the quota is largely used up the limit falls to a single round.
- The prompt before an exit is absent on touch devices wherever it depends on the mouse moving towards the window edge: without a mouse there is no such movement.
- The public chat always runs in the role “public", even if an administration session happens to be open. Tools meant for signed-in roles are not available there.
-
Visitor:I need 200 pieces of that.
-
Assistant:A line item carries at most 99 pieces. I can create 99; for the remaining quantity a quotation would be the right route.
- Cart updated · line item 99 · per-item limit reached
-
Visitor:And how long does delivery there take?
-
Assistant:I find nothing about that in the stored documents. I will not guess; I am passing the question on to a person.
- No source found · gap recorded
-
Visitor:Fine, let us do it that way.
-
Assistant:Noted. The cart with 99 pieces is set, “Continue” takes you to the shop, and the query about delivery time is with the team.
- Handover address ready · handover to a person
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
The Shipping Threshold and the Prompt Before an Exit
Two points in the cart decide particularly often: the shipping costs and the moment just before the visitor leaves the page. In the product neither is a declaration of intent but mechanics, calculated in one case and triggered in the other — with fixed limits and one admitted gap.
The Shipping Threshold as a Calculation, Not a Slogan
The calculation returns three figures about the threshold: the threshold itself, the shipping costs that apply and the amount still missing. From these comes a hint the visitor can check herself. The limits are fixed: shipping costs up to one thousand euros, at most twenty voucher rules per tenant.
- Threshold, shipping costs and missing amount all come from the same calculation
- Calculating happens in a single place, so conversation and handover cannot drift apart
- A threshold without shipping costs is rejected at setup
- At most twenty voucher rules per tenant
The Prompt Before an Exit
The loader knows five triggers: time on page, scroll depth, inactivity, exit intent and return visit. At most five rules are allowed, and one visit produces a single bubble — the first rule whose event occurs wins, the rest are torn down. The path filter is a prefix, not a pattern: “/cart" also matches “/cart/checkout". All of this is evaluated in the browser of the page; what the server never learns it need not keep either.
- Five triggers: time on page, scroll depth, inactivity, exit intent, return visit
- At most five rules, exactly one bubble per visit
- Inactivity restarts on pointer, key, scroll and touch
- The exit rule is dropped entirely on touch devices
- The path filter is a prefix, not a pattern
- Evaluation runs in the browser, not on the server
The gap stands in the fourth line: where the prompt depends on the mouse moving towards the window edge, it does not exist on a phone — the other four triggers keep working there. What then stands out in the transcripts is shown by conversation analytics.
The question before the drop-off can be found
-
Filtered by state and period, the transcripts that ended before the handover stand together.
-
The switch for statements without cover shows where an answer had no source — that is the list your catalogue grows from.
-
The filtered selection can be saved as CSV and passed on in-house.
The Path from Product into the Shop
Six stages lie between the product question and the checkout. None of them is an intention; each is a place in the code where something is checked, calculated or refused. The assistant is embedded with a loader in your shop template, as described under integration.
-
Search the Catalogue
Product search knows four forms: search, compare, bundle and also bought. It returns at most six hits and at least one, exclusively from your tenant's catalogue. A named article number beats the search term; without either, a hint comes back rather than a result.
-
Create the Cart as a Proposal
The call ends in the state “proposed" and executes nothing. What the visitor reads before the click is stored in that form and not regenerated later, so that afterwards it remains traceable what she clicked on.
-
Have It Confirmed
Moving from “proposed" to “confirmed" is a conditional database write: two simultaneous clicks execute the call exactly once. The buttons in the widget additionally lock themselves after the first click. After the click, role and required fields are checked again, not only beforehand.
-
Calculate Against the Catalogue
Every change recalculates the whole cart, with the live price from your shop or, if it does not answer, with the last sync and its date: subtotal, discount from the voucher rule, shipping costs, threshold and total. An article without a catalogue entry aborts the call, because a cart carrying a price nobody can substantiate is worse than no cart at all.
-
Continue to the Shop
The handover returns your shop's address with a random pickup token; with it your shop can fetch the cart through a read-only pickup address at XICBOT, provided it has connected this pickup itself. Exactly one open cart remains per conversation — otherwise every quantity change would produce a different token and it would be unclear which one applies. The token stands in the address and nowhere else.
-
Read It Back in the Log
Every tool line carries key, kind, state, preview, input, result, error text, duration, approval path and the marker for a capped call. The approval path says whether it ran automatically or was confirmed by the visitor. A shortened version goes to the widget: duration and approval path fall away, and the error text is replaced by a general sentence.
Whatever is called twice in this chain still runs once. The key against double execution is built from conversation, tool and sorted input and lives in the database, not in the caller. When it catches, “duplicate prevented" comes back rather than an error — the visitor sees no red box for something that never went wrong.
Setup once, operation monthly
The cart assistant is part of the shop assistant based on Shopware in the Community Edition. What the setup costs depends less on the conversation than on your catalogue: articles, shipping rules and the voucher list have to be present in a form that can be calculated with.
- The cart is changed in the conversation and calculated against your catalogue
- Every change is a proposal the visitor confirms
- Voucher, shipping costs and threshold are settled before the checkout
- The link into the shop carries a pickup token and nothing else
- What the assistant cannot substantiate it declines instead of guessing
- The prompt before an exit is evaluated in the browser, not on the server
Pro package
from 149 € per month net
Minimum term: none, cancellable monthly
- Pro operation from 149 € per month net, setup from 2,900 € net
- Cart, voucher, shipping threshold and checkout in chat
- Product cards and shop connection based on Shopware CE
- Free initial consultation and demo with a test assistant for your shop
All prices net, plus VAT Source: XICBOT price list, as of 11 September 2026
The cart assistant belongs to the Pro package with shop connection (Shopware Community Edition), product cards, cart in the conversation and conversation analytics — operation from 149 € per month net, one-off setup from 2,900 € net for training and integration. Operation includes hosting in Germany, care, updates and GDPR. Ongoing services are booked individually and can be cancelled monthly; there is no minimum term. Before we quote, we look at your catalogue and tell you what is still missing there for the cart assistant.
Fewer Drop-offs Just Before Checkout
We go through the points where questions stay open in your shop just before the checkout and tell you which of them the assistant can answer from your catalogue and which it cannot.
Shop With and Without a Cart Assistant
The rows face each other in pairs: on the left the moment in the shop, on the right what happens at that same point when a cart assistant is present. The right-hand side names an action, not an effect — what follows from it is decided by your range, not by this page.
Shop without an assistant
- Open question at the moment of purchase: stays unanswered, the cart is left behind
- Putting together the cart: the visitor looks for product and button unaided
- Voucher and promotion: easily overlooked in the small print
- Shipping costs: visible only at the checkout
- Path to the cart: several clicks and page changes
- Exit: the visitor is gone, the question goes uncounted
With a cart assistant
- Open question at the moment of purchase: answered from your catalogue or explicitly declined
- Putting together the cart: the assistant proposes the line item, the click carries it out
- Voucher and promotion: calculated on the cart and visible, redeemed in the shop
- Shipping costs: cost, threshold and missing amount are settled before the checkout
- Path to the cart: in the conversation; “Continue” with a pickup token leads into the shop
- Exit: a rule speaks up, and the uncovered question appears in the list afterwards
The click separates the two columns. The assistant creates the line item as a proposal; it is carried out only once the visitor confirms. A second click on the same proposal creates no second item, because the bolt made of conversation and input sits in the database rather than in the interface.
The last row is the one with the longest afterlife: on an exit, the uncovered question stays in the list. It is then no longer a lost session but a detail missing from the catalogue or the knowledge base.
Starting Point and Action
We show no invented success stories. On the left stands the starting point as it occurs in shops, on the right the action the assistant performs there — not the outcome that is supposed to follow. What comes out in the end depends on range, prices and catalogue upkeep and can only be measured in your own shop.
Starting point
- Online shop: Carts are left behind just before the checkout, questions about shipping and vouchers stay open
- Retail / B2C: The free-shipping threshold is narrowly missed without anyone saying so
- Support: Product and shipping questions arrive by mail and delay the order
- B2B shop: A tiered quantity is hunted for in the form, and the cart stays at the single unit
- Shop with a voucher promotion: The code sits in the banner and nothing happens in the cart
- Range with variants: The wrong version sits in the cart and is only noticed on delivery
What the assistant does there
- Online shop: The question is answered from the catalogue, the line item created as a proposal and, after the click, taken into the cart in the conversation
- Retail / B2C: The amount missing to the threshold is calculated and named, the addition stays a proposal
- Support: The question is cleared in the conversation or explicitly handed to a person
- B2B shop: The assistant sets the quantity on the line item — at most 99 units per article — and changes the cart only on a click
- Shop with a voucher promotion: The assistant calculates the voucher on the cart and shows its effect; it is redeemed in the shop
- Range with variants: The assistant reads the version from the catalogue and swaps the line item using the same build form it created it with
What can be measured and what cannotWhether an assistant prevents exits in your shop is shown only by your own shop over a period we agree together. We supply no industry figure for that. What we do supply are the transcripts: what was asked, what was answered and where an answer had no source. In the initial consultation we look at which of these points occur in your shop at all.
Further reading: recovering abandoned carts in shop chat covers triggers, timing and the limits of speaking up, and product cards and cart in chat shows how product, quantity and checkout come together in one conversation. A wider view of everyday shop operations is offered by AI chat assistant for online shops.
Frequently Asked Questions About the Cart Assistant
Almost every question about the cart assistant comes down to the same thing: what really happens, and what only appears to happen. The answers below say both.
Can the assistant really add products to my cart?
It puts together a cart in the chat that sits with XICBOT, not in your shop. The matching product is found by the product_search tool type exclusively in the catalogue of your account; a stated article number beats the search term, and at most six hits come back. The cart in the chat is put together by the cart tool type with its six kinds of change, among them changing quantity and applying a coupon, and at most 99 units per position; the chosen variant belongs to the position. For shops we rely on Shopware in the Community Edition. What happens is your decision: every change writes and is presented in plain text before execution. “Continue” opens your shop's stored address with a one-time pickup key that lets your shop fetch the cart from XICBOT, provided it integrates that pickup itself. Checkout and payment stay in the shop. Together with the product cards and the shop assistant, information turns into a route into the shop.
How does the assistant handle vouchers and promotions?
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.
What is the point of the shipping threshold?
Many shops offer free shipping above a certain order value. From the cart rules you have stored, the assistant calculates how far the cart is from that threshold and points it out with a hint such as “only 5.30 € to free shipping". On request it suggests a matching addition. The rule is guarded against a pointless hint: a free-shipping threshold without stored shipping costs is rejected, so the assistant does not announce something that already applies anyway. The assistant only assembles the cart in the chat; payment happens in your shop — there is no separate price or stock truth on our side.
Can the assistant bring cart abandoners back?
It can speak up where the tab would otherwise close in silence. Proactive engagement knows five triggers and at most five rules per assistant; the path filter is a prefix, so you can limit the approach to the checkout area. The rules are evaluated exclusively in the browser on your page: scrolling, pointer movement and standstill do not reach the server. The rule for inactivity also listens to scrolling and the mouse wheel, because someone who is reading is not inactive. Whether it worked is something you read in conversation analytics: an abandonment counts as an open conversation without a handover, with at least one visitor message, that stayed silent for half an hour and led to neither enquiry, appointment nor cart. We promise no outcome.
What exactly does tool control mean?
Tool control means the assistant does not only read your connected systems but also operates them. Seventeen forms are available: seven in the core — capture a request, take an appointment request, hand over to a human, search the catalogue, put together a cart in the chat, query an external system, pre-fill a form on your site once the visitor confirms — and ten for calendar, inventory, catalogue, customer management and ticketing; querying an external system and these ten come in the Custom package. Every tool is registered as reading, writing or irreversible; confirmation is the default. Anything that does more than read is first shown as a proposal, and only a click by the visitor carries it out. Every call is then recorded in the log, with input, result, duration and the path by which it was approved. How your own processes can be mapped is shown on custom functions.
How does the assistant know my products, prices and availability?
XICBOT answers from the product catalogue — title, image, price, variants, availability, delivery time, rating and promotional prices. What is not in the catalogue the assistant does not show as a card, and it is instructed to invent neither product nor price. For a shop based on Shopware in the Community Edition the catalogue is taken from the shop and synced on a schedule; the assistant queries price and availability of a named item in the shop at the moment of the answer, and if the shop cannot be reached, it names the last synced state as such. With other shop systems you deliver the catalogue, and how current a card is depends on how often that happens. If someone puts together a cart in the chat, the price is calculated in exactly one place, so the chat cannot show a discount the handover does not know about; a voucher is redeemed in the shop. More on the shop assistant page.
Does this work with my shop system?
The cart assistant is designed for shops running Shopware in the Community Edition. It is embedded with a single script line; the chat runs in its own origin with no access to your document, and no stylesheet is pushed into your page. The cart tool type knows six kinds of change — set, add, update, remove, clear and coupon — with at most 99 units per position. Price and stock come from the shop: the assistant assembles the cart in the chat, and “Continue” leads to the shop address you have stored, with a one-time pickup key attached; for the items to sit in the cart there, your shop needs an integration of its own. Products are found by the product_search type exclusively in the catalogue of your account. More under cart assistant.
What does the cart assistant cost?
The cart assistant is part of the Pro package with shop connection, product cards and conversation analytics: operation from 149 € per month net and a one-time setup from 2,900 € net for training and integration. Operation includes hosting in Germany, care, updates and GDPR. The assistant assembles the cart and returns an address of your shop with an attached pickup token; checkout and payment stay in the shop. The free-shipping threshold and the shipping cost come from your rules; a threshold without a stored shipping cost is rejected. Details under cart assistant and pricing. All services can be cancelled monthly; there is no minimum term.
If your question is not among them, ask it in the initial consultation — or look at the frequent questions, where operation, data protection and installation are answered.
Before the quote
What Has to Be in Place for the Setup
The assistant brings the mechanics, not the data. Four things decide how far it can calculate in your shop — whatever is missing from them is missing in the conversation too.
- The catalogue with articles, variants and prices as they apply in the shop
- The shipping rules including costs and, where one exists, the free-shipping threshold
- The voucher list with kind, value, minimum order value and validity
- The address the cart is handed over to, and who is allowed to change it
Is Your Catalogue Ready for the Cart in Chat?
Tell us your shop address and in what form your catalogue exists — articles, shipping rules, voucher list. From that we will tell you what the cart assistant can handle in your shop and what is still missing for it. You can reach us by phone at +49 5123 9579000.