Purchase Orders Become Rows in Google Sheets — Line Items Expanded, Columns Named Once
Most purchase order tools demand a per-supplier template or hand you a blank sheet to type into — the add-on reads any PO and writes its header and line items into your active sheet in 5–10 seconds, columns named once.
5–10s per PO page · 99% accuracy on printed text · Native Sheets sidebar · No templates, no Zapier
A Purchase Order in Your Tracker: Header Fields Once, Line Items as Rows
Type the column names you need into the sidebar — they become your table headers in Google Sheets. The AI finds each value by understanding what the field means, not where it sits, so one column list handles a one-line office-supplies order and a 40-line machine-shop PO in the same batch.
Header Fields — Once Per PO
Line Item Fields — One Row Per Line
The mechanism is Custom Column Extraction: you decide the columns, the AI fills them. "Order No.", "Document No.", and "PO Ref." all land in your PO Number column. Type header and line-item fields together — the AI writes header values once and expands each line item into its own row.
A PO Tracker Is a Living Spreadsheet — and Every New Purchase Order Is a Page of Typing
Procurement teams keep open orders in a shared sheet — PO number, supplier, dates, quantities, and unit prices, one row per line item. That tracker is only as current as the last person who typed into it. One buyer on r/procurement described the columns their daily working sheet holds: "list the supplier, p/n, qty, u/p, date you issued PO, supplier acceptance need by date". Every new PO means typing all of that again.
One PO is a header plus every line item — typed separately. A 15-line PO means the header fields (PO Number, Vendor Name, PO Date, Delivery Date) typed once, then fifteen more rows of Line Item, Quantity, Unit Price, and Line Total. One mistyped quantity and the tracker's totals are wrong, with no trail back to the error.
Every supplier prints the same PO differently. One supplier puts the item table under the header, another on page 2; labels vary — "Order No.", "Document No.", "PO Ref." Template-based tools break with each new supplier format and need constant maintenance.
The tracker only fills when someone remembers to update it. Free PO templates hand you columns, not data — the keying is identical. When the sheet drifts from the actual POs, delivery dates slip and no one notices until the supplier asks.
Name the columns once — the AI writes the header once and expands each line item into its own row. This is Custom Column Extraction: type PO Number | Vendor Name | Delivery Date alongside Line Item | Quantity | Unit Price | Line Total, and the header values repeat on every line row.
The add-on reads by meaning, not position — so supplier layouts stop mattering. "Order No.", "Document No.", and "PO Ref." all fill your PO Number column. One column list handles a new supplier, an ERP-generated PDF, and a scanned paper PO in the same batch — and a supplier redesign changes nothing.
The sidebar writes straight into the active sheet — no CSV, no re-import, no Zapier. No intermediate file to download or remap. The sidebar is the extraction engine; your tracker is the destination — the sheet stays the single source of truth, filled in the same pass that reads the PO.
From a Stack of Supplier POs to Rows in Your Tracker — in Three Steps
Upload — the POs as they arrive
If you're catching up on open orders, drop in the PO PDFs from email and supplier portals, phone photos of paper POs, and scanned copies — mixed freely in one batch, multi-page files included. The add-on accepts JPG, PNG, and PDF. Clean digital PDFs read best; straight-on photos in decent light are close behind.
Name your columns — matching the tracker you already have
Type the column list once: PO Number | Vendor Name | PO Date | Delivery Date | Line Item | Description | Quantity | Unit Price | Line Total | Total. For POs that don't print a line total, define a computed column named Line Total (Qty × Unit Price) and the AI multiplies during extraction. Add Category (options: Raw Materials/MRO/Services) as an inferred column and every line is classified in the same pass — no PO prints a category label.
Extract — each PO becomes rows, appended below your data
Click Extract. Each PO takes 5–10 seconds: header fields land once, and every line item becomes its own row in the next empty rows of the active sheet, headers matching the columns you named. A 20-PO week that would take hours of keying processes in a few minutes — and next week's POs append below, no re-mapping.
When PO-to-Sheets Works Best — and Where It Stops
Extraction is reliable on standard digital POs and clean scans — a few cases are worth knowing up front.
Handles reliably
Digital PO PDFs from ERP and accounting systems. SAP, NetSuite, and QuickBooks exports carry clean text — PO number, dates, and totals extract at near-perfect accuracy.
Multi-supplier batches with one column setup. Upload POs from ten suppliers at once; each lands as rows under the same headers, tagged with its own vendor name.
Standard printed POs and clear scans. ERP-generated PDFs and office scans at 200 dpi, including line-item tables, extract reliably.
Verify these cases
This writes PO data into a spreadsheet — it is not a procurement or ERP system. It won't send POs to suppliers, route approvals, or manage inventory; the rows are raw material for the tracker.
Multi-page POs with line-item tables that span page breaks. A product row spanning a page break can split — cross-check the last row of each page.
Handwritten, faxed, or mixed-unit tables. Faint carbon-copy and faxed POs reduce accuracy, and a table mixing units (each, case, pallet) in one column deserves a quick check of the Quantity and Unit Price cells.
Frequently Asked Questions
Can the add-on expand line items into their own rows while keeping PO Number and Vendor Name on every row?
Yes. Add the PO-level columns — PO Number, Vendor Name, PO Date, Delivery Date — alongside the line-level columns — Line Item, Description, Quantity, Unit Price, Line Total — and the AI writes each line item as its own row, repeating the PO-level values on every row. A 15-line PO becomes 15 rows, each traceable back to its PO number. When a PO doesn't print a line total, define a computed column such as Line Total (Qty × Unit Price) and the AI multiplies during extraction.
Some suppliers print the delivery date and shipping terms differently — can Delivery Date and Shipping Terms each have their own column?
Yes, and they don't need identical labels. Type Delivery Date and Shipping Terms as column names; the AI fills Delivery Date from whichever line the supplier labels "Requested Delivery", "Ship Date", or "ETA", and Shipping Terms from the header even when it's an abbreviation like FOB or Freight Prepaid. When a PO genuinely doesn't print a value, the cell stays blank rather than inventing one.
Will the extracted rows match the PO tracker I already have?
Yes, because you define the column names to match. If your tracker already has PO #, Supplier, Qty, and Unit Price columns, type those exact names in the sidebar — they become the headers, and extracted rows append below your current data. Your existing formulas (SUMIF by supplier, conditional formatting on late deliveries, pivot tables) keep working on the new rows.
My POs don't print a Line Total — can the AI calculate it?
Yes. Define a computed column named Line Total (Qty × Unit Price) and the AI multiplies during extraction instead of trusting a printed figure. The same mechanism handles totals when your POs print them differently than your tracker expects — for example Subtotal (Sum of Line Totals) or Tax (Subtotal × Rate).
Does this tool manage my procurement — approvals, inventory, sending POs to suppliers?
No — and it's important to say so plainly. The add-on writes PO data into spreadsheet rows; it is not a procurement or ERP platform. It won't send POs to suppliers, route approvals, or manage inventory. What it removes is the keying step: once every PO is rows in your tracker, the approval and follow-up work happens where it always did — in your spreadsheet and your procurement process.