1
Open the Load
In the left sidebar, click Shipments (Loads) and find the delivered load. Click it to open the drawer.
2
Go to the Documents Tab
Click the Documents tab inside the load drawer.
3
Upload Your File
Drag and drop your file into the upload area, or click to browse.Common POD formats include PDF, PNG, JPG/JPEG, GIF, BMP, WebP, and TIF/TIFF. Maximum file size: 20 MB.
4
Select the Document Type
In the preview dialog, choose Proof of Delivery from the dropdown (or another type if you’re uploading a different document), then click Confirm.
5
Verify the Upload
Wait for the Upload successful message. The file then appears in the table with Document Type, File Name, Created By, and Last Modified.Confirm that Document Type says Proof of Delivery. Click the filename to make sure the file opens.
Send PODs Over SFTP
Send PDFs through your Owlery SFTP connection, and Owlery attaches them to the matching load automatically. You only need SFTP access; an EDI translator or API integration is not required.1
Name the File After the Load Number
Name each PDF after the exact Load Number, for example,
37964416.pdf. Owlery removes the final extension and trims surrounding whitespace to find the load number. Do not add a document label or timestamp: 37964416_POD.pdf searches for load number 37964416_POD.Confirm the number on the load in Owlery. See Find Your Load Number.2
Place It in the Document Type Folder
Upload the file to
documents/{type}/ within your trading partner’s upload directory. For example, use documents/pod/37964416.pdf for a proof of delivery.Use a folder value from the table below. Folder values and the .pdf extension are matched case-insensitively. Only PDFs qualify for this document route. The SFTP document upload limit is 100 MiB (100 × 1024 × 1024 bytes).3
Confirm It Attached
Owlery saves the PDF on the matching load with a source of SFTP. Open the load’s Documents tab to verify it. After successful processing, Owlery moves the source file to the processed location, preserving its document folders and filename.
Supported Document Types
Use
purchaseorder for purchase order documents. All listed types attach a file to the load. Uploading an invoice or purchaseorder PDF through this route does not itself create a structured Invoice or Order record.
How Owlery Matches and Saves Files
Your trading partner directory must be configured against a broker profile in Owlery. This route does not support a directory configured only for a facility. Owlery requires exactly one non-deleted load with your broker profile and the load number from the filename. Matching spans your broker’s loads across shippers. Order numbers, BOL references, and partial matches are not used. Owlery saves the original filename, document type, SFTP source, and association with the load. If identical file content is already recorded on that load, Owlery reuses the existing document. Sending the same content under another filename or type does not change its existing type. The source upload still moves to the processed location.Files That Do Not Attach
- No matching load or multiple matches: Owlery moves the file to the failed location. Confirm the exact load number and resolve duplicate load numbers before uploading again.
- Missing broker configuration or a download or save error: The file also goes to the failed location. Contact support@owlery.ai if the filename is correct and the load exists.
- Unrecognized folder or non-PDF file: The file does not enter this document route. Other inbound rules may handle it; skipped files remain in the upload location. A file named
pod.pdfat the root does not identify a document type. - File remains in upload: Check the load’s Documents tab before resending. A move can fail after the document is saved. Contact Support if the file’s status is unclear.
Additional Path Details
Usedocuments/{type}/{loadNumber}.pdf for your uploads. The current matcher also recognizes a type in other directory segments below your partner directory, such as pod/37964416.pdf or inbound/bol/37964416.pdf. If multiple folder segments identify types, the first one wins. A type appearing only in the filename does not qualify.
Top-level outbound/ files are ignored, and tracking/ files use a separate flow. Temporary files ending in .tmp or .partial are not ingested. You do not need to add .pdf to your allowed EDI extensions for typed document uploads.
Reconcile a Missing-POD List
If a shipper sends you a list of loads missing PODs, work through the list by Load Number.1
Find the Exact Load
Search Shipments (Loads) for the Load Number on the list. Confirm the shipper and delivery location before opening it.
2
Check Documents First
Open Documents and look for a file whose Document Type is Proof of Delivery.A file with another type, such as Bill of Lading, does not satisfy a POD check even if the filename contains “POD.”
3
Upload Only What Is Missing
If no POD is present, upload it and select Proof of Delivery. Do not upload the same file again when a valid POD already appears.
4
Record Verification
Confirm the filename and Last Modified time, then mark that Load Number complete on the list. Repeat for the next load.
If the Shipper Still Reports a Missing POD
- Confirm that the POD is attached to the same Load Number the shipper listed.
- Confirm that its Document Type is Proof of Delivery.
- Open the filename to confirm the upload is readable and belongs to that load.
- If an invoice was disputed for Missing POD, return to the invoice and confirm its status after the shipper’s rules re-evaluate it. See Track and Fix Invoices.
- If the POD was attached to the wrong load, upload it to the correct load and contact support@owlery.ai with both Load Numbers.