Manufacturing · Building Materials and Architectural Products

EDI and API Integration for Asphalt and Pavement Product Manufacturers

Asphalt and pavement producers sell by the ton to contractors and public agencies, delivered hot from the plant against delivery tickets. ECOM connects orders, tickets, scheduling messages and invoices to your ERP so tonnage billed matches tonnage delivered.

View all manufacturing industries

What this covers

Products and business models in asphalt and pavement product

Products

  • Hot-mix asphalt
  • Asphalt binders and emulsions
  • Aggregates and base materials
  • Sealants and pavement maintenance products

Business models

  • Producers supplying contractors
  • Public agency contracts
  • Bulk binder and emulsion supply

Scenarios

Where asphalt and pavement product 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.

  • Ticket reconciliation

    The problem
    Billing depends on tickets with weights, and disputes arise from mismatches.
    How ECOM helps
    ECOM maps ticket weights into the ERP, 856 and 810 so tickets and invoices can be compared.
    What you gain
    Weight mismatches are reviewed before billing.

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

  • Time-sensitive hot loads

    The problem
    Hot mix must be delivered within a window.
    How ECOM helps
    ECOM carries job and delivery window references on orders and tickets and can flag a late dispatch.
    What you gain
    Hot-mix deliveries follow the job window.

    Talk to an EDI/API Expert about time-sensitive hot loads Share a sample 850 Purchase Order and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.

  • Public contracts and pay applications

    The problem
    Public agency work adds contract and reporting references.
    How ECOM helps
    ECOM carries contract and pay-application references through orders, tickets and invoices.
    What you gain
    Public-agency billing references stay on the documents.

    Talk to an EDI/API Expert about public contracts and pay applications Share a sample 850 Purchase Order 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 asphalt and pavement product manufacturers

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

Paving contractors
Order by job and day.
Public agencies
Buy under contracts.
Aggregate and binder suppliers
Supply materials.
Haulers and truck fleets
Deliver loads.
Terminals and rail
Move binder and aggregate.

Typical workflow

Where ECOM connects your systems and trading partners

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

  1. Contractor or agency→Your plant and ERP 850 Purchase Order Quantity in tons by job, date and time.
  2. Contractor or agency→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
  3. Your plant and ERP→Contractor or agency 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
  4. Your plant and ERP→Contractor or agency 856 Advance Ship Notice Tonnage and ticket references per delivery.
  5. Your plant and ERP→Contractor or agency 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
  6. Your plant and ERP→Binder and aggregate supplier 850 Purchase Order Purchase orders for binder and aggregate with quantities and requested delivery dates.
  7. Binder and aggregate supplier→Your plant and ERP 856 Advance Ship Notice Binder and aggregate deliveries with tonnage and ticket references, used to plan receiving and reconcile supplier invoices.
  8. Binder and aggregate supplier→Your plant and ERP 810 Invoice The supplier’s invoice for binder and aggregate, matched to the order and the receipt.

The diagram draws the exchanges between the lanes shown. Motor-carrier and warehouse documents (204, 990) are listed in the table below with the direction each travels.

  1. Daily orders

    Orders (850) and changes (860) by job.

  2. Load and ticket

    Plant loading produces tickets.

  3. Ship notice from tickets

    The 856 reports tonnage.

  4. Invoice from tickets

    The 810 follows.

  5. Material supply

    Binder and aggregate orders (850) and notices (856).

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 asphalt and pavement product manufacturers
850 Purchase Order You receive Quantity in tons by job, date and time.
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.
856 Advance Ship Notice You send Tonnage and ticket references per delivery.
810 Invoice You send Bills for what was shipped, tied to the order and the ship notice.
850 Purchase Order (supplier side) You send Purchase orders for binder and aggregate with quantities and requested delivery dates.
856 Advance Ship Notice (supplier side) You receive Binder and aggregate deliveries with tonnage and ticket references, used to plan receiving and reconcile supplier invoices.
810 Invoice (supplier side) You receive The supplier’s invoice for binder and aggregate, matched to the order and the receipt.

Other exchanges you may meet

  • Plant scale and ticketing systems
  • Agency contract and reporting portals

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

Tickets, tonnage and contracts

Every delivery has a ticket. Tonnage on the ticket drives billing and agency reporting, so order, ticket and invoice need to link with the job and contract reference.

  • Dimensions and units of measure

    Products sell by the piece, box, square foot, linear foot, pallet or bundle. Orders, ship notices and invoices must agree on units and conversions, or quantities and prices disagree.

  • Jobsite and yard delivery

    Deliveries go to branches, yards and jobsites, sometimes with delivery appointments or special equipment. Ship-to detail and carrier information are part of the exchange.

  • Distributor orders

    Most volume moves through distributors, dealers and home centers that send their own orders, changes and inventory or sales data.

Connected systems

Systems that send and receive this data

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

  • ERP
  • Plant scale and ticketing
  • Dispatch
  • Agency 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 contractor or agency, 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 plant scale and ticketing 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 asphalt and pavement product manufacturers

Illustrative exceptions and example handling that depends on configuration, not live data
ExceptionExample handling, once configured
Ticket weight differs from invoiceA comparison of ticket weight with the 810 can hold the invoice for review before billing.
Job reference missingA required-field check can hold the order for dispatch review.

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

Can scale tickets feed invoices?

Ticket data from your scale system can flow into the ERP so invoices follow delivered tonnage.

Does ECOM support public agency portals?

Agency systems vary. ECOM scopes each one as an additional connection alongside your contractor accounts.

How are units of measure and conversions kept consistent?

Item and unit conversions are agreed during mapping, so a quantity ordered in boxes can be shipped and invoiced in the unit the trading partner expects. They are part of the partner’s implementation guide and tested before go-live.

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 asphalt and pavement product 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.