Can ChatGPT update supplier price lists?
Sooner or later someone asks it: the supplier sent a 300-line price list, ChatGPT is open in the next tab, so why not paste it in and ask for the changes? It is a fair question, and the honest answer is "partly". A general AI chat assistant is good at some of the steps in a price update and risky at others. This guide separates the two so you can use one sensibly, and says when a dedicated tool is the better choice.
The comparison here is between a general AI chat assistant, such as ChatGPT, and a tool built for the single job of supplier price lists. No claims are made about any specific chat product's features, limits or accuracy, because they change often. The points below are about the kind of tool.
What the job asks of a tool
A price update is not one task. It is a chain, and an error anywhere flows to the end. The tool has to read the supplier's file completely, including every page, sheet and table; match each line to one of your items; work out each change in currency and percent; find items that now sell below cost; report new, dropped and unmatched lines; produce a file QuickBooks Online will import that changes only what you intend; and keep a backup of what was there before. The guide on price list updates in a spreadsheet or software goes through these steps one by one.
Ask of every tool: which of these does it do, and how would you know if it did one wrong?
What a chat assistant can do well
- Explain a confusing layout. Paste a small sample and ask what the columns mean, or how quantity breaks are laid out.
- Suggest formulas. Ask for a lookup that matches on SKU, or a percentage-change formula, then put the formula in your spreadsheet where you can see it.
- Draft a note to the supplier asking what the new unit of measure is, or whether a part number was replaced.
- Help you think about a rule, such as how to treat a price of "call" or a discontinued item.
These are uses where the output is text you read and judge. If it is wrong, you see it.
Where it gets risky
The risk is not that a chat assistant is useless. It is that its output looks confident whether or not it is right, and a price update has many places to be wrong without showing it.
- Long files. A big list can be cut off, summarised or only partly read, depending on the tool and the file. The reply may not say so. Count the lines in the answer against the source.
- The sums. A language model writes text that looks like a calculation. Unless the figures come from code or a formula you can inspect, treat each one as unproven. Percentages across hundreds of lines add up to many chances for a quiet slip.
- Matching. A model may pair a supplier part with an item that looks close but is not the same. A wrong guess here puts a cost on the wrong product. A safe process sends unclear lines back as questions instead of choosing.
- Missing lines. Dropped and new items are easy to lose. A model can list the ones it noticed without telling you about the ones it did not.
- Consistency. Run the same request twice and the wording, and sometimes the content, can differ. A repeatable update needs the same input to give the same output.
- The import file. QuickBooks Online expects particular columns. A column mapped to the wrong field, or a blank cell when the import overwrites existing values, can change fields you did not mean to touch.
- Citations. Unless you ask for it, you get a number without the row it came from, and even a quoted row needs checking against the source yourself.
- Data handling. Cost lists are sensitive. Know where the text goes and whether your supplier terms allow it.
Comparing the approaches
| What you care about | General AI chat assistant | Tool built for price lists | PriceListRadar |
|---|---|---|---|
| Quick questions about a layout | Good fit | Not what it is for | Not what it is for |
| Arithmetic you can inspect | Only if you make it use a formula or code | Depends on the tool | Code does every sum |
| Reading a large file in full | Check the line count yourself | Depends on the tool | Code ties the row count to the source |
| Unmatched lines | Depends on how you ask | Depends on the tool | Returned to you as questions |
| Repeatable result | Not guaranteed | Depends on the tool | Sums and matches follow fixed rules in code |
| QuickBooks import file | You build and test it | Depends on the tool | Checked rows only, Purchase Cost only |
| Setup | Open and paste | Depends on the tool | Upload two files |
| Cost | Depends on your plan | Depends on the tool | 12 credits per 100 lines |
The middle column says what to ask of any tool in the category, not what one product does. PriceListRadar's column is explained in the last section.
A way to use a chat assistant safely
If you want to use one on a price update, keep it to the parts where you can see its work.
- Do the structure in a spreadsheet: one flat table, SKUs stored as text.
- Ask the assistant for formulas rather than for results, and paste them into the sheet.
- Have the sheet calculate change and percentage, so every figure is traceable to a cell.
- Use the assistant for text jobs: explaining columns, drafting supplier questions.
- Count the lines in the source and in your table. They must agree.
- Test your import file on two rows before the full file.
That is slower than pasting a file and asking for the answer, and it is the version you can defend if a cost turns out wrong. The guide on updating item costs in QuickBooks Online walks through the whole update.
When a chat assistant is enough
It is a reasonable choice when:
- The update is small, a few dozen lines at most, and you will read every line anyway.
- You only want explanations or formulas, and you do the calculating in a spreadsheet.
- A mistake would be cheap and obvious.
When a dedicated tool makes more sense
A tool built for the job is the better choice when:
- Lists are long, arrive as PDFs or scans, or change layout between suppliers.
- You want sums done in code and unmatched lines returned as questions, not guessed.
- You need an import file and a backup every time, without building them.
- You would rather check a flagged change list than build the process yourself.
For the matching step in particular, the guide on matching supplier SKUs to your items shows why guessing is the wrong default.
How PriceListRadar does this
PriceListRadar is a tool built for supplier price lists and QuickBooks Online. It does use AI, so the difference is in how the work is divided.
- What you upload: the supplier's price list (Excel, CSV, Word, PDF or a scan) and your QuickBooks item list.
- Who does what: the model reads the layout and the rows. Code does every sum and every SKU match, checks the values against the source cells, and ties the row count to the source.
- Matching: exact SKU (also ignoring case, punctuation and leading zeros), then known aliases, then a look-alike match only when one item is a clear winner, which is still left for you to confirm. Anything else comes back to you as a question, not a guess.
- What you get: a change list with below-cost items first and new and dropped items marked, a QuickBooks import file with checked rows only that replaces Purchase Cost and never Sales Price, a backup of the affected items' current values, and a summary email.
- Checking: a second, stronger AI model reviews every result and lists what is left for you to decide. No person checks it, so you should still read the change list.
- Price: up to 100 price lines is 12 credits, and each further 100 lines or part adds 12. Packs start at 25 credits for $25, with no subscription and no expiry.
It does not push changes into QuickBooks for you and it does not advise what to charge. To try it on a real list, sign up.
Questions
- Is it safe to paste my item list into a chat assistant?
- Check the privacy terms of the tool and your supplier agreements first. Price lists and cost data are commercially sensitive, and some supplier terms limit sharing. If you are unsure, ask the supplier or use a tool whose data handling you have read.
- Can a chat assistant at least compare two columns for me?
- It can often help with a small table, and a spreadsheet formula does the same job more reliably. For anything that goes into your books, make the sums come from a formula or code you can inspect, not from text a model wrote.
- What should I ask a chat assistant to do instead?
- Use it for the language-heavy parts: explaining an odd layout, drafting a question to a supplier, suggesting formulas, or writing a script. Then run the numbers in a spreadsheet or a script you can re-run and check.
- Will the answer be the same if I run it twice?
- Not necessarily. Language models can word and sometimes calculate things differently from one run to the next. For a cost update you want a process that gives the same answer every time, so re-run and compare before trusting it.
Your next supplier list, checked row by row.
Sign in, upload the price list, download the change list and import file.