When Suppliers Send PDFs, Excel Files,
and WhatsApp Messages: One Workflow for All
A freight forwarder's inbox on any given morning contains: a bill of lading PDF from Maersk, a commercial invoice in an Excel spreadsheet from a Shenzhen supplier, a packing list photo sent via WhatsApp by a truck driver at the loading dock, a scanned certificate of origin from a Brazilian exporter, and a customs broker's email with the declaration details typed directly into the message body. Five documents. Three file formats. One goal: extract the relevant fields from all of them into a single shipment record. For most logistics teams, this means opening each file individually, reading each one, and typing the data into a tracking spreadsheet or TMS. The extraction isn't the bottleneck. The format switching is.
Key Takeaways
- Five documents, five file formats, one morning inbox — the real bottleneck isn't reading the data, it's the mental whiplash of switching from PDF viewer to Excel to WhatsApp while trying to stitch everything into a single shipment record.
- "Get your suppliers to use a standard template" is a coordination fantasy — those 150 monthly files you receive across xls and pdf come from organizations that gain nothing from reformatting, because standardization only benefits the receiver.
- Stop asking 50 suppliers to change how they work and start building a receiver that handles any format — ImageToTable.ai processes PDFs, Excel sheets, WhatsApp photos, and email body text through the same field definitions, producing a single consolidated row regardless of how many formats fed into it.
The Format Chaos That Defines Real Logistics Work
Software vendors tend to describe logistics document processing as if all documents arrive in the same format through the same channel. The demo shows a clean PDF pipeline: documents in, structured data out. The reality, as anyone working in freight forwarding or supply chain operations knows, is nothing like that.
One Reddit user attempting to automate supplier communications captured the experience exactly: "One sends a PDF quote, another replies in broken English, third one just says 'WhatsApp me.'" The formats are unpredictable because the suppliers are unpredictable — and you cannot force a supplier in Shenzhen or São Paulo to standardize their document output to fit your internal workflow. They use what they have. A small factory might generate invoices in Excel with merged cells and color coding. A regional trucking company might issue delivery notes as handwritten carbon copies photographed on a phone. An overseas agent might forward a PDF created from a scan of a scan of a fax.
The Make Community forum records the same pattern at scale: one user described receiving "150 different files monthly, in xls and pdf, sent by different organizations, formats not standardized." That's 150 documents per month, each potentially in a different layout, from organizations that will never coordinate their formatting with each other.
The standard advice — "ask your suppliers to use a standard template" — is not practical at scale. A freight forwarder working with 50 suppliers across 15 countries is not going to train 50 organizations to adopt a common document format. Suppliers have their own systems, their own processes, their own reasons for formatting things the way they do. The burden of adaptation falls on the receiver. The question is whether the adaptation is manual typing or automated extraction.
The logistics industry's document format problem is not a technology problem — it's a coordination problem that technology can solve asymmetrically. You don't need everyone to standardize. You need a receiver that handles anything.
Why Format Standardization Isn't the Answer
Attempts to standardize supplier document formats fail for the same reason they've always failed: standardization benefits the receiver, not the sender. A freight forwarder saves hours per week if every supplier submits documents in a consistent format. But the supplier gains nothing — they're already sending documents the way their own system generates them, and changing that format adds work to their side for a benefit that accrues entirely to yours.
This asymmetry is most acute with smaller suppliers and agents. A factory with ten employees generates invoices in the Excel template they've used for a decade. A truck owner-operator sends delivery confirmations as phone photos because they're on the road with no access to a scanner or PDF converter. An overseas buying agent forwards documents via WhatsApp because it's the fastest channel between two time zones. These aren't examples of poor process — they're examples of optimized process for the sender's constraints. Asking them to change introduces friction into a relationship where you're the one asking for a favor.
The realistic approach is to accept that documents will arrive in multiple formats and design the extraction workflow around that inevitability. The goal isn't format standardization at the source. It's format-agnostic extraction at the receiver.
One Column List, Every Format
Column-name extraction makes format-agnostic processing possible because it separates what you want to know from how the document is structured. You define the fields you need — shipment reference, shipper, consignee, commodity description, weight, value, origin — once. The AI reads each document, in whatever format it arrives, and locates the corresponding values by understanding what they mean rather than where they sit.
This is fundamentally different from format-specific extraction, where a PDF tool reads PDFs, a spreadsheet tool reads Excel files, and someone manually types data from WhatsApp photos. Format-specific extraction requires pre-sorting: open each document, identify the format, route it to the appropriate tool, then combine the results. Format-agnostic extraction processes everything through the same field definitions — the AI distinguishes PDF text layers from spreadsheet cells from photographed carbon copies on its own.
Consider a shipment record built from five documents in five formats:
| Document | Format | Fields Extracted | Format-Specific Tool Needed? |
|---|---|---|---|
| Bill of lading from Maersk | B/L number, vessel, voyage, container, weight | Yes (PDF tool) | |
| Commercial invoice from Shenzhen supplier | Excel (.xlsx) | Invoice number, item descriptions, unit prices, total value | Yes (Excel tool) |
| Packing list from loading dock | WhatsApp photo | Package count, weight per package, marks | No — manual typing |
| Certificate of origin from Brazil | Scanned PDF | Exporter, country of origin, certifying authority | Yes (OCR tool) |
| Customs declaration from broker | Email body text | Entry number, HS codes, declared values, duty paid | No — manual reading |
With format-specific tools, this shipment requires three different extraction tools plus two manual transcription steps — and then all five outputs must be manually combined into a single record. With column-name extraction, all five documents upload into a single batch, process through the same field definitions, and output into one consolidated row.
A typical multi-format logistics field list:
Shipment Reference | Document Type | B/L or AWB Number
Shipper Name | Consignee Name | Origin Country
Commodity Description | HS Code | Quantity
Gross Weight (KGS) | Declared Value | Invoice NumberCollection Link: One Inbox for All Suppliers
Standardizing the formats suppliers use is impractical. Standardizing the channel they send through is not.
The Collection Link generates a shareable upload page — a single URL you can give to every supplier, agent, and driver. The recipient opens the link, enters a short verification code, and uploads their document. They don't need an account. They don't need a login. They don't need to install anything. The file — whether it's a PDF, an Excel sheet, or a phone photo — lands directly in your processing queue.
This replaces the fragmented intake that defines most logistics operations: documents arrive across email, WhatsApp, WeChat, fax, and physical mail, and someone has to gather them all into one place before processing can begin. A Collection Link consolidates intake into a single channel without requiring the sender to change their document format or workflow. The sender still generates documents however they want — they just send them to one place instead of five.
For teams processing documents across locations, the link can be shared with warehouse staff who photograph PODs at the dock, overseas agents who forward supplier paperwork, and drivers who submit delivery confirmations from the road — all feeding into the same queue.
Step by Step: Mixed-Format Freight Extraction
Files processed securely, not stored. Type your field names and upload different file types to test cross-format extraction.
Frequently Asked Questions
Can I really upload PDFs, Excel files, and photos in the same batch?
Yes. The AI detects the file type automatically and applies the same field definitions regardless of format. A PDF bill of lading, an Excel commercial invoice, and a photographed packing list all process through the same upload and produce output rows with the same column structure. No pre-sorting or format-specific routing is required.
Do I need to configure anything differently for each supplier's format?
No. Because extraction is driven by the field names you define — not by templates tied to specific document layouts — the same configuration works across all suppliers and all formats. A new supplier sending documents in a format you've never seen before processes through your existing field definitions without additional setup.
How do suppliers send documents through the Collection Link?
You generate a shareable link and send it to the supplier. They open it in a browser, enter a short verification code, and drag-and-drop or select their file. They don't create an account, install software, or learn a new system. The file appears in your processing queue immediately. The link can be shared through email, WhatsApp, or any other channel the supplier already uses to communicate with you.
What about documents that arrive in languages other than English?
The AI processes documents in multiple languages — Chinese, Spanish, Portuguese, French, Arabic, and others — through the same field definitions. A Chinese-language commercial invoice and an English-language BOL can process in the same batch. The field names you define tell the AI what to look for; the AI handles the language of the source document automatically.
How does extraction accuracy compare between clean PDFs and photographed documents?
Clean digital PDFs with embedded text layers produce the highest accuracy — near 99% for printed fields. Photographed documents introduce variables (lighting, angle, resolution) that reduce accuracy proportionally to image quality. The AI compensates for perspective and lighting better than traditional tools, but a well-lit, flat, high-resolution photo will always produce better results than a dim, angled, compressed WhatsApp image. For the most accurate extraction, request PDFs when possible but accept photos when necessary — the workflow handles both.
For focused freight document to Excel conversion, our bill of lading tool processes BOLs from every carrier into a single structured spreadsheet.
For specific document types within the logistics workflow, see our guides on extracting bill of lading data, processing handwritten proof of delivery, and extracting customs declaration fields. For the broader principle of handling format variety, read about unifying data from documents in different formats.