Skip to main content

Purolator EDI: requirements and onboarding

Connect Purolator Canadian shipping and accounts-payable workflows with a clear boundary between E-Ship EDI and E-Ship Web Services. Choose the needed invoice, status and shipping functions instead of assuming every interface is one package.

Quick answers

Can SignalEDI help me connect to Purolator?
SignalEDI helps prepare mappings, sample validation, and the workflow required for your Purolator program. Scope is confirmed during setup. Production connection requires the applicable partner approval; this guide is not evidence of a live connection or certification.
What determines the Purolator onboarding timeline?
The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule. Agree the schedule after requirements and testing scope are confirmed. This is not a guaranteed go-live date.
Which ERP systems can I use for Purolator?
Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
Review integration scope

Plan the integration workflow

SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.

  1. 1. Your business system

    Identify the source records, system edition, data owner, and allowed access.

  2. 2. SignalEDI preparation

    Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.

  3. 3. Partner testing and approval

    Complete the partner-controlled tests and retain permission before enabling live exchange.

Conceptual workflow only. A diagram or catalog listing does not establish certification or an active production connection.

Build your onboarding checklist

Download the onboarding worksheet (text)

Public sources reviewed 2026-11-09

What the public record confirms

  • Purolator's public E-Ship EDI page lists X12 version 4010 invoice 210, shipment status 214, remittance advice 820 and acknowledgement 997 capabilities. It also lists proprietary formats with different document coverage. These are offered capabilities, not a requirement that every customer implement all four transactions.
  • The E-Ship EDI page identifies SFTP and AS2 communication options. The selected route, document details and onboarding arrangement still need confirmation for the account; a supported transport is not proof that a particular integration is connected.
  • Purolator separately describes E-Ship Web Services for functions such as label creation, estimates and tracking within business systems. Its billing support materials distinguish API shipment support from invoice and billing questions.
  • Sources were reviewed on November 9, 2026. Private account specifications and production acceptance were not accessed. This Canadian guide does not assume that Purolator International or a freight-specific workflow shares the same setup, and it does not claim SignalEDI certification, partnership or an existing live connection.

Document and workflow scope

Use the cited source boundaries below, then confirm your current assigned program: Exact specifications come from your partner packet. Treat this as a planning checklist, not a substitute for the current implementation guide.

  • Canadian account and service record: identify the billed entity, shipping locations, account scope and relevant courier or freight service. Record which operational and financial teams own the project, especially when a separate cross-border provider or business unit is involved.
  • EDI invoice and status specification: obtain the assigned layout, version and business rules for the selected document types. Define how account, invoice, shipment and tracking references connect to the ERP and order-management system without relying on customer order number alone.
  • Remittance and acknowledgement scope: confirm whether these functions belong in the chosen implementation and how they relate to the accounting process. Keep acknowledgement of electronic data separate from approval of a charge, payment execution and proof that a parcel has arrived.
  • Shipping API workflow: if labels, estimates or other execution functions are needed, document their interface separately. Establish the connection between the shipping record and later carrier charges, including changed package details and orders with more than one parcel.

Connectivity and testing requirements

Connectivity

Confirm whether the current Purolator program uses AS2, SFTP, VAN, or another named transport.

Onboarding window

Not verified on this page.

Certification focus

The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule.

  • Purolator's public E-Ship EDI page lists X12 version 4010 invoice 210, shipment status 214, remittance advice 820 and acknowledgement 997 capabilities. It also lists proprietary formats with different document coverage. These are offered capabilities, not a requirement that every customer implement all four transactions.
  • The E-Ship EDI page identifies SFTP and AS2 communication options. The selected route, document details and onboarding arrangement still need confirmation for the account; a supported transport is not proof that a particular integration is connected.
  • Purolator separately describes E-Ship Web Services for functions such as label creation, estimates and tracking within business systems. Its billing support materials distinguish API shipment support from invoice and billing questions.
  • Sources were reviewed on November 9, 2026. Private account specifications and production acceptance were not accessed. This Canadian guide does not assume that Purolator International or a freight-specific workflow shares the same setup, and it does not claim SignalEDI certification, partnership or an existing live connection.

Questions to resolve from the current buyer packet

  • Choose EDI billing, shipment visibility, shipping execution or a defined combination. Assign a business outcome to each interface so that a completed invoice import is not mistaken for a completed shipping integration.
  • Request current account-specific technical materials and confirm the document subset. Record whether X12 or a proprietary layout is selected, and do not assume those formats have identical fields or acknowledgement behavior.
  • Review the relationship between shipment, parcel, customer order and invoice identifiers. Explain how a multi-piece shipment and charges received after delivery will be matched without discarding important references.
  • Confirm service, account, location and currency mappings with operations and finance. Keep values grounded in the actual account and invoice rather than inheriting another carrier's charge codes or shipping-service names.
  • Define how staff handle an invoice dispute, missing status event, rejected document and uncertain submission. Preserve the evidence appropriate to each problem and use the corresponding support route.
  • Retain the agreed transport setup, safe sample results and actual account acceptance independently. Complete operational monitoring and recovery checks before declaring any Purolator workflow ready for live use.

How SignalEDI handles it

  • Prepare a versioned mapping and testing checklist from the requirements you provide.
  • Validate synthetic or scrubbed samples before partner testing.
  • Review acknowledgement and exception handling before production cutover. Scope is confirmed during setup.

Review mapping and validation in the self-serve workspace before partner testing. Developer quickstart

Pricing

SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.

Compare current plans

Practice the workflow before partner testing

These are recommended preparation exercises, not additional partner requirements or a customer success story. Use synthetic or scrubbed samples and adapt each exercise to the current guide assigned to your program.

Select only the agreed document subset

Create a scope checklist for the actual project and mark each proposed invoice, status, remittance or acknowledgement flow as required, optional or unconfirmed. Compare the selected X12 or proprietary format with the assigned guide. Include one unsupported assumption to verify that it cannot pass unnoticed.

What a useful result looks like

The implementation has an explicit document and format boundary. An advertised capability does not automatically become an obligation or account entitlement. Missing technical detail is tracked for confirmation rather than copied from another carrier, format or customer relationship.

Reconcile multiple parcels to one order

Prepare a synthetic customer order fulfilled using several parcels, then introduce carrier status and invoice records with different arrival times. Trace the order, shipment, parcel and billing references through the proposed data model. Include a parcel reference that does not yet match any known shipment.

What a useful result looks like

The system retains the individual parcel histories while preserving their relationship to the customer order. An unmatched record becomes an actionable exception, not a discarded event. Accounting can reconcile charges without assuming that one order always means one tracking number or one invoice line.

Handle repeated status and billing input

Replay a synthetic status event and a previously imported invoice, then provide a genuine later event and an adjustment. Review how duplicate detection distinguishes repeated delivery from new business information. Preserve the source timestamps and identifiers so the result can be explained.

What a useful result looks like

The repeat does not create a second financial posting or duplicate customer notification. New events and adjustments remain visible even when they reference an existing shipment. The system's definition of duplicate is based on the assigned interface and business identity rather than a broad match on tracking number.

Recover a connection interruption

Simulate an interrupted exchange using the selected transport's agreed behavior. Include one known rejection and one submission whose outcome cannot yet be determined. Document how operators inspect status, preserve files and resume processing without exposing account access material.

What a useful result looks like

Recovery distinguishes confirmed failure from uncertainty and does not blindly resend accepted work. A restored connection does not by itself close missing invoices or status gaps. The evidence identifies what was tested locally and what still requires Purolator's account-specific acceptance before production.

Common integration questions

Can I keep my existing ERP or accounting system?
Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
Does validation mean my partner has approved production?
No. Passing document validation checks your sample against the configured rules. Partner certification, enrollment, transport approval, and permission to send live documents are separate steps controlled by the applicable partner program. Use synthetic or scrubbed samples while preparing and keep the approval evidence before switching to production.
Where can I see SignalEDI pricing?
SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.

Authoritative sources

Source review date: 2026-11-09. Links below establish only the facts described; your current buyer-issued materials remain authoritative for program-specific technical requirements.

Purolator questions

Which EDI documents does Purolator publicly support?
The official E-Ship EDI page lists invoice, shipment-status, remittance and acknowledgement options, with format-specific coverage. Use that as a starting point for selecting the functions your account needs. Obtain the actual mapping guide and onboarding instructions before treating any published capability as a mandatory document or an enabled production service.
Is Purolator E-Ship EDI the same as E-Ship Web Services?
No. The public materials describe different integration offerings. Decide whether the business needs accounting data, status visibility, shipping execution or several of those outcomes, then scope the appropriate interfaces. Shared shipment references can support reconciliation, but a working billing feed does not prove that label creation or other API operations have been configured.
What should a Purolator integration do when invoice and shipment data disagree?
Keep the original records and determine which reference, charge or event differs. Do not overwrite a shipment with invoice data merely to make totals match, and do not treat a tracking update as approval of a disputed charge. Use the account's business and support processes to resolve the discrepancy with a traceable outcome.

Related EDI resources

Prepare your side for partner testing

SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.

Connect now

Topics: Purolator EDI requirements · Purolator supplier EDI · Purolator EDI CA

© 2026 SignalEDI Inc. All rights reserved.