Supplier Price List Stuck in a PDF? Get It Into Excel Without Losing the Details.
By Zechariah Myrick · October 24, 2026 · 7 min read
Start by asking your supplier for an Excel or CSV file. If only a PDF is available, extract a small sample into a separate review table before updating your working catalog. Keep item codes, pack quantities, units, prices, and source pages together. A neat-looking spreadsheet can still contain shifted rows or missing digits. The useful result is a checked import your office can repeat—not simply a file that opens in Excel.
For a Naples or Bonita Springs business, this often begins with a routine office task: a supplier sends a revised catalog, and someone spends the afternoon copying products into the spreadsheet the team actually uses. The challenge is preserving what each price means while keeping the existing approved data available.
Ask for the source table before buying a converter
A supplier may already have a downloadable spreadsheet, a product export, or a customer-portal report. Ask whether it includes stable item numbers, package quantities, currency, and an effective date. A spreadsheet still needs checking, but it can avoid reconstructing rows from a page designed mainly for reading.
Keep the supplied file unchanged and record which revision you received. Do not merge two catalogs merely because their file names look similar. If one contains your account-specific prices, treat it as business material and use only tools your business has approved for that information.
Try your existing tools on one representative section
Microsoft’s current Power Query PDF connector guide, updated October 9, 2026, documents selecting a PDF, choosing detected content in Navigator, and transforming it before loading. Availability depends on the product and host. Check your actual Excel setup rather than assuming every desktop, web, or Mac version exposes the same options.
Adobe’s Acrobat PDF-to-Excel instructions, updated October 22, 2026, describe XLSX export and settings for worksheets, numeric separators, and text recognition. These are existing options worth testing before commissioning custom software. Neither a successful export nor a tidy layout establishes that every product row is right.
Choose a sample with the awkward parts: a description running over two lines, a table crossing a page break, a repeated heading, and a product sold by the case. If the PDF is a scan, text recognition may be necessary. Blurry or incomplete source material needs review; an AI guess cannot resolve a missing digit reliably.
Decide what a usable row must contain
Before importing the whole catalog, define the columns your office needs. A practical starting table includes supplier, source revision, source page, supplier item code, description, pack quantity, unit of measure, listed price, currency, and review status. Leave unknown values visibly unresolved. Do not silently turn an empty price into zero.
Keep codes such as 00127 as text from the import step onward. A code identifies an item; it is not a quantity to calculate. Microsoft’s Power Query data-type guidance explains column types and automatic type detection. Review the conversion steps before loading: a later display format cannot reliably recover an identifier already altered during import.
The source reference matters when someone questions a row. An office manager should be able to open the right PDF page, see the product and its nearby notes, and understand what was imported. Keeping that connection is more useful than an AI-generated assurance that the extraction was accurate.
A fictional Bonita Springs catalog change
Imagine an office manager at a Bonita Springs property-care business updating a supply list. This is a fictional example, not an AI Dream Builders client or a local price guide. The old catalog lists item 00127 as a case of 12 cloths for $24. The revised catalog lists the same item code as a case of 10 for $22.
An import that compares only the case price reports a lower price. A checked comparison also flags the changed pack quantity. In this invented example, the implied per-cloth amount changes from $2 to $2.20. Those figures are simple arithmetic on fictional inputs, not a purchasing recommendation. The office still needs to confirm the supplier’s description, units, and applicable terms.
Now suppose the product description wraps onto the next line and the converter attaches the next item’s price to it. The spreadsheet may still look orderly. The correct response is to hold that row for review against the source, rather than fill the gap with whichever price looks plausible.
Use a review table between the PDF and the approved catalog
Load extracted data into a staging sheet—a place to inspect proposed changes. Keep the current catalog separate. Compare rows using supplier plus a stable item code, and flag duplicates, missing codes, changed packs, unexpected units, and new or removed products. A missing row is a question to investigate, not automatic permission to delete an item your business still uses.
Microsoft’s PDF connector documentation specifically discusses misidentified multiline rows and possible cleanup using transformation steps. For your office, the important decision is which situations can be corrected by a clear rule and which must remain exceptions. A rule that works on one tidy page may join the wrong lines when the supplier changes its layout.
Give someone responsibility for approving the reviewed version. Keep a copy of the previous approved catalog and a record of which source revision produced the replacement. If a downstream estimate or purchasing tool uses these prices, agree when the approved update takes effect. Extraction should not automatically send quotes or place orders.
When a repeatable import is worth building
For an occasional short PDF, manual entry with a second check may be proportionate. A built-in converter may be enough when the columns are consistent and the review is easy. A configured Power Query transformation can be useful when similar files arrive repeatedly. Test it again when the supplier changes the layout.
Custom work becomes worth discussing when several suppliers use different formats, your team repeatedly cleans the same fields, or the reviewed rows must feed another system. A useful implementation can preserve source references, show exceptions in one place, compare revisions, and export only approved rows. AI may help interpret descriptions, but fixed rules and human review should control identifiers, units, and acceptance.
Test with several representative revisions, including a difficult page, before expanding the workflow. Count wrong or missing rows, time spent correcting them, unresolved exceptions, and whether a reviewer can trace a value back to its source. Include the checking time when comparing methods. Fewer keystrokes alone do not prove the setup is helping.
Get the catalog off the retyping pile
AI Dream Builders is an independent Naples studio offering automation, AI integration, and custom software for businesses in Naples and Bonita Springs. Zechariah Myrick can assess the files and the spreadsheet you need, then scope an existing-tool setup or custom connection. A useful first paid deliverable can be a reviewed sample import, a visible exception list, and an agreed output format—not an untested promise to convert every supplier automatically.
[Call (239) 544-6990](tel:+12395446990) and say: ‘We keep retyping supplier PDF price lists into Excel, and I want a repeatable import.’ Start with the type of catalog, how often it changes, and which spreadsheet or system receives the rows. The initial conversation is free. Scope, price, ownership, ongoing costs, and support are agreed before paid work begins. You can also describe the import problem here. Leave passwords, account-specific pricing files, and private business documents out of the form.
If your catalog is already approved but job notes are slowing down estimates, the separate estimate-drafting guide covers that later step.