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.