Price list updates: spreadsheet or software?

Published 17 October 2026. Updated 17 October 2026.

The usual starting point is a spreadsheet. A supplier sends a new price list, you open it next to your item export, and you work down the lines. For a small catalogue and a tidy file, that is a perfectly good way to work. This guide is about the point where it stops being good, how to tell whether you have reached it, and what to do well in either case.

It compares two approaches in general terms: doing the update yourself in a spreadsheet such as Excel or Google Sheets, and using software that is built for the one job of turning a supplier price list into checked cost changes. It is not a verdict that one always wins.

What the job actually takes

Whatever tool you use, a supplier price update has the same steps.

1. Get the supplier's prices into one flat table, one line per item.
2. Match each supplier line to one of your items.
3. Compare the new cost with the cost you have now, in currency and as a percentage.
4. Compare the new cost with your sales price and find items that now sell below cost.
5. Decide what to do with new items, dropped items and lines that do not match.
6. Put the checked costs into QuickBooks Online without touching anything else.
7. Keep a backup, because the import cannot be undone with a button.

The tool changes how much of this you do by hand. It does not remove any of the steps.

Where a spreadsheet works well

A spreadsheet is flexible, familiar and already paid for. It is a good fit when:

• You deal with a few suppliers and their lists change once or twice a year.
• The files arrive as clean Excel or CSV with a consistent layout.
• Your item names are close to the supplier's part numbers, so matching is a simple lookup.
• One person owns the update and knows which columns to trust.
• A late or missed change would be noticed quickly and costs little.

In that situation, a saved workbook with a lookup column, a change column and a conditional format for negative margin does the job. If that describes you, keep it.

Where a spreadsheet starts to break down

The failures are rarely dramatic. They are small and quiet, which is why they survive.

• Retyping. Costs copied from a PDF or a Word table pick up transposed digits and dropped decimals. Nobody sees them until a margin report looks odd.
• Lost lines. A filter left on, a hidden row or a paste that stops early removes items without any warning. Counting lines in the source and in your sheet is the only defence, and it is easy to skip.
• Damaged SKUs. Spreadsheets can drop leading zeros, turn long numbers into scientific notation and change values like 3-4 into dates. The match then fails or, worse, lands on the wrong item.
• Layout work every time. Quantity breaks, merged cells, repeated headers and "call" notes in the price column need a different clean-up for each supplier.
• Version confusion. Which file was last quarter's? Which copy has the fixes? Three similar names in a shared folder is how an old list gets imported.
• Formulas that rot. The sheet works because of one person's lookups. When that person is away or leaves, nobody trusts a change they did not make.
• Nobody checks the second time. The person who built the sheet is also the one reading its output, so a wrong formula is read by the person least likely to spot it.

None of these is a reason to avoid spreadsheets. They are the reasons to build a few safeguards into one, which the checklist below covers.

Where software built for this job helps

Software for supplier price lists exists to take over the steps that go wrong by hand: reading the layout, matching lines, doing the sums and preparing the file for your accounting system. What it takes over varies from product to product, so judge any tool on the specifics.

Questions worth asking of any tool in this category:

• Which file types does it read, including PDFs and scans, and how does it show you what it read?
• Does it do the arithmetic in code, or leave it to a model's text output?
• What does it do with lines it cannot match: guess or ask?
• Does it flag items that now sell below cost, and put them first?
• Does the output go straight into the format your accounting system imports?
• Is there a backup of current values before anything changes?
• What does it cost per update, and what happens if you only need it twice a year?

Comparing the approaches

The middle column says "depends on the tool" on purpose. Judge a specific product on its own claims and its own samples. PriceListRadar's column is explained near the end of this guide.

When a spreadsheet is enough

Stay with a spreadsheet if most of these are true:

• You update fewer than a handful of lists a year.
• Each list is a clean Excel or CSV file with a few hundred lines at most.
• You can finish an update in an afternoon and trust the result.
• Your own check has caught nothing wrong for a long time, and a missed change would not hurt much.

Spending money on a problem you do not have is its own mistake.

When software makes more sense

Look at software when several of these are true:

• You have many suppliers, and the layouts keep changing or arrive as PDFs and scans.
• An update takes days, or gets postponed because it takes days.
• You have sold items below cost because a change went unnoticed.
• The person who built the sheet is the only one who can run it.
• You want a backup and a clear list of unmatched lines every time, without relying on discipline.

A checklist that works with either approach

• Keep the supplier's original file untouched, and work on a copy.
• Export your current item list before you change anything, and store it with the date.
• Count the item lines in the source and in your working table. The numbers must agree.
• Store SKUs as text so leading zeros and dashes survive.
• Calculate change in currency and as a percentage with formulas, never by eye.
• Check the unit. A jump of several hundred percent can be a change of unit, such as from each to a box, rather than a real increase. The supplier price increase checklist goes through this and similar traps.
• Treat lines with no match as questions. Do not let a guess reach an import. The guide on matching supplier SKUs to your items sets out a safe order of rules.
• Put only checked rows in the import, and change purchase cost only. The guide on updating item costs in QuickBooks Online covers the import itself.
• Import two rows first and open them to confirm only the cost moved.
• Read the biggest changes against the source before the full import.

How PriceListRadar does this

PriceListRadar covers the middle of the job, from the supplier's file to a QuickBooks Online import file. It does not connect to QuickBooks directly; you import the file yourself.

• What you upload: the supplier's price list (Excel, CSV, Word, PDF or a scan) and your QuickBooks item list.
• How it works: it reads the layout and the rows, matches each line to your items by 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 it still leaves for you to confirm. Code does every sum and every match. Lines it cannot match come back to you as questions, never guesses.
• What you get: a change list with below-cost items first, new and dropped items marked, a QuickBooks import file containing 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 the result, so the final read of the change list is yours.
• Price: an update of up to 100 price lines is 12 credits, and each further 100 lines or part adds 12. Packs start at 25 credits for $25, credits do not expire and there is no subscription.

It does not tell you what to charge and it is not pricing advice. If a spreadsheet already does this job for you, you may not need it. If you are ready to try it on a real list, sign up.

Questions

How many supplier lists make a spreadsheet too slow?

There is no fixed number. The pressure comes from the combination of lists per year, lines per list and how different the layouts are. Two clean files a year is a spreadsheet job. Dozens of suppliers in mixed layouts is where the time goes.

Can I build the matching and flagging into my own spreadsheet?

Yes, with lookups and a few formulas. The hard part is keeping it working: each supplier layout needs its own clean-up, and the sheet only stays reliable if its builder stays around to fix it.

Does software mean I stop checking the result?

No. Whichever way you work, read the top of the change list against the source and test a few rows in QuickBooks before a full import. Software shortens the typing and the comparing, not the responsibility for your costs.

Is it worth changing for a handful of updates a year?

Only if the hours or the missed changes cost more than the alternative. If each update takes you a few hours and goes smoothly, a spreadsheet may be all you need. If one missed increase has already cost you margin, the case changes.