Third-Party Logistics integration

Dunavant EDI integration

How EDI and API integration with Dunavant typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Dunavant.

At a glance

Dunavant integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Dunavant program or a customer relationship.

Illustration of a container ship at sea, representing the third-party logistics industry that Dunavant operates in.
Industry. Third-Party Logistics: where Dunavant operates.
Workflow diagram: your TMS, ERP and finance systems exchange documents with Dunavant through ECOM. You send 300; you receive 301, 315, 310, 214; 997 acknowledgments go both ways. Your systems TMS · ERP · finance ECOM integration map · validate · connect · monitor Dunavant 300 300 301 315 310 214 301 315 310 214 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Tenders and invoices re-keyed Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Dunavant

Tell us which documents you exchange with Dunavant, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Dunavant.

  • Review of Dunavant's requirements with you, once you have them
  • EDI and API integration with your TMS, ERP and finance systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Dunavant

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Dunavant integration fits your systems

Your systemsTMS, ERP and accounting
ECOMMapping, validation, connectivity and monitoringAS2, SFTP or VAN · Carrier API · Portal or TMS network
DunavantIts program, documents and requirements
  1. ConfirmConfirm your Dunavant program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding Dunavant integration

Who this is for: Importers, exporters and shippers that move freight with Dunavant, and their logistics, compliance and finance teams.

Scope: This guide describes typical practice for this kind of trading relationship; Dunavant's own program details are confirmed during onboarding.

Dunavant provides logistics services. ECOM's directory lists it under global logistics. Shippers working with forwarders and customs providers typically request bookings, receive confirmations and milestone updates, and receive freight invoices, with customs data handled in parallel.

Teams that work with a freight forwarder or customs provider gain most from fast tender responses and status they can trust. Dunavant's own EDI or API specification is not part of this guide and no Dunavant document was read: treat what follows as typical practice for a freight forwarder or customs provider, and confirm the documents, X12 version, delivery method and testing steps with Dunavant.

ECOM maps the documents to your TMS, ERP and finance systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.

Business scenarios

Where Dunavant integration gets complicated

Typical requirements—confirm with your trading partner.

Milestone visibility

Milestone events show where freight is and when it clears.

How ECOM helps: ECOM connects tender, response and status messages (214) to your TMS or ERP and shows where each load stands, flagging missing or late status.

What you gain: Planners see current load status, and late or missing messages are noticed early.

Multi-leg international shipments

International moves chain bookings, milestones, customs and charges across several parties. Identifiers have to link every leg.

How ECOM helps: ECOM builds the ship notice from your shipment data, checks it against the order and the label data before it is sent, and flags differences you can fix before the load leaves.

What you gain: Fewer receiving problems and compliance deductions caused by notices that do not match the load.

Charges and accessorials

Invoices include many charge lines that must reconcile to the quote.

How ECOM helps: ECOM matches freight invoices to the tender and status (214) history and lists charges that differ from the agreed rate or have no supporting event, so they can be reviewed before payment.

What you gain: Fewer overcharges paid, and less manual freight audit work.

Returns processing

Returned goods need receipt, disposition and credit documents that reconcile.

How ECOM helps: ECOM monitors each document and acknowledgment, flags rejected, late or mismatched ones and routes each exception to a named owner with the document history attached.

What you gain: Billing and delivery problems are corrected sooner, with less chasing by phone and email.

Workflows

Typical Dunavant business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not Dunavant's published process.

Booking to invoice

  1. 1Send 300 booking request
  2. 2Receive 301 confirmation
  3. 3Receive 315 milestones
  4. 4Receive 310 invoice

Customs coordination

  1. 1Share shipment data
  2. 2Provider prepares entries
  3. 3Receive clearance status
  4. 4Reconcile charges

Documents and APIs

Dunavant documents by program

General guidance. We could not verify Dunavant's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Dunavant's confirmed requirements. Confirm the list, versions and programs with Dunavant.

DocumentNameDirectionProgramStatusPurpose
300 Reservation (Booking Request) (Ocean) To Dunavant Not stated General guidance Typically requests space or a booking on a vessel.
301 Confirmation (Ocean) From Dunavant Not stated General guidance Typically confirms a booking with sailing and equipment details.
315 Status Details (Ocean) From Dunavant Not stated General guidance Typically reports shipment milestones such as gate-in, loaded and discharged.
310 Freight Receipt and Invoice (Ocean) From Dunavant Not stated General guidance Typically bills an ocean shipment with freight and charge detail.
214 Transportation Carrier Shipment Status Message From Dunavant Not stated General guidance Typically reports pickup, location updates and delivery.
997 Functional Acknowledgment Both directions Not stated General guidance Typically confirms that each file was received and could be read.

Connectivity

How companies connect

  • AS2, SFTP or VAN

    Carriers and brokers commonly exchange EDI over AS2, SFTP or a value-added network.

    General guidance

  • Carrier API

    Many carriers also expose tracking, rating or tender APIs next to EDI.

    General guidance

  • Portal or TMS network

    Some carriers and brokers work through a customer portal or a transportation management network instead of, or beside, direct EDI.

    General guidance

Challenges

Common integration challenges

  • Linking identifiers

    Booking, container and bill of lading references must connect.

  • Customs data

    Customs data accuracy affects clearance.

  • Milestone gaps

    Missing events hide delays. Ask Dunavant how this applies to your program.

  • Invoice detail

    Charge lines vary by lane. Requirements vary by program.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set by Dunavant. ECOM works from them during mapping and testing.

Automation options for Dunavant shippers

Four ways to automate. One foundation.

ECOM helps you automate the exchange, connect it to your systems, and see what needs action. Dunavant sets its own requirements; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

General EDI flow

How EDI with Dunavant typically works

The documents, their order and the timing are Dunavant's to set; this is the general sequence most programs of this kind follow.

  1. 300 Reservation (Booking Request) (Ocean)

    From you to Dunavant

    Typically requests space or a booking on a vessel.

  2. 301 Confirmation (Ocean)

    From Dunavant to you

    Typically confirms a booking with sailing and equipment details.

  3. 315 Status Details (Ocean)

    From Dunavant to you

    Typically reports shipment milestones such as gate-in, loaded and discharged.

  4. 310 Freight Receipt and Invoice (Ocean)

    From Dunavant to you

    Typically bills an ocean shipment with freight and charge detail.

  5. 214 Transportation Carrier Shipment Status Message

    From Dunavant to you

    Typically reports pickup, location updates and delivery.

  6. 997 Functional Acknowledgment

    Both directions

    Typically confirms that each file was received and could be read.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your Dunavant program

Each request goes to an ECOM EDI specialist with Dunavant's name attached, so the reply starts from your program.

  • Review Dunavant's requirements

    Send us Dunavant's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Dunavant to your ERP

    Tenders, status and freight invoices in and out of the TMS, ERP and finance systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Dunavant document, then go live with monitoring from the first file.

    Plan testing and certification

Dunavant integration FAQs

Does Dunavant use EDI with shippers?

Forwarders and customs providers commonly exchange EDI or APIs with shippers. This page does not include Dunavant's requirements.

Does ECOM file customs entries?

ECOM connects and monitors the documents and data between your systems and your providers. Customs filing is done by licensed parties.

Which EDI documents are typical for a freight forwarder or customs provider?

Typical documents are 300, 301, 315, 310, 214, 997. That is general practice, not Dunavant's published list.

How does onboarding with Dunavant usually work?

Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on Dunavant's requirements, test cycles and your ERP.

Does this guide mean Dunavant endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by Dunavant.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. Dunavant sets its own requirements and can change them at any time; your Dunavant implementation guide, supplier portal or account contact is the authoritative source for your program.

  • ASC X12: transaction set reference (standards body) Standards reference
  • Dunavant: company description Background, not checked against a company source The one-sentence description of Dunavant comes from general public knowledge and was not checked against Dunavant's own website for this page.
  • Dunavant: no company document read Background, not checked against a company source No Dunavant supplier, customer or integration document was read for this page. Everything shown is typical practice for this type of company.

Request Dunavant integration assistance

Tell us about your Dunavant program, documents and ERP. We will outline the connection, mapping and testing plan.