Guide · Inbound
How to turn a PDF purchase list into clean rows without retyping it.
The purchase list arrives as a PDF with merged columns. Someone retypes it into a spreadsheet every cycle, and every typo later shows up as a stock-out.
Most distribution warehouses receive their procurement or purchase list as a PDF from a head office, a cooperative or a supplier. The PDF looks tidy on screen, but copying it out is slow: columns are merged, quantities for several hubs sit in one cell, and product names do not match the names in your own master.
Why copy-paste and generic converters fail
- Merged columns: a single cell may hold the product, the pack size and a quantity, so pasted rows land in the wrong columns.
- Quantities by hub: one line may carry quantities for several collection points that must be split.
- Names that drift: the supplier’s description differs from your SKU name, so a lookup silently fails.
- Page breaks: a table that continues over pages repeats headers or loses rows.
- No check: a converted file is just text; nobody tells you a line did not match the product master.
A reliable way to do it
- Read every row of the PDF, including merged columns, into a structured table.
- Split quantities by hub so each row is one product for one location.
- Match each line to its SKU in the product master: packing, weight and storage zone.
- Flag mismatches for a person to resolve; never guess a match.
- Only then let the rows count as expected stock for receiving at the gate.
A quick quality check before you receive
| Check | Why it matters |
|---|---|
| Row count equals the PDF’s line count | Catches rows lost at page breaks |
| Total quantity per hub equals the PDF totals | Catches split errors |
| Every line matched to a SKU | Unmatched lines become stock-outs later |
| Weight known for every SKU | Needed later for bag allocation |
How Warehouse OS does it
Warehouse OS is built for distribution warehouses that fulfil many small orders every cycle. The cycle’s purchase list is read from the PDF, including merged columns, and each line is checked against the product master. Receipts are logged with vehicle, gate and challan; stock is put away to the zone and rack a 3D twin of the floor suggests. Member orders are joined with product weights so every order gets a small bag, a large bag or a split before packing starts. Each permanent bag tag is scanned to a durable dispatch box carrying its route, van and member, and every receipt, move and dispatch stays on one record. It runs on web and handheld.
Questions
How do I convert a PDF purchase list into Excel rows?
Read every row including merged columns into a table, split quantities by hub, then match each line against your product master and flag anything that does not match before it counts.
Why do PDF-to-Excel converters give wrong rows?
Purchase lists often merge several fields into one cell and carry quantities for many hubs per line; a generic converter copies the layout, not the meaning, and does not check against your product master.
What should be checked after extracting a purchase list?
Row counts, totals per hub, a SKU match for every line and a known weight for every SKU.
See it on your own data. Warehouse OS — Purchase list to packed orders. Book a 30-minute working session with an engineer.