AI Chatbot CSV Price List: Prepare the File

An AI chatbot CSV price list is the quickest way to teach a chatbot what things cost, and the easiest way to teach it something wrong. A spreadsheet looks tidy to a person, but a chatbot reads it as text. If a row says “XL, 49” without saying what the 49 is, or if a column holds your cost next to your price, the chatbot will quote what it finds. This guide shows how to prepare a price file that gives correct answers, what to leave out, how to keep it current and how to test it before visitors see it.

Talkmio is an AI live chat for websites. Its assistant, Mio, answers from your website, FAQ and uploaded documents, and files in the knowledge base can be PDF, DOCX, TXT, MD, CSV or HTML, up to 15 MB each. Mio never invents prices or policies, so the quality of your price list is the quality of the price answers.

When an AI Chatbot CSV Price List Is the Right Tool

A CSV file suits data that is naturally a table: a service menu, a catalogue of products with a few attributes, rental rates, tuition fees, shipping zones or a parts list. It is the wrong tool for explanations, policies and anything that needs paragraphs. For those, write a normal page or a question and answer pair, and let the CSV carry only the numbers and names.

If your prices already live on public pages, Mio reads them when it crawls your site. A CSV helps in three situations: the prices are not on the website, the website shows only “from” prices while the real list is longer, or the data changes often and you export it from another system. In each case the file becomes one more knowledge piece, and Mio combines it with the rest of your content.

Source of prices	Best format	Reason
A few fixed plans	Web page or question and answer pair	Needs explanation, not rows
Hundreds of products with attributes	CSV	Rows map cleanly to products
Quotes and offers with terms	PDF or DOCX	Layout and conditions matter
Prices that change weekly	CSV exported from your system	Easy to replace and re-read
Prices that depend on a customer	Do not publish in chat	Hand over to a person

Make Every Row Self-Contained

The most important rule is that each row must make sense on its own. A chatbot may retrieve a single row without the rows around it or the header above it. Think of every row as a sentence: it should name the thing, state the variant, give the price, the currency and the unit, and say what the price includes.

product,variant,price,currency,unit,includes_vat,note
Gift box small,12 chocolates,19.90,EUR,per box,yes,Ready to ship in 2 working days
Gift box large,24 chocolates,34.50,EUR,per box,yes,Ready to ship in 2 working days
Wedding favour,single piece,2.40,EUR,per piece,yes,Minimum order 50 pieces

Compare that with a row such as “GB-S, 12, 19.9”. A person who knows the shop can decode it. A chatbot cannot, and a customer should never see a code. Use the name the customer uses, the way it appears on your website and in your product pages. If your catalogue has internal codes, keep them out or put them in a column the customer would also recognise, such as the code printed on the box.

Write units and currency in every row

“Per night”, “per hour”, “per square metre”, “per month” and “one-off” change the meaning of a price completely. State the unit in its own column. Do the same with the currency, using a plain code such as EUR or USD, and use one currency per file unless the column is explicit. The ISO 4217 currency codes are a good standard to follow.

Choose Clear Columns and Keep Them Few

A price list with thirty columns is not more informative to a chatbot, it is more confusing. Keep the columns a customer might ask about: name, variant or size, price, currency, unit, whether tax is included, availability notes, lead time and one short note. Move everything else to another file or delete it.

Header names in plain words. Use “price”, not “p1_net_eur”.
One value per cell. Do not put “19.90 / 24.90 with engraving” in one cell; use two rows or two columns.
No merged or blank cells. Repeat the product name on every row instead of leaving it empty under a group heading.
Consistent decimal format. Pick a dot or a comma and keep it throughout.
Text in one language per file. Mio can answer across languages, but a file that mixes two languages in one column makes retrieval harder.

Save It Correctly: Format and Encoding

A CSV file is plain text with values separated by commas. The simple format is described in the CSV specification, and the overview of the format lists the common variations. Three habits prevent most problems.

Save as UTF-8. Otherwise accented letters, euro signs and non-Latin alphabets turn into garbage and Mio may quote broken names. A short note on choosing character encodings explains why.
Quote cells that contain commas. A note such as “Ready to ship, 2 working days” must be wrapped in double quotes, or the row shifts.
Open the saved file in a text editor. If it looks like clean rows, it is ready. If you see a single long line or strange symbols, export again.

Keep each file well under the 15 MB limit. In practice, a price list is tiny, but a full product export with long descriptions can be large. Split a very large export by category, such as “prices-kitchen.csv” and “prices-garden.csv”, which also makes updates easier.

Leave Out What Must Never Be Quoted

This is the step people forget, and it is the most expensive mistake. Anything in the file can end up in an answer. Before you upload, delete columns that contain your purchase cost, margin, supplier names, wholesale or trade prices, staff discounts, customer-specific prices, internal comments and anything marked “do not share”. The safest rule is to export only what you would be happy to see printed on your public price page.

If you have trade prices for registered customers, do not put them in the public knowledge base. Our guide on sensitive topics for an AI chatbot explains what to keep out of the chat. Also keep the Business instructions in step with the file: if Mio must never negotiate or promise discounts, say so there.

Add Dates, Validity and Exceptions

Prices change, and a visitor who sees a quote from last season is a visitor who will argue with your team. Put a “valid from” date in the file name and in a column, and add a column or note for exceptions such as minimum order, delivery charges or a surcharge for remote areas. Write promotional prices as separate rows with their own validity dates rather than overwriting the regular price. When the promotion ends, delete the row, upload the new version and use the re-read option so the old answer disappears.

If the price list conflicts with your website, Mio sees two sources. Our article on conflicting sources explains why this causes hedged or inconsistent answers and how to settle which source is right. The simplest policy is to have one owner for prices and one routine that updates the site and the file together.

Common Mistakes in a Price File

A few errors appear again and again, and each is easy to avoid. The first is mixing tax-inclusive and tax-exclusive prices in the same column, so that the chatbot cannot say which is which. Give each price its own flag or keep to one rule across the whole file. The second is using ranges such as “20-30” without saying what decides the final price. If the price depends on size, material or quantity, split the range into rows. The third is leaving out the conditions that customers ask about next: minimum order, delivery fee, setup fee and the date the price was last checked.

A fourth, quieter mistake is copying marketing text into cells. Long sales descriptions make the file heavy and push the numbers out of sight. Keep the cell text short and put the explanation on a normal page, where Mio can find it separately.

Upload, Test and Review the Answers

In Talkmio, open Mio AI, then Knowledge base, and add the CSV as a file.
Open Try Mio and ask the ten questions customers ask most: “How much is the large box?”, “Is VAT included?”, “Do you have a minimum order?”
For each answer, look at which knowledge pieces were used. Confirm that the CSV row was the source for price questions and that the number matches.
Ask questions the file cannot answer, such as the price of a product you do not sell. Mio should say it does not know and hand over, not guess.
Ask in another language. Mio replies in the visitor’s language and can answer from content written in a different one.
Ask a vague question, such as “What is the cheapest option?”, and check that the answer is correct and does not invent a comparison your file does not support.

Keep your test questions in a list. After every update of the file, run the same list again. It takes five minutes and catches the most common errors: a shifted column, a missing currency or a price that changed in one place and not another. Our guide on pricing questions in an AI chatbot adds advice on wording and on questions that must go to a person.

Keeping the AI Chatbot CSV Price List Current

A price file only helps if it is current, so assign an owner and a rhythm. For a small shop, that may be a monthly check and a quick update before each sale. For a business that exports from a system, it may be a scheduled export that someone uploads. Either way, the routine is the same: replace the file, use the re-read option, run your test list and note the date.

Remember what a CSV cannot do. It is a snapshot, not a live feed, so do not let Mio promise stock levels or delivery dates that change by the hour. Mio hands over questions about a specific order to your team, which is the right place for them. Put general lead times in the file and say “typically”, and keep real-time stock questions for a person. If you need a broader introduction, the guide to building an AI chatbot from a PDF covers the document side, and training a chatbot on website content covers the pages.

Frequently Asked Questions

Can I train an AI chatbot on a CSV file?

Yes. In Talkmio you can add CSV files to the Mio knowledge base, along with PDF, DOCX, TXT, MD and HTML, up to 15 MB each. Mio answers only from your content, so a clean file with self-contained rows gives accurate answers, and a messy file gives confusing ones.

How large can the file be?

Up to 15 MB per file in the knowledge base. Most price lists are far smaller. If you export a large catalogue, split it by category, which also makes updates easier. The plan you choose limits how many knowledge pages Mio can keep, so check your plan limit too.

Should I include my cost or margin columns?

No. Anything in the file can end up in an answer. Remove cost, margin, supplier names, trade prices and internal notes before you upload, and export only what you would print on your public price page. Check the file in a text editor once more before adding it.

What happens if a price is missing?

Mio never invents prices or policies. If it cannot find the price in your content, it tells the visitor it is connecting them with a person and the chat appears in your Inbox with the full history. Add the missing row, re-read the source and test again.

How do I update prices without breaking answers?

Replace the file, use the re-read option and run your list of test questions in Try Mio. Remove expired promotional rows instead of leaving them, and add a valid-from date to the file name so you always know which version is live.

Does the chatbot work with other languages?

Yes. Mio replies in the language the visitor writes in, and a question in one language can be answered from a file written in another. Keep each file in one language, and check a few answers in your main customer languages before launch.

The Bottom Line

A good AI chatbot CSV price list has self-contained rows, plain column names, units and currency in every row, UTF-8 encoding, validity dates and nothing you would not print publicly. Test it with a fixed list of questions, update it with a routine and leave order-specific questions to a person. Start free with Talkmio, upload your file to the knowledge base and see whether Mio quotes the numbers you would.

AI Chatbot CSV Price List: How to Prepare Your Spreadsheet