Convert price list PDF to Excel on Mac (2026 workflow)

The new price list arrived this morning: a 34-page PDF, attached to a one-line email from the supplier — “updated pricing effective August 1.” Somewhere in those 34 pages, some prices went up. Your job is to find out which ones, reprice your own catalog, and get the new costs into the POS or the quoting spreadsheet before the effective date. And the only format the supplier ships is PDF, because the price list is generated from their ERP straight to a print layout.

Everyone downstream of a supplier lives this: the distributor repricing 800 SKUs a quarter, the restaurant checking whether the produce vendor moved prices again, the contractor who quotes from three suppliers’ lists and needs them in one sheet to compare. The data is a table — it was a table in the supplier’s system — but what you received is a picture of a table, spread across pages, interrupted by category headers and footnotes.

This guide is the Mac workflow: convert a price list PDF to Excel on Mac — read on-device, never uploaded — with SKU, description, and price in their own columns, category headers preserved, and multi-page tables stitched back into one sheet.

Why price lists break table extractors

A price list looks like the easiest possible extraction — it’s just a table. Four structural habits make it the document that quietly defeats generic converters:

1. The table continues across pages. Thirty pages of rows with the header repeated (or worse, not repeated) at each page top. Tools that extract per page hand you thirty fragments with thirty header rows to delete, and page-boundary rows that split mid-description.
2. Category headers live inside the table. ”— FASTENERS —” as a full-width row, then forty SKUs, then ”— ADHESIVES —”. Grid-based extractors either drop these rows or leave them as junk rows in your data. But the category is information — you want it as a column value on each row, not as debris between them.
3. Quantity-break tiers. 1–9: $4.20 / 10–49: $3.80 / 50+: $3.15, sometimes as three columns, sometimes crammed into one cell, sometimes as indented sub-rows. There’s a right shape for this data (one row per SKU per tier) and no grid extractor produces it.
4. Footnote markers on the numbers. $12.40* where the asterisk means “while stocks last.” Left in the cell, that string breaks every numeric operation downstream; the marker needs to move to its own column or go.

Layout-based tools fail on these because the fixes require reading the table, not just seeing it. This is exactly the gap a prompt-driven extractor closes.

Method 1: ignitai on Mac (the read-on-device way)

ignitai extracts by description, not by grid coordinates. The flow for a supplier list:

1. Drag the PDF in — or File-picker it, or right-click → Open With from Finder. One file is one job; a scanned or photographed price list works the same way as a born-digital one (the scanned-PDF walkthrough covers the scan-quality details).

2. Describe the output shape in plain English. A prompt is required — the Convert button stays disabled without one — and this is where every structural problem above gets solved in a sentence each:

   “One row per item: category (from the section headers), sku, description, unit, unit_price, currency. The table continues across all pages — don’t restart at page breaks. For quantity-break pricing, one row per tier with a min_qty column. Drop footnote markers from prices.”

   Save it as a preset; it syncs to your other devices via iCloud, and next quarter’s list is one click.

3. Pick Excel, hit Convert. The PDF is read on your Mac — never uploaded — and only the recognized text goes to ignitai’s private hosted pipeline to build the sheet. On macOS 26 Apple’s native on-device table recognition makes dense catalog pages extract noticeably sharper; the same flow works back to macOS 14.4. A typical list is usually ready in under a minute.

4. Open the result in Excel or Numbers. One worksheet, one row per item, every cell clean text — bare numbers in unit_price, no currency symbols or footnote junk — so a single formatting pass (currency format on the price column) types the sheet. The in-app preview is read-only; edits happen in the spreadsheet.

Comparing several suppliers? Run their lists as one batch — select all the PDFs and drag them in together with the same prompt, adding: “include a supplier column using the company name printed on the list.” One consolidated sheet, one row per item per supplier, ready to pivot. Two caveats that keep the batch honest: filenames never leave your Mac, so there’s no filename column — the supplier name has to come from the document’s own pages, which is why the prompt asks for it — and if one supplier sent a JPEG instead of a PDF, it needs its own run: a drop that mixes PDFs and images imports only the PDFs, and image files convert as a separate batch with the same prompt.

Two tables means two runs. The output is always one table on one worksheet. If the last pages of the list are a different structure — a freight table, a returns schedule — that’s a second run with a second prompt, not extra sheets in the same workbook.

Method 2: Excel for Mac’s Get Data (no PDF connector)

Excel for Mac ships Power Query under Data → Get Data, but the Mac’s connector list — Text/CSV, XLSX, XML, JSON, SharePoint, SQL Server, OData — has no From PDF option; that connector is Excel-for-Windows-only. So Excel on the Mac can’t ingest the price list directly. Even on Windows, where From PDF exists, it detects one generic table per page: thirty fragments for a thirty-page list, category headers as junk rows, tier pricing left in whatever shape the layout crammed it into. The stitching and cleaning that follow are the actual work, and Power Query makes you do them by hand.

Method 3: Preview + Numbers (the two-page fallback)

For a short, clean, born-digital list: open the PDF in Preview, select the table, copy, paste into Numbers, and repair the columns by hand. It works when the list is a page or two with single-line descriptions. It stops working exactly where price lists get real — multi-line descriptions paste as extra rows, page boundaries shear the table, and tier pricing lands as one mashed string. Numbers also has no Text to Columns command, so every repair is manual. Fine for a lunch-menu-sized list; not for a catalog.

Method 4: web converters (the confidentiality line)

For a public price list — the one on the supplier’s website — a web PDF-to-Excel tool poses no real privacy question, and if it’s short and gridded, one may do the job. Two reasons this path still underdelivers: generic converters have the same per-page table blindness as Power Query (fragments, junk rows, mangled tiers), and free tiers gate at a few files or a few pages, which a 34-page catalog exceeds immediately.

The sharper line is confidentiality. Negotiated price lists — your cost basis, your volume discounts, the terms your supplier gives you — are routinely under NDA, and your margins are reverse-engineerable from them. That’s not a document to upload to a converter you don’t control. The on-device read exists for exactly this class of file: the PDF stays on your Mac, and only recognized text touches ignitai’s private pipeline.

On iPhone and iPad

The quarterly reprice is a Mac job, but price lists don’t always arrive as PDFs at a desk:

• iPhone — the rep hands you a printed sheet at a trade counter: capture it with the in-app camera scan, apply the saved preset, and the rows are in a sheet before you’re back in the van. A JPEG price list in an email goes in through the share sheet the same way — the picture-to-Excel iPad guide covers the image-input details.
• iPad — reviewing a new list on the couch: save the attachment to Files, select it from the picker or share sheet (there’s no external drag-and-drop into the app on iPad), convert with the synced preset, and iCloud puts the XLSX on your Mac for the comparison pass.

The comparison pass: catching the increases

The sheet isn’t the deliverable — the diff is. With this quarter’s extraction next to last quarter’s:

1. Put both on separate sheets of one workbook, keyed by sku.
2. =XLOOKUP(A2, old!A:A, old!E:E) pulls each SKU’s previous price alongside the new one; a change_pct column and a filter for anything above zero is your increase report.
3. Filter for #N/A in the lookup both directions: new SKUs the supplier added, and discontinued SKUs still living in your POS.

This pass is the reason the extraction needs to be clean — one row per SKU, bare numeric prices, consistent SKU strings. Every footnote asterisk or split row you didn’t remove upstream becomes a false positive here. If the destination is a shared tracker rather than a local workbook, the same XLSX imports straight into Google Sheets — the PDF-to-Google-Sheets Mac guide covers that handoff — and Numbers users can open it directly, per the PDF-to-Numbers guide.

Bottom line

For a supplier price list PDF that needs to become a working Excel sheet on a Mac: drag it into ignitai, write the one-paragraph prompt (columns, continue-across-pages, one-row-per-tier, drop the footnotes), pick Excel, Convert, then run the XLOOKUP diff against last quarter. Use Preview-and-paste for a one-page menu; accept a web tool only for public lists you’d hand a stranger anyway. For the negotiated list that defines your margins, the on-device read is the point: the PDF never leaves your Mac.

Get ignitai on the App Store — sign in with Apple, first conversion free, then $19.99/mo after a 3-day trial; one subscription covers iPhone, iPad, Mac, and Vision Pro.

FAQ

How do I convert a multi-page price list PDF to Excel on a Mac?

Drag the PDF into ignitai, describe the columns in one sentence — SKU, description, unit, price — and tell it the table continues across pages. Pick Excel and hit Convert. The whole list comes back as one sheet, one row per item, with the category section headers carried into their own column.

How do I handle quantity-break (tiered) pricing?

Ask for one row per SKU per tier: SKU, description, minimum quantity, and unit price at that tier. A three-tier item becomes three rows, which is the shape VLOOKUP, pivot tables, and most POS imports actually want — flattening tiers into extra columns is what breaks imports.

Does the price list get uploaded?

No — the PDF is read on your Mac and never uploaded. Only the text recognized on-device goes to ignitai’s private hosted pipeline to build the sheet. For a public catalog that’s a convenience; for a negotiated price list under NDA, it’s the difference that matters.