AI Chatbot for Webshops: Order and Return Questions

The questions that fill a webshop inbox

Look through a month of support email in almost any small webshop and the same pattern appears: where is my order, can I change the address, how do I return this, when do I get my money back, and the product arrived broken. The first four are lookups against data you already have. The fifth needs judgement. A well-built chatbot handles the lookups instantly, at any hour, and routes the judgement cases to you with the facts already collected.

The mistake is starting with the language model. Start with the list of questions, the system that holds each answer, and what the bot is allowed to do about it. That list becomes the specification for the integration.

Connecting order and tracking data

Shopify and WooCommerce both expose orders through an API, and the Swedish carriers most shops use, such as PostNord, DHL, Budbee and Instabox, provide tracking events either directly or through a shipping platform. The bot should call these as tools: look up an order, read its fulfilment status, fetch the latest tracking event. It should never invent a delivery date.

Keep the access read-only wherever possible. If the bot must write, for example to register a return, give it one narrow action rather than broad admin rights. We cover how to stop a bot from improvising answers in our guide to chatbot hallucinations.

Returns and the 14-day right of withdrawal

Under the Swedish Distance Contracts Act, consumers can withdraw from most online purchases within 14 days of receiving the goods, without giving a reason. The bot can check the delivery date, confirm the customer is inside the window, issue a return label and tell them the refund rules: you must refund within 14 days of the withdrawal, but you may wait until the goods are back or the customer shows they have been sent.

• Exceptions matter: sealed hygiene products once opened, custom-made goods and perishables are not covered. Put them in the bot's rules explicitly.
• If your own return policy is more generous, such as 30 days, the bot should apply your policy, not the legal minimum.
• A withdrawal is not a complaint. A faulty product falls under the Consumer Sales Act with up to three years to complain, and that is a human case.

For the full picture of the consumer rules, see distance selling rules in Sweden.

Identity checks before sharing order info

An order record contains a name, an address and what someone bought. Handing that to anyone who types an order number is a personal data breach under GDPR. The simple rule: two factors that only the buyer should know, typically the order number plus the email address or postcode on the order.

1. Ask for the order number and email together, and only confirm a match or no match.
2. Never read out the full delivery address; show the town or the last characters at most.
3. Limit failed attempts per conversation to stop guessing.
4. If the customer is logged in on your site, use that session instead of asking again.
5. Log what the bot disclosed, so a complaint can be investigated.

Hand-off for complaints, and when you do not need this

Complaints, damaged deliveries, chargebacks and anything involving money beyond a standard refund should go to a person. The bot's job is to collect the order number, photos, a description and the customer's preferred contact, then create a ticket so you do not have to ask again. An angry customer who gets a fast, informed human reply is often easier to keep than one who argued with a machine.

When not to buy this: if you ship a handful of orders a day, a good order-status page, automatic tracking emails and a clear returns page will remove most questions at almost no cost. A connected chatbot makes sense when order questions take real hours every week, or when customers write outside office hours and expect an answer. Our AI chatbot setup is built for that case; if you are unsure which side you are on, book a short call and bring a sample of your inbox.

Frequently asked questions