Straight into the service manual page
WrenchQuarry
More

Odoo vendor pricelists: 3 steps before ordering

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

To update vendor pricelists in Odoo, export the list, correct it against current vendor prices, and import the corrected file.

Key takeaways

  • Check the date behind each pricelist before you trust it, since an old sheet may be correct or simply forgotten.
  • Work from the vendor's source document, not memory, when correcting each price line in your export.
  • Read the vendor's unit against your buying unit, because a box price entered as a piece price can cause an ordering mistake.
  • Test a draft request for quotation before confirming, and review the price it shows before placing an order.

If the pricelist is out of date, an order can carry an old price, and nobody notices until the invoice arrives or a crew asks why a job ran over budget. For dispatchers and office leads, a stale pricelist rarely causes one big error. It causes a slow drift, a few lines at a time, across every order placed that month.

Updating pricelists is unglamorous work. It means pulling a list, checking it against what vendors have actually quoted, and loading the result back in, usually on a day when the phone is ringing. It is also the kind of task that slides when nobody owns it. The good news is that the Odoo 18.0 documentation describes a simple loop you can follow every time: export the pricelist, correct the file, and import it back. This post walks through those three steps in plain language, along with the habits that keep the loop from breaking down.

Nothing in this routine replaces a vendor's written quote or your own buying rules. The goal is narrower: get the prices stored in Odoo to match the prices your vendors have given you, before anyone places an order that depends on them.

Step 1: Export the pricelists you need

Start by pulling the pricelists out of Odoo. You want to work from what the system holds right now, not from memory or from an old spreadsheet saved on someone's desktop. The Import vendor pricelist page in the Odoo 18.0 documentation gives the path for this: "To export a pricelist, go to Purchase app ‣ Configuration ‣ Vendor Pricelists." From that list, the same page says to "tick the checkbox(es) for the desired vendor pricelists."

Be deliberate about what you select. Export only the vendors and products you expect to order during the next cycle. A smaller file is easier to check line by line, and it keeps you from changing prices for a supplier nobody will call this month. If one vendor supplies most of your fittings, fasteners, or filters, put that pricelist first. A stale price on a high-volume item costs more than a stale price on something you order once a year.

Before you open the file, write down two things: the date of the export and the reason you are doing it. A short line in a shared log is enough, such as the vendor name, the date, and who will check the result. This sounds like paperwork, and it is, but it is what lets you answer "which prices were current on the fifteenth?" when a crew disputes a part cost weeks later. For the related job record, see the job cost sheet guide.

Keep an untouched copy of the export as well. Save it under a name that says it is the original, and do all your edits in a second copy. If an import goes wrong, you need something to compare against. Without the original, you are guessing what the sheet looked like before you changed it, and that guess is exactly the kind of error this routine is meant to remove.

A pricelist that has not changed in a long time may still be correct, or it may simply be forgotten. Neither possibility is safe to assume. Compare the date on the vendor's latest sheet or email with what the pricelist in Odoo reflects, and note any vendor where the two do not agree.

While you scan the export, look for gaps, not just wrong numbers. The Odoo documentation uses this example: "Large Desk (Reference: E-COM09) has no records in the vendor pricelist." A product with no line for a vendor is the easiest one to order without anyone confirming what it should cost. Mark every product your team orders that has no line for the vendor you usually use. Those are the rows to fill first.

Give the export one owner. Whoever pulls the file should either check it or sign off on the changes, because the person who edits a price is the one most likely to miss it. If your office has two people who could do this, agree in advance which one does it this cycle, so two people do not both export and both edit the same vendor.

Step 2: Correct the file from current vendor prices

This is the step where most of the work happens, and it is where mistakes happen too. The Odoo documentation puts the instruction briefly: "Modify the exported file, as needed, then import it back into the Odoo database." The "as needed" part is yours to judge, so decide before you start what counts as needed. For most offices, that means any line where the vendor's current price differs from what Odoo holds, any missing line, and any vendor price you have not yet confirmed.

Pull the most recent price sheet, quote, or written confirmation from each vendor, and compare it line by line with your export. Do not copy a price from a similar part on another vendor's sheet because the descriptions look alike. Two items with nearly identical names can carry very different numbers, and a copy-down mistake can carry one price through a dozen rows before anyone sees it.

Match rows by the internal reference wherever you can. The documentation's example pairs a product name with a reference code, E-COM09, and the reference is the more reliable key because names get typed in different ways by different people. If a reference is missing from your file, stop and look it up before you enter a price. A row with the wrong product behind it is harder to find later than a row you left blank for a day.

The documentation's examples show what a complete line looks like. One reads: "Add pricelist for Storage Box: the vendor, Ready Mat intends to sell the product for $14." Another reads: "Add pricelist for Large Desk: vendor is Azure Interior, price is $1399." Each line states the product, the vendor, and the price. Those three facts are what you check on every row you touch. The figures are sample entries, so do not carry them into your own file. Use the numbers your vendors have actually given you.

Check the unit before the price. A vendor may quote by the box, the case, or the each, and your team may buy in a different unit. Read the unit on the vendor's sheet against the unit your team buys in. A box price entered as a piece price looks reasonable at a glance, and the mismatch may only show up when the invoice arrives. Write the unit in your log next to any line where the two differ. For customer estimates, see the related guide to equipment estimate line items.

Check the file format before you import it. The documentation states the requirement this way: "To import vendor pricelists, ensure the XLSX or CSV file is accurately completed." Treat "accurately completed" as a checklist you run yourself. Look for blank price cells on rows you meant to fill. Look for prices stored as text rather than numbers, which often happens when a figure is pasted from an email or a PDF. Look for currency symbols, extra spaces, or thousands separators that a spreadsheet may have added without telling you.

Confirm that the vendor name in each row matches the vendor record you use in Odoo. A name spelled slightly differently may not line up with that record, and the mismatch is hard to spot in a long list. If you see two spellings for the same supplier in your file, pick the one in Odoo and use it everywhere.

When a vendor has not sent a new price, do not guess. Keep the existing price, and note in your log that it is unconfirmed, so the buyer knows which numbers have been checked and which have not. An estimate typed in to fill a gap can look like a confirmed price for months. An honest blank, or an explicit unconfirmed note, is easier to act on.

Pay closer attention to the lines that matter most to a dispatcher. Parts that go on jobs every week, parts that come from a single vendor, and parts that are hard to replace on short notice should be checked twice. A mistake on an ordinary fastener costs a few minutes. A mistake on the one part that stops a crew costs a day.

For large changes, ask a second person to check a sample of rows before the import. The sample should cover the whole file, not just the first screen. Two sets of eyes catch errors that one person, looking at the same familiar sheet for an hour, will read straight past.

Step 3: Import the file and check the results

Import your corrected file into Odoo. Allow time to check the result afterward. An import can finish without you noticing a problem and still leave the wrong numbers in place. Plan to look at the results before any order relies on them.

Start with the rows you changed. Open the vendor's pricelist in Odoo and compare each changed line with your corrected file. Confirm the product, the vendor, and the price, the same three things you checked in step two. If you changed many rows, sample across the whole file rather than reading only the top, and include a few rows from the middle and the bottom.

Then check one or two rows you did not change. This catches the case where the import moved values or touched lines it should not have. If an untouched price now looks different from the original export, stop. Do not place orders from that vendor until you have compared the import against your original copy and understand the difference.

Next, go back to the gaps. Open the products you flagged in step one as having no line for the vendor. Each one should now have a line with a price, or be recorded in your log as still unconfirmed. An open gap should never be ordered quietly, because the buyer will have no way of knowing whether the number on the order was ever checked.

Then test the result where it matters: at ordering. Create a draft request for quotation for a product from the vendor, and review the price shown on its line before ordering. A pricelist that looks right on a configuration screen only helps if its price comes through to the order. If the number on the draft differs, find out why before you confirm anything. Do not override the price by hand without a note in your log explaining who changed it and why.

If a check fails, resist the urge to keep editing the live pricelist until it looks right. Go back to your corrected file, make the change there, and import again. The file stays the record of what you intended, and the next review becomes much easier. Keep the original export, the corrected file, and the log together in one folder, labeled with the vendor's name and the date.

Remember that the check is not finished when the import completes. Prices can change again after you import, so the log should show when the pricelist was last checked against the vendor's own document, not only when the import ran.

Finish by logging the outcome: the import date, the file name, the number of rows you changed, the rows still unconfirmed, and who checked the result. A short entry like that turns a one-time cleanup into a record that the next person can pick up without asking you what happened.

Illustrative example: a price change

Suppose a written vendor quote changes an item's price from $30 to $60 for the same unit. Update that line in your exported file, import it, and review the result. If a draft request for quotation still shows $30, pause before ordering and investigate the difference. These prices are illustrative.

Keeping the routine on schedule

The routine only helps if it runs again. Pick a schedule that matches how often your vendors change prices, and put the next pass on a calendar with a named owner beside it. A single person does not have to do every step, but one person should be responsible for each vendor, so nothing sits unfinished between two desks.

Make the routine visible. A shared calendar entry, a short note at the top of the log, or a reminder in the team's regular meeting is enough. The aim is that anyone in the office can see when the pricelists were last checked and what is still open, without having to ask someone who may be out that day.

Give dispatchers a simple way to report problems. When a dispatcher orders a part and the price looks wrong, they should be able to tell the office in one line: the product, the vendor, and the price they saw. That turns a surprise on a job invoice into a fix in the next pass, instead of a dispute weeks later.

Keep the list of vendors short at first. It is tempting to clean up every pricelist at once, and that usually stalls. Start with the vendors behind most of your orders, get their lines right, and then add the rest. A routine that finishes is worth more than a plan that stalls halfway through a long supplier list.

Review the process itself every so often. If the same product keeps showing a gap, the item probably belongs on the vendor's pricelist permanently rather than being handled by hand each cycle. If the same vendor keeps sending prices in a different layout, ask for the format you use, or build a simple mapping that turns their sheet into your columns. Small changes like these save more time than any single cleanup.

Today, choose a vendor you expect to order from next and compare its latest written price sheet with an untouched export.

Questions before ordering

Should I update every vendor at once?

Start with the vendors behind most of your orders. Expand the routine after that smaller pass is finished.

Can I order when a price is still unconfirmed?

Confirm the price with the vendor before relying on it. Keep the unresolved line visible in your log so the buyer can follow up.

Sources

More field guides