Manufacturing · Transportation, Aerospace and Defense

EDI and API Integration for Shipping Container and Intermodal Equipment Manufacturers

Shipping container and intermodal equipment makers build containers, chassis and trailers for leasing companies, ocean carriers and logistics operators, delivered in batches with unit-level identification. ECOM connects batch orders, unit-number lists, delivery and invoices to your ERP.

View all manufacturing industries

What this covers

Products and business models in shipping container and intermodal equipment

Products

  • Dry, refrigerated and specialty containers
  • Chassis and intermodal trailers
  • Tank containers and modified units
  • Parts, repair and refurbishment

Business models

  • Manufacturers selling to leasing companies and carriers
  • Depot and conversion businesses
  • Intermodal equipment pools

Scenarios

Where shipping container and intermodal equipment manufacturers lose time and margin

Recurring problems for this kind of business, how ECOM connects the systems and documents involved, and what you gain. Bring your own example and we will work through it with you.

  • Unit-number identification

    The problem
    Each container has a unique unit number that appears in delivery and acceptance records.
    How ECOM helps
    ECOM carries unit numbers by delivery batch onto the 856 and delivery list and holds a list with a missing number for review.
    What you gain
    The customer receives a complete record of units delivered.

    Talk to an EDI/API Expert about unit-number identification Share a sample 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Batch production and delivery

    The problem
    Orders are produced and delivered in batches to depots and ports.
    How ECOM helps
    ECOM maps batch orders with specification, quantity and delivery depot into the ERP and carries delivery events (214).
    What you gain
    Batches are tracked to the depot or port.

    Talk to an EDI/API Expert about batch production and delivery Share a sample 850 Purchase Order, 860 Purchase Order Change Request and 214 Transportation Carrier Shipment Status Message, or describe what goes wrong, and we will show how it would map to your ERP.

  • Inspection and acceptance

    The problem
    Customers inspect and accept units against the order specification, and invoicing depends on which units were accepted.
    How ECOM helps
    ECOM compares accepted units (861) with delivered units and holds the invoice for review when they differ.
    What you gain
    Invoicing follows the units the customer accepted, not the units delivered.

    Talk to an EDI/API Expert about inspection and acceptance Share a sample 861 Receiving Advice/Acceptance Certificate and 810 Invoice, or describe what goes wrong, and we will show how it would map to your ERP.

Who you connect with

Trading relationships for shipping container and intermodal equipment manufacturers

Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.

Container leasing companies
Order batches.
Ocean carriers
Order equipment.
Intermodal and logistics operators
Order chassis and trailers.
Steel, floor and component suppliers
Supply materials.
Depots and delivery partners
Receive units.

Typical workflow

Where ECOM connects your systems and trading partners

The pattern below is typical for shipping container and intermodal equipment manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.

  1. Leasing company or carrier→Your plant and ERP 850 Purchase Order Batch quantity, specification and delivery depot.
  2. Leasing company or carrier→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  3. Your plant and ERP→Leasing company or carrier 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Depot or carrier 204 Motor Carrier Load Tender Tenders a truck shipment to a motor carrier.
  5. Depot or carrier→Your plant and ERP 990 Response to a Load Tender The motor carrier’s acceptance or decline of the tender.
  6. Depot or carrier→Your plant and ERP 214 Transportation Carrier Shipment Status Message Shipment status events from the motor carrier.
  7. Your plant and ERP→Leasing company or carrier 856 Advance Ship Notice Unit numbers per delivery batch.
  8. Your plant and ERP→Leasing company or carrier 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  9. Leasing company or carrier→Your plant and ERP 861 Receiving Advice/Acceptance Certificate Customer acceptance record.
  1. Take batch orders

    Orders (850) and changes (860) carry specification, quantity and delivery depot.

  2. Produce and number units

    Unit numbers are assigned and recorded during production and inspection.

  3. Notify delivery

    The 856 or delivery list reports unit numbers by batch.

  4. Track delivery

    Status events (214) show arrival at the depot or port.

  5. Invoice by batch

    The 810 follows acceptance (861).

EDI and API exchanges

The documents behind the workflow

X12 transaction sets typical for this workflow, with what each carries here. Select a code for the full transaction reference.

DocumentDirectionWhat it carries for shipping container and intermodal equipment manufacturers
850 Purchase Order You receive Batch quantity, specification and delivery depot.
860 Purchase Order Change Request You receive Changes to open orders: quantities, dates or cancellations.
855 Purchase Order Acknowledgment You send The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
204 Motor Carrier Load Tender You send Tenders a truck shipment to a motor carrier.
990 Response to a Load Tender You receive The motor carrier’s acceptance or decline of the tender.
214 Transportation Carrier Shipment Status Message You receive Shipment status events from the motor carrier.
856 Advance Ship Notice You send Unit numbers per delivery batch.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
861 Receiving Advice/Acceptance Certificate You receive Customer acceptance record.

Other exchanges you may meet

  • Equipment interchange and ocean-carrier messages
  • Depot systems

Where a trading partner offers an API, a portal or file exchange instead of EDI, ECOM scopes that connection alongside the EDI ones. Functional acknowledgments (997 or 999) report validation results, including rejection; they do not prove business acceptance or ERP posting. Which acknowledgments and business responses each partner expects is confirmed with that partner.

Operational detail

Unit numbers, batches and acceptance

Unit numbers connect a container’s production record, delivery and acceptance. A mismatch between the delivered list and the accepted list holds up invoicing, and batches are delivered to depots and ports.

  • Long-lead programs and traceability

    Aerospace, rail and marine programs run on long lead times, controlled parts and traceability requirements that come from the customer or program.

  • Fleet orders and delivery to depots

    Containers, chassis and intermodal equipment are ordered in batches for fleets and delivered to depots, terminals or ports, so ship notices need to identify units and delivery locations.

Connected systems

Systems that send and receive this data

Documents are only useful when they reach the systems that run the business.

  • ERP
  • Production and inspection systems
  • Depot systems
  • Customer portals

Onboarding and monitoring

From first requirement to daily exception handling

  1. Confirm the requirement

    Obtain each partner's implementation guide or specification, for example from your leasing company or carrier, and agree which documents, versions and data are in scope.

  2. Map to your systems

    Map each document to the fields in your ERP and production and inspection systems so the data posts without re-keying.

  3. Test with the partner

    Exchange test documents and review the results with the partner before go-live, including changes, cancellations and error cases, not only the simple order.

  4. Validate, acknowledge and monitor

    A 997 or 999 reports the validation result of the document as received, including rejection; it does not show that the business accepted the content or that your ERP posted it. Business responses are separate: an 855 for orders, an 824 for application errors. Monitoring can show what is late, missing or rejected, once it is set up with you.

  5. Resolve exceptions

    Which failures and late documents are watched, who is alerted and how each is resolved are agreed during onboarding. Rejected or unacknowledged documents can then go to the people who can fix them, with the document and the reason in view.

Example exceptions for shipping container and intermodal equipment manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Unit number missing from a delivery listThe list can be held for review so the customer receives a complete record of units delivered.
Accepted units fewer than delivered unitsThe difference can be flagged for review so invoicing waits for resolution.

Illustrative examples of exceptions a team in this industry may need to review. Each check compares data from your ERP, WMS, trading partner documents or scans, where those are available. Which conditions are checked, who is alerted and what happens next are configured with you during onboarding. This is not a screenshot of a live system or a list of built-in checks.

How ECOM helps

ECOM products and services that apply

Each partner connects in the way it can support. These products cover the connections and visibility manufacturers need most.

  • PRISM-EDI

    Exchange of schedules, orders, ship notices and invoices with customers and suppliers in X12 or EDIFACT, translated to and from your ERP.

  • PRISM-WebEDI

    Browser-based purchase orders, acknowledgments, ship notices and invoices for suppliers without EDI systems.

  • PRISM-SmartConvert

    Supplier confirmations, invoices and customer orders that arrive as PDFs, emails or scans converted into ERP-ready data.

  • PRISM-SCV

    Monitoring of transactions and exceptions across customer and supplier documents.

Frequently asked questions

Does ECOM support ocean-carrier equipment messages?

Where customers use EDIFACT or other equipment messages, ECOM scopes them. The ocean freight page covers shipping documents for cargo.

Can unit lists be sent in bulk?

Yes, in the format the customer allows, mapped from your production and delivery records.

Do you need our trading partner's implementation guide to start?

It helps, but you can start without one. Tell us who you trade with and which systems you run, and we will help obtain and review each partner's requirements. The guide, not this page, decides the exact documents, versions and rules for that partner.

Talk to an EDI/API expert about shipping container and intermodal equipment manufacturers

Share your trading partners, your ERP, a sample document or the problem that keeps recurring. A completed specification is not needed: a partner guide, a rejected document or a description of the issue is enough to start.