Skip to content
Back to blog

Shipping Questions Chatbot: What to Answer and How to Set It Up

Which shipping questions shoppers ask, what data a chatbot needs to answer them, and how to set one up on WooCommerce or a product feed, with a human handoff.

A shipping questions chatbot is an assistant on your store that answers the same handful of questions shoppers ask before and after they buy: what shipping costs, how long it takes, whether you ship to their country, and where their order is. It works when it reads from your real shipping policy and product data, and when it knows when to pass a conversation to a person. This guide covers the questions to prepare for, the data the bot needs, a setup path for WooCommerce and product feeds, and how to tell whether it is working.

Konvuno
Answer Shipping Questions From Your Site
Konvuno answers visitor questions from your website content and product catalog, and can hand off conversations when a person needs to respond.
Visit Konvuno

TL;DR

  • Shipping questions fall into two groups: general policy questions (cost, speed, destinations, duties) and order-specific questions (tracking, address changes, lost parcels). They need different data.
  • A bot can answer policy questions from a clear, current shipping policy and your product feed. Order-specific questions need carrier and tracking data, or a handoff to a person.
  • When the bot is unsure, it should ask a clarifying question or hand off. It should never guess a delivery date.
  • Track what shoppers actually ask, fix the gaps in your policy, and watch how many chats still need a human.
  • Konvuno installs with one script tag, syncs WooCommerce and Google Merchant or Facebook feeds, and is configured from a dashboard.

Table of Contents

Why shipping is the question shoppers ask most

Shipping is where a purchase is won or lost. In AlixPartners’ 2024 Home Delivery Survey, 92% of surveyed U.S. consumers said free-shipping availability affects their purchase decisions, and 92% said a delayed order would affect their next purchase. Shoppers who cannot find a cost or a delivery estimate often leave rather than email you.

For a small store without a support team, this creates a daily grind. The questions are repetitive, they arrive at night and on weekends, and the answers already exist somewhere on your site, usually buried in a policy page. That is the case for a chatbot: it does not replace your judgment, it puts the answer where the question is asked.

The shipping questions to prepare for

Look at how large retailers organize their own help pages, because they have already counted what customers ask. Zappos’ shipping FAQ covers shipping costs, delivery times, expedited shipping, international and special-address shipping, tracking, address changes, restrictions, return-shipping charges and signature requirements. That list is a good skeleton for any store.

Before the purchase

These are general questions. The answer does not depend on who is asking, only on the product and the destination.

  • How much is shipping, and is there a free-shipping threshold?
  • How long will delivery take, and is there an expedited option?
  • Do you ship to my country, to a PO box, or to a military or special address?
  • Will I owe customs duties or taxes on arrival?
  • Are there products you cannot ship to my location?
  • What is your return shipping policy, and who pays?

International shoppers add their own layer. OluKai’s international FAQ treats as separate questions whether the delivery address can be changed, how international tracking works, what the return and exchange rules are, and how long refunds take.

After the purchase

These are order-specific. The bot needs to know who the shopper is and what they ordered.

  • Where is my order?
  • Tracking has not updated in days. What now?
  • I entered the wrong address. Can I fix it?
  • My parcel came back to the sender.
  • An item is missing or wrong.

Zappos tells customers who entered an incorrect address to contact support before the order ships, which is a perfect example of a rule your bot should state plainly and then route to a human. MOZA’s help page likewise lists tracking that has not updated, a parcel returned to sender, refused deliveries, and missing or incorrect items as their own questions, each with its own answer.

If you want more ideas for where a bot earns its keep across a store, these examples of AI in ecommerce show how stores apply it beyond support.

General answers versus order-specific answers

The most common mistake is treating all shipping questions as one problem. They are two, and they need different inputs.

General shipping questions Order-specific questions
Examples Cost, speed, destinations, duties, returns Tracking, delays, address changes, missing items
Data needed Shipping policy, FAQ, product feed Order record, carrier, tracking number
Who can answer A bot, fully A bot with an order integration, or a person
Risk if wrong Misleading promise on the product page Wrong delivery date, angry customer
Good default Answer and cite the policy Collect order number, then hand off or look up

For order-specific lookups, the platform has to expose the data. Shopify’s documentation, for example, says fulfillment tracking can expose the carrier, tracking number and tracking URL and allows later updates to that information. Its event documentation lists fulfillment events such as pending, success, cancellation and updates, which can feed order-status replies. The principle holds on any platform: if the bot cannot see the order, it should not pretend to.

The honest design for a small store is this. Let the bot handle every general question on its own. For order-specific ones, have it explain the standard process, link the carrier’s tracking page when the shopper has a tracking number, and offer a human when something has gone wrong.

Prepare your shipping information first

A chatbot is only as accurate as the page it reads. Before you configure anything, write down a clear, current shipping policy. Bench Accounting’s guidance says it should cover delivery times, costs and methods, tracking, restrictions, international shipping and returns, and should be updated as customer feedback or operations change. Their April 4, 2025 article also lists the topics a practical shipping FAQ should answer: international destinations, estimated delivery times and costs, duties or taxes, tracking status, late or missing orders, and return-shipping responsibilities.

A checklist you can work through in an afternoon:

  1. Costs. List every rate, by method and destination, and any free-shipping threshold.
  2. Timing. Separate handling time (how long you take to pack) from transit time (how long the carrier takes). Shoppers blur them, and so will a bot if your page does.
  3. Destinations. Name the countries and regions you ship to, and the ones you do not.
  4. Duties and taxes. State who pays at the border, in one sentence.
  5. Exceptions. Oversized items, restricted goods, holidays, PO boxes.
  6. Problems. What happens with a lost, late, damaged or wrong item, and who to contact.
  7. Returns. Who pays return shipping, and how refunds are timed.

Write each as a short, direct statement, not a legal paragraph. “Orders placed before 2 p.m. Eastern ship the same business day” is easy for a bot to quote. A vague “we ship promptly” is not.

Set it up on WooCommerce or a product feed

There are two sources of truth to connect: your shipping rules and your products.

Your shipping rules

In WooCommerce, shipping is built on zones. According to the WooCommerce documentation, shipping zones determine the shipping options and rates customers see at cart and checkout, so they are the right place to confirm your numbers before a bot repeats them. If your zones say domestic orders ship by flat rate and your policy page says something different, fix that first. The bot will otherwise inherit the contradiction.

Copy the same facts into your knowledge base in plain language: a shipping page, a returns page, and a short FAQ. This is the layer that answers general questions.

Your products

Product-level questions mix with shipping ones: “Is this in stock, and can it arrive by Friday?” or “Does this ship to Canada?” For these, the assistant needs live product data. If you publish a Google Merchant or Facebook product feed, or run WooCommerce, a catalog sync keeps prices and availability current without you editing answers by hand.

How this works in Konvuno

Konvuno is built for exactly this setup. Here is the path:

  1. Add the single script tag to your site. No developer is needed.
  2. In the hosted dashboard, add your shipping policy, returns policy and FAQs as knowledge.
  3. Connect your WooCommerce store or paste your Google Merchant or Facebook feed URL. The catalog syncs automatically, so product, price and availability answers stay current.
  4. Preview the assistant and ask it your own shipping questions before you go live.
  5. Turn on human handoff for the topics you want a person to own, such as address changes and lost parcels.

Because the assistant answers from your own content and catalog, shipping answers match what is on your site. It also speaks 7 languages, which matters when your international shoppers ask about delivery in their own language. If you serve several language markets, this look at multilingual customer support explains why answering in the customer’s language builds trust.

Handle uncertainty, delays and exceptions

The shipping bots that annoy people are the ones that guess. Microsoft’s human-AI interaction guidance for designing assistants says that when the system is unsure of the user’s goal, it should ask for clarification or gracefully limit its services instead of guessing. Apply that to shipping in four ways.

Ask before answering. “How long does shipping take?” depends on the destination. A good bot asks for the country or ZIP code, then answers.

Never promise a date you do not control. Quote your stated delivery window and say it is an estimate. Carriers delay parcels, and a firm date from a bot becomes a broken promise.

Admit the limits. If the bot cannot see an order, it should say so and offer the next step: the tracking link, a form, or a person.

Hand off with context. When a shopper reports a lost parcel or a wrong address, the human should receive the conversation, the order number and the question, so the customer does not repeat themselves.

A simple rule of thumb for what to route to a person:

Situation Bot action
Standard cost, timing, destination question Answer from policy
Customs and duties for a specific country Answer with your general statement, point to the carrier or customs authority for exact charges
Tracking has not updated Explain typical delays, share link, offer human
Wrong address after ordering Collect order number, hand off immediately
Lost, damaged or missing item Apologize, collect details, hand off
Angry or repeated message Hand off

A shipping-ready test before you go live

Pretend to be a shopper and ask your own bot every question in the lists above. Then try the awkward versions:

  • “Can you ship this to Hawaii?”
  • “I ordered yesterday, why hasn’t it shipped?”
  • “Do I pay taxes if I’m in Canada?”
  • “Can I change my address?”
  • A question in another language you support.

Every wrong, vague or overconfident answer points to a gap in your content, not a flaw in the idea. Fix the source page, not just the reply.

We see it differently: your policy page is the product

We build Konvuno for owners who run a store without a support team, and we see the same pattern. Owners expect the AI to be the clever part. In practice the clever part is the shipping policy you write.

We see it differently: your policy page is the product — overview diagram

A bot that reads a clear page gives clear answers. A bot that reads a muddled page gives confident, muddled answers. So we push owners to spend an hour tightening the policy before they touch any setting, and to use the preview to read every answer as a customer would. The dashboard’s conversation log and analytics on what visitors ask then become your editorial calendar: each unanswered or escalated question is a sentence missing from your policy.

We also believe the owner, not a developer, should control this. Shipping rules change with carriers, seasons and suppliers. If updating an answer needs a ticket to someone else, it will not get updated. That is why configuration and preview happen in the hosted dashboard, with no per-seat pricing to discourage you from giving a teammate access.

— Konstantin

Measure whether it is working

You do not need a complicated report. Track a few numbers weekly:

  • Shipping questions asked. Which ones come up most? Move the top three onto your product and cart pages too.
  • Handoff rate. How many shipping chats still need a human? A falling rate for general questions is good. A steady rate for order problems is normal.
  • Unanswered questions. Each one is a content gap. Add the answer to your knowledge base.
  • Repeat emails. Compare the volume of shipping emails before and after launch.
  • Cart behavior. Check whether shoppers who chat about shipping go on to check out.

Conversation analytics in Konvuno show what visitors ask, so you can read the questions yourself rather than guessing. Review them weekly for the first month, then monthly. Update the shipping policy whenever a carrier, rate or destination changes, and the bot follows.

Try it on your own store

Konvuno plans start at €29 per month for Starter, with Growth at €79 per month and Business at €199 per month. Every plan includes full conversational catalog capabilities, and you can configure and preview the assistant before you pay. Compare the plans on the Konvuno pricing page and see how your own shipping policy sounds in the assistant’s voice.

FAQ

Can a chatbot answer where my order is?

Yes, if it can see your order and carrier data, or if it can send shoppers to the right tracking page. Without that access, it should explain how tracking works, ask for the order number and offer a human. It should never invent a status.

What shipping questions should a chatbot answer first?

Start with cost, delivery time, destinations, duties and returns, because they are the same for every shopper and come straight from your policy. Add order-specific questions once your general answers are accurate.

How do I stop a chatbot from giving wrong delivery dates?

Give it only your stated delivery windows, label them as estimates, and have it ask for the destination before answering. Where the bot is unsure, it should clarify or hand off instead of guessing.

Does a shipping chatbot work with WooCommerce and product feeds?

It can, as long as the assistant supports catalog sync. Konvuno syncs WooCommerce and Google Merchant or Facebook product feeds automatically, so product, price and availability answers stay current. Shipping rules still belong in your policy content.

Sources