Email Ingestion
As an alternative to SFTP, you can email BOL documents directly to a dedicated email address assigned to your organization during onboarding.
Email + Metadata
Attach BOL PDFs with an index.json file
File Name Convention
Encode metadata in the file name
How It Works
Send an email to the dedicated ingestion address with your BOL PDF(s) attached. Include an index.json metadata file as an additional attachment to describe the shipment. The index.json follows the same specification as the SFTP method.
Provided during onboardingAlternative: File Name Convention
If you are unable to include an index.json file, you can encode shipment metadata directly in the PDF file name or email subject line. The system will parse the following format to identify and publish the eBOL:
File Name Format
<order_number>_<trailer_number>_<seal_number>_<branch_plant_12_char>_<ship_to>_<timestamp>.pdfExample
123456_NF13589_12218008_FortWorthTX_RETAIL01_20250115143022.pdf| Segment | Description | Example |
|---|---|---|
| order_number | Order or delivery number | 123456 |
| trailer_number | Trailer identifier | NF13589 |
| seal_number | Seal number on the trailer | 12218008 |
| branch_plant_12_char | Branch/plant identifier (max 12 characters) | FortWorthTX |
| ship_to | Receiver/destination identifier | RETAIL01 |
| timestamp | Upload timestamp (YYYYMMDDHHmmss) | 20250115143022 |
Limitations of file name convention
- Character limits apply to each segment (e.g., branch/plant is capped at 12 characters)
- No support for multiple order or PO numbers
- Fields like carrier name, customer name, and receiver name cannot be included
- The metadata file approach is recommended for complete data submission
Prefer SFTP for production use
Email ingestion is best suited for low-volume submissions or initial testing. For production workflows, we recommend the SFTP method for its reliability, automation support, and richer metadata capabilities.
View SFTP Documentation