Convert bill of lading PDF to Excel on Mac (2026 guide)

The freight bills came in with the morning email: nine signed bills of lading from last week’s shipments — three from the LTL carrier’s portal, four scanned at the dock and photographed, two faxed back by a consignee who still faxes. The shipment log needs the same thing from every one of them: BOL number, ship date, shipper, consignee, carrier, PRO number, pieces, weight, class, charges. The PDFs have all of it, scattered across labeled boxes in nine slightly different form layouts. So the ops coordinator does what ops coordinators have always done: retypes each one into the spreadsheet, cell by cell, and hopes no weight got fat-fingered on the way to the freight-invoice audit.

Everyone who touches freight paperwork lives this. The shipping manager keeping a lane-cost log. The broker reconciling carrier invoices against what was actually tendered. The small manufacturer whose ERP wants shipment data its EDI feed doesn’t carry. The warehouse office tracking OS&D claims against signed delivery copies. A bill of lading is a legal document designed for a clipboard, not a database — and the data on it dies in a filing cabinet unless someone retypes it.

This guide is the Mac workflow: convert bill of lading PDFs to Excel on Mac — read on-device, never uploaded — with BOL number, carrier, consignee, weight, and charges in their own columns, one row per shipment, ready to audit.

Why bills of lading defeat table extractors

A BOL isn’t a table at all — it’s a form with a small table embedded in the middle, and that shape breaks every grid-based tool:

1. The data lives in labeled boxes, not rows. Shipper block top-left, consignee top-right, carrier and PRO number in the middle band, charge terms in a corner. A grid extractor looks for rows and columns; a form gives it a mosaic. What comes back — when anything comes back — is scattered fragments with the labels and values decoupled.
2. Every carrier prints a different form. The standard short form, the VICS layout, each LTL carrier’s branded variant, the freight broker’s own template — same fields, different boxes, different order. Template-based extractors need a mapping per layout; a week of freight sees them all.
3. The commodity grid sits mid-form. Handling units, package type, HM flag, description, NMFC code, class, weight — a genuine table wedged between the address blocks and the signature band. Grid tools that find it hand it to you amputated from the BOL number that gives it meaning.
4. The copies that matter are scans. The signed delivery copy — the one with legal weight, the one the invoice audit needs — comes back from the dock as a photocopy, a fax, or a phone photo. A layout parser gets nothing from a scan; it needs to be read, not parsed.

The fixes require understanding the document — knowing that the number next to “PRO #” belongs in the PRO column no matter which corner it printed in. That’s what a prompt-driven extractor does that a grid tool can’t.

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

ignitai extracts by description, not by layout template, so one prompt covers whatever form the carrier prints:

1. Drag the PDFs in — or use the file picker, or right-click → Open With from Finder. A scanned or faxed copy 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. Start from the Forms starter template or write your own, one clause per habit above:

   “One row per bill of lading: bol_number, ship_date, shipper, consignee, origin_city, destination_city, carrier, pro_number, handling_units, total_weight_lbs, freight_class, charge_terms, freight_charges. Take each value from its labeled box; if a field isn’t printed, leave it empty. Skip the terms-and-conditions text and the signature band. ISO dates, bare amounts.”

   Save it as a preset — it syncs to your other devices via iCloud — and next week’s stack is one click.

3. Pick Excel, hit Convert. Each 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 commodity grids extract noticeably sharper; the same flow works back to macOS 14.4. A typical batch is usually ready in under a minute.

4. Open the result in Excel or Numbers. One worksheet, one row per BOL, every cell clean text — ISO dates, bare weights and amounts — so one formatting pass types the columns for the log. The in-app preview is read-only (rename only); edits happen in the spreadsheet.

A week of freight is one batch. Select all nine PDFs in Finder and drag them in together with the same prompt — they consolidate into one worksheet, one row per BOL, which is the shipment log. The prompt’s bol_number column does the work of keeping shipments apart: filenames never leave your Mac, so there’s no filename column, and the identity has to come from each document itself — and on a BOL, the number is the most prominent field on the page. If two of the nine are phone photos rather than PDFs, they run as their own batch: a drop mixing PDFs and images imports only the PDFs.

One table per run — you pick the grain. “One row per BOL” builds the shipment log. Want the commodity lines instead — one row per NMFC item, with the BOL number repeated on each? That’s a second run with a second prompt, not extra sheets in the same workbook. Two shapes, two runs.

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

Excel for Mac ships Power Query under Data → Get Data, but the Mac connector list — Text/CSV, XLSX, XML, JSON, SharePoint, SQL Server, OData — has no From PDF option; that connector is Excel-for-Windows-only. And a BOL is Power Query’s worst case even on Windows: From PDF detects visual grids, so the address boxes arrive as disconnected two-cell mini-tables, the commodity grid comes back orphaned from its BOL number, and the signature band contributes noise. The repair work after Power Query is the data entry you were trying to eliminate — and it gets nothing at all from the faxed copies.

Method 3: Preview + Numbers (the one-shipment fallback)

For a single born-digital BOL: open it in Preview, select text box by box, paste into Numbers, repair by hand. A form doesn’t select as a table — it selects as label-value soup in print order — so every field is its own copy-paste. Workable for one shipment a week; at nine it’s slower than retyping, and against a fax it’s nothing at all.

Method 4: web converters (the customer-data line)

Generic web PDF-to-Excel tools share Power Query’s grid blindness — a form comes back as fragments, if the free tier’s page gate lets the batch through at all. But the disqualifying issue is the content. A bill of lading names your customers and their addresses, what they bought, in what volume, on what charge terms — a competitor’s shopping list, one upload away. Sending that to a free converter you don’t control is a data-handling decision about your customer relationships. The on-device read exists for exactly this class of document: the PDF stays on your Mac, and only recognized text touches ignitai’s private pipeline.

On iPhone and iPad

Freight paperwork is born at the dock, not at the desk:

• iPhone — the driver hands over the signed copy: capture it with the in-app camera scan before the truck leaves, apply the saved preset, and the shipment is in the log while the trailer’s still in the yard. A Live Activity shows conversion progress from the lock screen. A BOL that arrives as a photo in a text goes in through the share sheet the same way.
• iPad — the warehouse-office iPad collects the day’s PDFs in Files: multi-select them 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 the Mac where the log lives.

One subscription covers iPhone, iPad, Mac, and Vision Pro, so the preset travels with you.

The audit pass: what the shipment log unlocks

The sheet isn’t the deliverable — the checks are:

1. Audit the freight invoices. The carrier’s invoice says what they’re charging; the BOL says what was tendered. Match on pro_number, compare weight, class, and charges, and reweigh-and-reclass surprises surface in a filter instead of slipping through AP. The invoice-to-Excel guide covers extracting the other side of that match.
2. Tie shipments to orders. A BOL without a PO behind it is a question worth asking. The purchase-order workflow builds the order-side sheet; matching the two closes the loop from order to delivery.
3. See the lanes. A pivot on origin → destination with summed weight and charges shows which lanes carry the volume and what they actually cost — the negotiation ammunition that’s invisible in a filing cabinet.
4. Track OS&D. Signed copies with exception notes are the paper trail for shortage and damage claims; with dates and BOL numbers in columns, the claim that’s about to hit its filing deadline is a sort away.

If the log lives in a shared workbook, the same XLSX imports straight into Google Sheets — the PDF-to-Google-Sheets Mac guide covers that handoff.

Bottom line

For bill of lading PDFs that need to become a shipment log on a Mac: drag the batch into ignitai, write the one-paragraph prompt (one row per BOL, each field from its labeled box, empty when not printed), pick Excel, Convert, then run the invoice audit and the lane pivot. Use Preview-and-paste for a single born-digital form; keep customer and pricing data away from web converters entirely. The coordinator’s hour belongs on the exceptions and the claims, not the retyping — and the on-device read means the freight files never left your Mac to get there.

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 bill of lading PDF to Excel on a Mac?

Drag the PDFs into ignitai, describe the fields in one sentence — BOL number, ship date, shipper, consignee, carrier, PRO number, pieces, weight, freight class, charges — and tell it to take each value from its labeled box and leave missing fields empty. Pick Excel and hit Convert. The batch comes back as one sheet with one row per BOL, ISO dates, and bare amounts.

Does it work on scanned or faxed bills of lading?

Yes — signed BOLs and proof-of-delivery copies usually arrive as scans, and the document is read on-device rather than parsed for a text layer, so a scanned or faxed copy works the same way as a born-digital PDF. The cleaner the scan, the sharper the extraction, and macOS 26’s native table recognition helps on dense commodity grids.

Can it pull the commodity line items instead of one row per BOL?

Yes, as its own run — the output is always one table per run, so you choose the shape in the prompt. ‘One row per BOL’ builds a shipment log from a batch; ‘one row per commodity line, repeating the BOL number on each row’ explodes the line items. Two shapes means two runs with two prompts.