Skip to main content

Loblaw Companies EDI: requirements and onboarding

Prepare Loblaw Companies orders around the actual delivery responsibility, portal status and shipment evidence, so an electronic ASN does not hide an unresolved pickup or late-delivery exception.

Quick answers

Can SignalEDI help me connect to Loblaw Companies?
SignalEDI helps prepare mappings, sample validation, and the workflow required for your Loblaw Companies 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 Loblaw Companies 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 Loblaw Companies?
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

  • Loblaw's public Supply Chain Vendor Portal announces that sign-in moved to the Loblaw Supplier Portal on October 19, 2026. Access to a supplier account and access to its applications are separate administrator-managed concerns; a working login does not establish EDI production approval.
  • The publicly linked PO Updates guide identifies itself as V1.0 dated February 17, 2026, while the Help page lists an April 7 update. It separates Loblaw Pickup from Vendor Delivered orders, with different readiness and shipping actions. Check both the current link and the document's internal version before using screenshots.
  • For vendor-delivered orders, an EDI ASN can set In Transit, but late information still needs the portal update described in the guide. Pickup readiness records pallet floor spaces separately from pallet count. These operational distinctions do not establish a complete transaction-set or transport specification.
  • Treat the following exercises as supplier preparation, not an assertion that SignalEDI has a live Loblaw Companies connection, certification or authority to amend orders. Your assigned technical packet and current transportation instructions control the implementation.

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.

  • Purchase orders: obtain the current Canadian program guide, preserve the complete order identifier and associate each line with its delivery type, ship location and destination. A single customer name is not enough to route an order.
  • Shipment notices: confirm the ASN format, packaging hierarchy, receiving destination, shipment reference and correction rules. Link the outbound message to the physical load rather than generating it solely from ordered quantities.
  • Portal readiness and exceptions: maintain a separate worksheet for pickup readiness, changed load details, late deliveries and missed pickups. Identify which actions are automated and which still require an authorized operator.
  • Invoices and acknowledgements: ask for the current billing map and acceptance semantics. Do not infer invoice acceptance from an In Transit display, a transport receipt or a successfully submitted portal form.

Connectivity and testing requirements

Connectivity

Confirm whether the current Loblaw Companies 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.

  • Loblaw's public Supply Chain Vendor Portal announces that sign-in moved to the Loblaw Supplier Portal on October 19, 2026. Access to a supplier account and access to its applications are separate administrator-managed concerns; a working login does not establish EDI production approval.
  • The publicly linked PO Updates guide identifies itself as V1.0 dated February 17, 2026, while the Help page lists an April 7 update. It separates Loblaw Pickup from Vendor Delivered orders, with different readiness and shipping actions. Check both the current link and the document's internal version before using screenshots.
  • For vendor-delivered orders, an EDI ASN can set In Transit, but late information still needs the portal update described in the guide. Pickup readiness records pallet floor spaces separately from pallet count. These operational distinctions do not establish a complete transaction-set or transport specification.
  • Treat the following exercises as supplier preparation, not an assertion that SignalEDI has a live Loblaw Companies connection, certification or authority to amend orders. Your assigned technical packet and current transportation instructions control the implementation.

Questions to resolve from the current buyer packet

  • Classify every lane before mapping: supplier-arranged delivery, Loblaw-arranged pickup, or a specifically agreed cross-dock arrangement. Have logistics confirm the classification against the order rather than copying a default from the supplier master.
  • Reconcile supplier number, ship-location ID, DC, purchase-order number and line identifiers across commercial, warehouse and EDI systems. Preserve leading zeroes in imports and exports; spreadsheet formatting must not change business identity.
  • Assign separate owners for physical pallets, trailer floor space, pickup windows and late reasons. Record the source of each value and who can correct it when the warehouse changes a load after the first readiness update.
  • Document a status-check procedure before repeating a submission. The public guide describes display synchronization edge cases, so a visual status change alone should not trigger duplicate transportation instructions or a replacement ASN.
  • Retain the guide revision, permitted user role, safe sample evidence and unresolved questions together. Agree the production start with the assigned program, including who handles exceptions when the primary logistics contact is unavailable.

EDI requirements quick reference

Document codes and the planning checklist for this partner also live on the Loblaw Companies EDI requirements page. That page stays separate from this onboarding profile.

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.

Separate pickup and vendor-delivery lanes

Prepare two synthetic orders for the same product and destination, one assigned to supplier delivery and one to Loblaw pickup. Trace the planned actions from order intake to dispatch. Add a cross-dock case only if it belongs to your agreement, then ask the warehouse and transportation owners to explain which readiness event they use.

What a useful result looks like

The planning record distinguishes who moves the goods and which event can be reported. An ASN created for the vendor-delivery example does not automatically mark the pickup example ready. Each unresolved instruction is attached to its lane rather than hidden in a company-wide default.

Reconcile stacked pallets

Create a harmless loading example with stacked and unstacked pallets. Calculate physical pallet count and occupied trailer floor space independently, then compare both with the order's ship location and collection window. Change the stack arrangement after the first calculation and identify every downstream record that would need review.

What a useful result looks like

The team can explain the difference between the two measures and can revise the load without losing the original calculation. Invalid or ambiguous loading information is held for review. This is an internal consistency exercise, not a claim that a live portal update has been accepted.

Record delay after an ASN

Walk through a vendor-delivered shipment that has a valid outbound notice and later becomes delayed in transit. Record the original shipping event, the new estimate, the reason and the person responsible for the required operational update. Keep test data outside production and use the current guide to confirm the action available for that status.

What a useful result looks like

The exception remains visible despite successful electronic transmission. Staff do not assume that the original ASN describes the latest transport situation, and a late update is not confused with a new physical shipment or a new invoice.

Investigate an unexpected portal status

Present the operations owner with a hypothetical order whose display changes after a readiness update. Before repeating the action, compare the original confirmation, portal history and authorized transport records. Record whether the evidence indicates synchronization, a genuine cancellation or a change requiring escalation, without assuming every status anomaly has the same cause.

What a useful result looks like

The operator has a documented decision path and enough identifiers to investigate. No duplicate pickup or cancellation is issued merely to make a screen look right. The retained evidence distinguishes the visible status, the confirmed business outcome and anything still unknown.

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.

Loblaw Companies questions

Does a Loblaw Companies ASN replace every portal update?
No. The public guide makes a narrower distinction for vendor-delivered shipment status and retains a late-information workflow. Build an exception checklist around your lane and current instructions. Ask operations to confirm who notices a delayed vehicle and who records the change, even when an ASN has already been transmitted.
Why should Loblaw Companies pickup data distinguish pallets from pallet spaces?
Stacking can make those measures different. For preparation, compare the warehouse's pallet inventory with the trailer layout instead of assuming the two totals match. Keep the loading plan and source quantities available for review, and confirm the current portal limits and exception route with the transportation instructions.
What proves a Loblaw Companies connection is ready?
A documented scope, correct identifiers, tested business cases and the program's required production approval. Portal access, sample validation and a page describing the workflow are separate evidence. Retain the actual acceptance result and identify any operational step, such as a pickup exception, that remains outside the electronic mapping.

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: Loblaw Companies EDI requirements · Loblaw Companies supplier EDI · Loblaw Companies EDI CA

© 2026 SignalEDI Inc. All rights reserved.