Shipping and delivery times: questions before buying

The cart is full, the pointer rests on the button, and then comes the question that decides the sale: what does shipping cost, and when will the goods arrive? In most shops both are written down somewhere, but rarely where the customer is currently reading. They would have to open the shipping page, work out their zone, estimate the weight and add the daily cut-off. They do not do it. They ask, or they leave. Averaged across fifty separate studies on cart abandonment, 70.22 % of online shopping carts are abandoned (Baymard Institute, as of 22 September 2025). A chat assistant can occupy this moment, but only on one condition: it has to take the answer from the shop's real shipping rules instead of from a plausible-sounding guess. This article shows which data that requires, how country zones, bulky goods and part deliveries are handled cleanly in the conversation, why a delivery time belongs in the answer as a range rather than as a promise, and what distance selling law demands in any case.

Enlarge graphic

Labels in the illustration

• Shop chat in the cart
• When does this reach me in Austria?
• Zone Austria, parcel shipping:
• 3 to 5 working days after payment.
• Surcharge from the stored zone table.
• And the table is bulky goods?
• Yes, the table goes by freight:
• 5 to 8 working days, with notice.
• The lamp follows as a part delivery.
• Read from the shipping rules
• A range is given, no fixed date is promised
• Write a message
• What the answer is built from
• Shipping methods, country zones, surcharges
• Weight, bulky goods and freight items
• Stock and daily cut-off per article
• Payment method, holidays and working days
• Delivery restrictions from the shop rules
• If one of these is missing, the assistant says so openly.
• Two paths, one question
• Guessed
• A date sounds concrete
• The date breaks later
• Complaint and return
• Wrong once, costly for long
• From the rules
• A range, not a date
• Zone and surcharge named
• Edge cases are named
• The answer holds up in practice
• Clear cost, timing and edge cases before the click instead of at the checkout

Answering shipping and delivery in the chat

The last question before the click

Shipping cost and delivery time are not a footnote but the final test before a purchase. Anyone who has made it into the cart has already accepted the product; all that remains open is what will be payable in the end and when the parcel arrives. This is exactly where a large share of purchases falls apart. The average across fifty separate studies on cart abandonment stands at 70.22 % (Baymard Institute, as of 22 September 2025). Not every one of those abandonments is caused by shipping, and not every abandonment is a lost customer: some are comparing, some are saving items for later. But the questions about cost and timing are the two that can be settled fastest when someone is ready at the right moment.

The information exists almost everywhere. It merely sits in three different places: the cost on the shipping page, the deadline in the delivery terms, the availability on the product page. For the customer this adds up to a calculation they never wanted to make. They would have to determine their zone, estimate the weight of the cart, know the cut-off time for the day and know whether the chosen payment method shifts the deadline. An assistant takes that calculation off their hands by assembling the parts that are maintained in the shop anyway. How an assistant works in the cart beyond that is described in the article recovering cart abandonment with a shop chat; the matching scope of functions is bundled by the cart assistant.

What must be stated before the order

The chat is not a legally exempt side room. For consumer contracts in electronic commerce, Section 312j(1) of the German Civil Code requires a clear statement, at the latest when the ordering process begins, of "whether delivery restrictions apply and which means of payment are accepted". The pre-contractual information duties themselves, among them the total price including all freight, delivery and shipping costs as well as the delivery and performance terms, are set out in Article 246a Section 1 of the Introductory Act to the German Civil Code. Anyone repeating this information in the chat is therefore not inventing it but restating it. That is precisely why the data source matters more than the wording.

This maximum applies where no performance time has been agreed and none follows from the circumstances either. It is a fallback value, not a usual delivery time, and above all it shows one thing: as soon as a date is named in the conversation, a statement comes into existence that the shop will be measured against. An assistant answering "the day after tomorrow" on a hunch sets a deadline nobody has checked. If it passes, what remains is not a misunderstanding in a chat but a complaint with a timestamp and a transcript. The difference between a reliable answer and a guessed one is therefore not a matter of style here but a matter of data.

Why guessing is especially expensive here

An invented delivery time is not a small error, because it only surfaces days later and then with someone who has already paid. By then the wrong statement has set off a chain: the customer has planned around a date, ordered the goods for an occasion, perhaps decided against an alternative. When the date breaks, first comes a query, then a complaint, often a return and in many cases a public review. The effort has moved out of sales and into service. An assistant that merely guesses shifts work from the moment of purchase into the aftermath, and makes it more expensive on the way.

The way out is uncomfortable and effective at the same time: where a basis is missing, no figure is given. In our own measurement series 8 out of 8 questions without a basis were declined instead of guessed (XICBOT, own measurement series of 11 September 2026); eight questions deliberately placed outside the available material were tested, and the wording of every answer is in the measurement file. The sample question concerned contact details that were not on file; the behaviour is the same for a shipping zone that is not on file. It can be read up under measurement series; how this binding to your own material is achieved technically is described in the article preventing hallucinations with a knowledge base and RAG.

The real shipping rules as the basis

For an answer to be reliable, the assistant needs read access to the places where the shop keeps its shipping logic. As a rule those are the shipping methods with their zones and price tiers, the article master data with weight, dimensions and a bulky-goods flag, the stock level with replenishment time, and the configuration for cut-off times and working days. With Shopware in the freely available Community Edition, the article's delivery time and availability come from the shop, the other shipping details from the stored settings and the knowledge base; the checkout is not touched. Which actions are permitted is defined through tool control; which product data an assistant can evaluate at all is set out on the shop assistant page.

• Shipping methods per zone with price tiers, free-shipping threshold and surcharges, in the version the checkout also calculates
• Article weight, dimensions and bulky-goods flag, so that parcel and freight items are kept apart
• Stock, replenishment time and pre-orders per variant rather than per article only
• Cut-off time, definition of working days and the holiday calendar of the dispatch warehouse
• Payment methods with their effect on the start of shipping, for instance with prepayment or a payment check
• Delivery restrictions, excluded zones and articles that cannot go to every country

Whatever cannot be read from the system belongs in the maintained knowledge base: special rules for promotional periods, behaviour during strikes or storms, the handling of requested delivery dates. What matters is that there is an owner and a cadence for it, otherwise the text ages faster than the shipping matrix. What such a maintenance process looks like and who carries it is described in the article building a knowledge base: what content belongs in it. The split is deliberate: figures come from the shop, rules and exceptions from the knowledge base, and each is checked separately.

Country zones and what lies outside them

As soon as a shop delivers across the border, a shipping statement turns into a table. Zones group countries together, but rarely the way a customer expects: Switzerland lies outside the customs union, individual island groups and overseas territories belong to a country and still sit in a zone of their own, and some articles may not be exported at all for reasons of dangerous goods or approval rules. To the visitor all of this looks the same: an address in a form field. For the calculation it is the difference between parcel shipping, a surcharge and a refusal. An assistant that determines the zone from the destination country named and states the matching rule replaces a table nobody reads voluntarily.

Bulky goods, freight and the delivery notice

As soon as an article no longer fits into a parcel, everything about the answer changes: the price, the deadline, the carrier and the process at the customer's end. Freight items are announced in advance, arrive within a time window, often stop at the kerb and sometimes need two people. Anyone answering a blanket "two to three working days" in the chat because that is true for parcels creates an expectation for a sofa that nobody can meet. The distinction usually exists in the shop already, as a flag on the article. It only has to be carried through into the answer.

A form cannot do this, because every one of these follow-up questions pulls another one after it. The customer only knows what to ask next once they have the answer, and a form only knows one move. This is exactly where a conversation has the advantage over a page of shipping information: the assistant can ask for the condition that decides this particular case. How conversation, form and live chat otherwise differ is compared in the article chat assistant, form or live chat.

Part delivery: one cart, several parcels

The normal case in retail is the mixed cart: one article in stock, one on replenishment, one from a second warehouse. The customer's question is nevertheless in the singular: "when will my order arrive?" An honest answer here has two parts, namely the earliest and the latest deadline, plus the decision that goes with them. Because as a rule the customer has a choice: wait until everything is ready to ship together, or have it delivered in parts. Both have consequences for cost and timing, and they should know both before ordering, not afterwards.

• Ship together - one parcel, one deadline governed by the slowest article. Sensible where replenishment is short and the parts belong together.
• Part delivery - the available part goes out immediately, the rest follows. Sensible for urgent needs, but the rule on shipping costs for the second consignment must be settled beforehand.
• Swap the article - an available variant replaces the sold-out one. The assistant may suggest this but must never do it silently, and must name the difference.
• Remove the line - the cart is trimmed by the article that dictates the deadline. This is the fastest solution and the one offered least often.

The order matters: first describe the situation, then offer the choice, never make the choice on the customer's behalf. An assistant that switches to a part delivery on its own initiative changes the cost structure of an order, and that is no longer an answer but a decision. Where such a change really is to be carried out, it belongs in the integration as a permitted action and not in a free-form reply. How cards and cart work together in the conversation is shown in the article product cards and cart in the chat; the purchase itself, including payment, stays with the shop's regular checkout in every case.

Delivery time as a range, not a promise

A delivery time is a chain of four links: picking in the warehouse, handover to the carrier before the cut-off, transit within the zone and the delivery attempt at the recipient. Each link has its own spread, and only the first two are within the shop's control. That is why the right form of answer is a range in working days with the conditions alongside it: from when it counts, what shifts it, what it depends on. This is not an evasion but the only form that still holds when a public holiday falls in between. Naming a date instead promises the precision of a chain that the shop only controls by half.

What can be measured and what cannot

Shipping questions are one of the few kinds of conversation that can be counted cleanly, because they almost always contain the same terms. Conversation analytics shows how often cost, deadline, zone or bulky goods are asked about, what share of that could be answered from the rules and where conversations end without a result. If questions about one particular zone pile up, what is usually missing is a piece of data in the shop rather than in the assistant. That turns the analysis into a tool for the catalogue and not only for the chat. How to use this analysis day to day is deepened in the article evaluating and optimising chats.

• Share of conversations in which shipping cost or delivery time comes up at all
• Share of those answered from the stored rules without a follow-up question
• Cases where a piece of data was missing, together with the zone or article group behind it
• Handovers to a member of staff, split by reason rather than counted only
• Recurring customer phrasings that are missing from the search and the catalogue

What cannot be measured is the revenue that would have been lost without the assistant, because there is no comparison group for it. A specific increase in revenue or conversion rate therefore cannot be assured; it depends on range, prices, target group and competition. What can be influenced are the factors that sit in your own house: complete shipping rules, a clear line between an answer and a promise, and a handover to a human as soon as a case falls outside the pattern. How that handover succeeds cleanly is described in the article AI assistant: handover to staff; how an assistant fits into an existing shop is shown in the article embedding an AI assistant in website and shop. How the shop assistant answers shipping and delivery time questions from your stored rules is shown on the product page; we are happy to look at your shipping rules with you via the contact page.

Frequent questions