EDI automation built for freight
Trading partner onboarding that used to take weeks now takes hours. A visual mapping workbench, automated inbound and outbound pipelines, and full envelope history — in one place.
Map EDI to your data. Visually.
Stop building field mappings by hand in a text editor. The PulseCargo™ mapping workbench shows you the raw EDI file, your target data model, and a click-to-connect surface — in three columns, side by side.
Three-column interface
Raw EDI file on the left. Target data model on the right. Click-to-connect mapping surface in the middle. Drag a segment. Click the target field. Set a transform if needed. Save the overlay.
Per-partner overlays
Each trading partner gets their own mapping overlay layered on the shared engine. When a partner updates their spec, you update the overlay — not the whole mapping. Version history is preserved.
X.12 transaction sets
204, 210, 214, 315, 322, 850, 856. The sets your ocean and trucking partners send and receive. EDIFACT support in architecture.
Transform support
Field-level transforms for data type conversion, string manipulation, and conditional logic — without writing code. Set it in the workbench, save it to the overlay, and move on.
One registry for every trading partner.
Every EDI relationship is different. PulseCargo tracks them all in a per-partner configuration that lives in the platform — not in a shared drive or someone’s email.
Per-partner transaction sets
Configure which X.12 transaction sets each partner sends and receives. One partner may send 856s; another sends 214s. Each is configured independently.
Per-partner field mapping overlays
Each trading partner’s segment quirks are captured in their own overlay. Partners with non-standard implementations don’t break the shared mapping engine.
Channel configuration
SFTP, AS2, or FTPS per partner. Credentials, endpoints, and connection settings stored per partner. The transport layer is independent of the mapping layer.
Inbound and outbound pipelines
Manage both directions per partner. Inbound pipeline: receive, parse, validate, map, deliver. Outbound pipeline: generate, envelope, send, confirm.
Envelope history
Every inbound and outbound envelope is retained with timestamp, ISA control number, transaction sets, and processing result. Downloadable per envelope.
ACK tracking and control numbers
Functional ACKs (997/999) generated automatically for inbound transactions. Control number sequencing managed per partner and per direction. No manual tracking.
Full EDI flow — both directions.
Receive, parse, deliver
Your trading partners send EDI via SFTP, AS2, or FTPS. PulseCargo receives the file, validates the envelope, parses the transaction sets against your mapping overlay, and delivers the structured data into your operational records.
- Functional ACKs generated automatically
- Parsing errors flagged and retained for debugging
- Test endpoints for pre-live validation
Generate, envelope, send
Generate EDI from data already in your TMS. PulseCargo wraps the transaction set in the correct envelope, sequences the control numbers, and delivers to the partner via their configured channel.
- Control numbers managed per partner and direction
- Retry handling for failed deliveries
- Delivery confirmation logged per envelope
EDI traffic at a glance.
The EDI dashboard shows you what’s moving — inbound and outbound — across all trading partners. Exceptions flagged. ACKs tracked. Channels monitored.
Portal admin view
Cross-tenant EDI activity across all partners, all tenants. See what’s flowing, what’s failing, and what’s held for review — from one view.
Tenant admin view
Your own EDI traffic, filtered to your partners. No access to any other tenant’s envelope history. Isolation is enforced at the data layer, not at the query layer.
EDI specifics.
What X.12 transaction sets are supported?
204 (Motor Carrier Load Tender), 210 (Freight Invoice), 214 (Shipment Status), 315 (Status Details — Ocean), 322 (Terminal and Ramp Activity), 850 (Purchase Order), 856 (Ship Notice/ASN). More being added based on partner demand.
What transport channels are supported?
SFTP, AS2, and FTPS for both inbound and outbound. Each trading partner is configured independently with their own channel and credentials. Email-drop (inbound via mailbox) is on the roadmap.
How does the mapping workbench handle spec changes?
Each trading partner has their own mapping overlay layered on the shared engine. When a partner updates their spec, you update their overlay. The underlying engine and other partners’ mappings are not affected.
What happens when an inbound file fails?
The envelope is retained in history with the error detail. A functional ACK with reject reason is sent if the transaction set warrants it. The failed file is available for download and replay once the mapping issue is corrected.
Ready to connect your first trading partner?
EDI onboarding takes hours, not weeks. Contact us to see the mapping workbench in a live environment.
Request a demo →