Third-Party Logistics integration

Murphy Logistics EDI and API integration

Murphy Logistics' company fact sheet describes EDI and API connectivity for customers. Typical documents, workflows, onboarding and how ECOM helps.

At a glance

Murphy Logistics integration, in three pictures

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

Illustration of a warehouse with dock doors and stacked pallets, representing the third-party logistics industry that Murphy Logistics operates in.
Industry. Third-Party Logistics: where Murphy Logistics operates.
Workflow diagram: your ERP and warehouse systems exchange documents with Murphy Logistics through ECOM. You send 940, 856; you receive 945, 944, 846; 997 acknowledgments go both ways. Your systems ERP · WMS · finance ECOM integration map · validate · connect · monitor Murphy Logistics 940 856 940 856 945 944 846 945 944 846 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 Shipping orders 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 Murphy Logistics

Tell us which documents you exchange with Murphy Logistics, 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 Murphy Logistics.

  • Review of Murphy Logistics' requirements with you, once you have them
  • EDI and API integration with your ERP and warehouse 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
Murphy Logistics

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 Murphy Logistics integration fits your systems

Your systemsERP, WMS and accounting
ECOMMapping, validation, connectivity and monitoringAS2, SFTP or VAN · Provider API
Murphy LogisticsIts program, documents and requirements
  1. ConfirmConfirm your Murphy Logistics 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 Murphy Logistics integration

Who this is for: Brands, manufacturers, distributors and retailers that store or fulfill through Murphy Logistics, and their order, inventory and finance teams.

Scope: Murphy Logistics's own capability statement is cited; everything else on this page is typical practice, confirmed with Murphy Logistics during onboarding.

Murphy Logistics is a warehousing and logistics provider with a workforce of more than 500 people according to its company fact sheet.

Murphy Logistics' company fact sheet describes EDI and API connectivity for customers. This guide uses that as its documented starting point and treats the rest as typical practice for a warehousing and logistics provider; the exact documents, versions and test steps for your program are confirmed with Murphy Logistics during onboarding.

Typical exchanges with a warehousing provider move shipping orders out, shipping advice back, inbound notices and receipt advice in, and inventory data in both directions. The integration work is keeping those records in step between your ERP and the facility, whatever transport carries them.

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

Business scenarios

Where Murphy Logistics integration gets complicated

Typical requirements—confirm with your trading partner.

Mid-size provider, enterprise-grade data

A provider with a large workforce serves many clients at once, so each client needs its own mapping, test cycle and monitoring without disturbing the others.

How ECOM helps: ECOM builds your connection to Murphy Logistics as its own mapped and monitored flow, with testing to acceptance before orders move.

What you gain: A client-specific integration that does not depend on manual re-keying at the facility.

Peak season volumes

Peaks stress order latency and carrier cut-offs.

How ECOM helps: ECOM runs the connection as a monitored service and watches queues and acknowledgments through busy periods, so a spike does not leave documents waiting.

What you gain: Busy periods run on the same process, without manual catch-up.

Onboarding a new client

Each client brings its own documents, item data and rules to the warehouse system.

How ECOM helps: ECOM runs onboarding as a project: we confirm Murphy Logistics's requirements with you, map the documents, build the connection and run test cycles until Murphy Logistics accepts them.

What you gain: A shorter, more predictable path to the first accepted live document.

Ship notices and labels

Outbound shipments to retailers need accurate ship notices and compliant carton or pallet labels built from warehouse data.

How ECOM helps: ECOM aligns ship-notice content with the warehouse confirmation and flags mismatches before the notice leaves.

What you gain: Fewer retailer compliance charges and rejected deliveries.

Workflows

Typical Murphy Logistics business workflows

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

Outbound order

  1. 1Send 940 shipping order
  2. 2Warehouse picks and packs
  3. 3Receive 945 shipping advice
  4. 4Update ERP and invoice

Inbound receipt

  1. 1Send inbound notice
  2. 2Warehouse receives goods
  3. 3Receive 944 receipt advice
  4. 4Update inventory

Documents and APIs

Murphy Logistics documents by program

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

DocumentNameDirectionProgramStatusPurpose
940 Warehouse Shipping Order To Murphy Logistics Not stated General guidance Typically tells a warehouse what to pick, pack and ship.
945 Warehouse Shipping Advice From Murphy Logistics Not stated General guidance Typically confirms what the warehouse shipped.
944 Warehouse Stock Transfer Receipt Advice From Murphy Logistics Not stated General guidance Typically confirms what the warehouse received into stock.
846 Inventory Inquiry/Advice From Murphy Logistics Not stated General guidance Typically shares inventory positions or availability between the two sides.
856 Ship Notice/Manifest To Murphy Logistics Not stated General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
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

    Warehouse and fulfillment providers commonly exchange EDI with clients over AS2, SFTP or a value-added network.

    General guidance

  • Provider API

    Many providers also offer order, inventory and shipment APIs next to EDI.

    General guidance

Challenges

Common integration challenges

  • Shipment confirmation

    Shipping advice has to match what is invoiced and what the customer receives. Confirm how it applies with Murphy Logistics.

  • Multiple clients and sites

    Rules differ by client and facility, so the same document can need different handling. Confirm how it applies with Murphy Logistics.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set with the provider, and ECOM works from them during mapping and testing. Confirm how it applies with Murphy Logistics.

  • Order latency

    Late orders miss carrier cut-offs, so how fast documents move between your ERP and the facility matters. Confirm how it applies with Murphy Logistics.

Automation options for Murphy Logistics shippers

Four ways to automate. One foundation.

ECOM helps you automate the exchange, connect it to your systems, and see what needs action. Murphy Logistics 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

Zero Trust for EDI and file transfer

Zero Trust EDI and MFT for your Murphy Logistics connection

Exchanges with Murphy Logistics move business documents between your systems and an outside party. A Zero Trust design assumes no connection, file or user is safe by default.

  • Authentication

    Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.

    Business outcome: A lost or reused credential affects one partner, not all of them.

  • Least privilege

    Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.

    Business outcome: A mistake or compromise in one account stays limited to what that account could reach.

  • Isolation

    Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.

    Business outcome: Outside connections do not land directly on your internal systems.

  • Encryption

    Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.

    Business outcome: Less exposure if a file is intercepted or a file store is reached.

  • Certificate and key management

    Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.

    Business outcome: Fewer outages caused by an expired certificate or key.

  • Monitoring and access controls

    Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.

    Business outcome: Late, missing or failed files are noticed early, before they hold up payment, shipping or reporting.

  • Audit trail

    Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.

    Business outcome: You can answer who sent what and when, for your own audits and partner reviews.

What this means for your data

Partner access

Each trading partner connects with its own identity and a limited scope, and any connection can be reviewed or removed on its own.

File and document handling

Documents are verified when they arrive and every transfer is logged.

Exceptions

Late, missing or rejected files raise an alert and go to a named owner.

Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. Murphy Logistics may set its own security requirements, which come first.

General EDI flow

How EDI with Murphy Logistics typically works

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

  1. 940 Warehouse Shipping Order

    From you to Murphy Logistics

    Typically tells a warehouse what to pick, pack and ship.

  2. 945 Warehouse Shipping Advice

    From Murphy Logistics to you

    Typically confirms what the warehouse shipped.

  3. 944 Warehouse Stock Transfer Receipt Advice

    From Murphy Logistics to you

    Typically confirms what the warehouse received into stock.

  4. 846 Inventory Inquiry/Advice

    From Murphy Logistics to you

    Typically shares inventory positions or availability between the two sides.

  5. 856 Ship Notice/Manifest

    From you to Murphy Logistics

    Typically tells the receiver what is on each shipment, often with carton or pallet label details.

  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 Murphy Logistics program

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

  • Review Murphy Logistics' requirements

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

    Request a requirements review
  • Connect Murphy Logistics to your ERP

    Warehouse orders, receipts, shipments and inventory in and out of the ERP and warehouse systems you already run.

    Discuss ERP integration
  • Testing and certification

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

    Plan testing and certification

Murphy Logistics integration FAQs

What connectivity does Murphy Logistics describe?

Murphy Logistics' fact sheet describes EDI and API connectivity. The documents, transports and test steps for your account are not set out publicly and are confirmed with Murphy Logistics during onboarding.

Which EDI documents are typical for a warehousing and logistics provider?

940, 945, 944, 846, 856, 997 are the documents commonly exchanged in this kind of relationship. That is general practice; Murphy Logistics's own program defines which of them apply to you.

How does onboarding with Murphy Logistics 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 Murphy Logistics's requirements, test cycles and your ERP.

Does this guide mean Murphy Logistics endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by Murphy Logistics, and it does not describe Murphy Logistics as an ECOM customer.

Sources and accuracy

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

Request Murphy Logistics integration assistance

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