Enterprise EDI Integration (ANSI X12)
Jet Delivery supports full ANSI X12 Electronic Data Interchange (EDI)
for enterprise customers requiring structured, file-based logistics integration.
Our EDI environment is production-grade, secure, and actively used by
aerospace, healthcare, manufacturing, and retail customers.
EDI implementations are coordinated directly with your technical team.
We provide mapping guidance, test files, validation rules, and go-live support.
Supported X12 Transaction Sets
204
Motor Carrier Load Tender
Used to submit shipment requests to Jet Delivery.
Includes shipper, consignee, service level, equipment, and reference data.
990
Load Tender Response
Acceptance or rejection of a 204 load tender.
214
Shipment Status
Pickup, in-transit, delay, and delivery status updates.
210
Motor Carrier Freight Invoice
Electronic invoice transmission including line item charges and fuel.
Secure File Transfer Options
We support multiple secure exchange models depending on your internal compliance requirements:
- SFTP (SSH encrypted)
- FTPS (SSL/TLS secured)
- HTTPS file transfer
- Standard FTP (when mutually approved)
Exchange models supported:
- You upload tenders to Jet Delivery
- You retrieve responses from Jet Delivery
- Jet Delivery pushes responses to your server
- Bi-directional polling exchange
All production connections require credential provisioning and directory isolation.
204 Load Tender — Required Business Fields
To ensure correct service routing and dispatch automation, the following fields are required:
N7-19
Type of Service Code
Required
2-digit service type identifier.
Example: 05
L11 (Qualifier ZZ)
Vehicle Code
Required
3-character vehicle code.
Example: L11*VAN*ZZ~
Tenders missing required service or vehicle fields may be rejected or placed on hold.
Implementation & Testing Process
- Technical kickoff — Confirm transaction sets, connectivity model, and identifiers.
- Mapping alignment — Review service codes, equipment codes, and references.
- Test file exchange — Validate ISA/GS/ST envelopes and segment compliance.
- Parallel testing — Validate operational accuracy.
- Production cutover — Controlled go-live with monitoring.
Typical implementation timeline: 2–4 weeks depending on partner complexity.
Validation & Error Handling
- ISA/GS/ST envelope validation
- Segment-level syntax validation
- Required business rule validation
- Service / equipment mapping validation
Rejected tenders will be returned via:
- 990 rejection message
- Email notification (if configured)
- Manual coordination for critical shipments
Security & Compliance
- Encrypted transport (SFTP / FTPS / HTTPS)
- Credential-based authentication
- IP restriction (optional)
- Directory isolation per trading partner
- Audit logging of inbound/outbound files
Getting Started
To begin EDI onboarding, please contact your
Jet Delivery sales representative.
Share the transaction sets you need (204/990/214/210), your preferred connectivity
(SFTP/FTPS/HTTPS), and a technical contact. We’ll coordinate mapping and testing.