Quick answers
- Can SignalEDI help me connect to Metro Inc.?
- SignalEDI helps prepare mappings, sample validation, and the workflow required for your Metro Inc. 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 Metro Inc. 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 Metro Inc.?
- 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.
Plan the integration workflow
SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.
1. Your business system
Identify the source records, system edition, data owner, and allowed access.
2. SignalEDI preparation
Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.
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 checklistPublic sources reviewed 2026-11-09
What the public record confirms
- Metro Inc.'s official corporate site distinguishes food and pharmacy operations. Its food page identifies banners operating in Quebec and Ontario, including Metro, Super C and Food Basics. The Canadian business should not be confused with similarly named wholesalers or retailers in other countries.
- The supplier-relations page offers a Quebec product-innovation entry point and links a Supplier Code of Conduct updated in October 2025. Product introduction and responsible-procurement obligations are relevant onboarding work, but neither is a technical EDI implementation guide.
- The public primary sources reviewed on November 9, 2026 do not establish a universal transaction matrix, transport protocol, ASN hierarchy or invoice grouping rule for every Metro Inc. supplier. Account-specific technical and receiving materials remain required inputs, not details to infer from another Canadian retailer.
- This guide separates verified business context from recommended preparation. It does not represent a SignalEDI certification, a completed supplier setup or approval to use a particular production endpoint.
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.
- Account and banner scope: record the contracting entity, approved supplier number, province, banner and receiving location. Ask whether food, pharmacy, warehouse and direct-store arrangements have separate technical or finance instructions.
- Product setup: obtain the assigned requirements for item identifiers, pack hierarchy, descriptions, costs and supporting product records. Link a proposed product to its approved listing status before making it available to an order-processing workflow.
- Order and receipt messages: request current samples showing the destination and item references your account will receive. Confirm whether an order revision, short shipment or substitution needs a specific response rather than a free-text note.
- Invoice and adjustment documents: confirm invoice references, Canadian tax fields, credits and dispute evidence with the applicable finance instructions. Keep technical transmission acknowledgements separate from goods receipt, price agreement and payment status.
Connectivity and testing requirements
Connectivity
Confirm whether the current Metro Inc. 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.
- Metro Inc.'s official corporate site distinguishes food and pharmacy operations. Its food page identifies banners operating in Quebec and Ontario, including Metro, Super C and Food Basics. The Canadian business should not be confused with similarly named wholesalers or retailers in other countries.
- The supplier-relations page offers a Quebec product-innovation entry point and links a Supplier Code of Conduct updated in October 2025. Product introduction and responsible-procurement obligations are relevant onboarding work, but neither is a technical EDI implementation guide.
- The public primary sources reviewed on November 9, 2026 do not establish a universal transaction matrix, transport protocol, ASN hierarchy or invoice grouping rule for every Metro Inc. supplier. Account-specific technical and receiving materials remain required inputs, not details to infer from another Canadian retailer.
- This guide separates verified business context from recommended preparation. It does not represent a SignalEDI certification, a completed supplier setup or approval to use a particular production endpoint.
Questions to resolve from the current buyer packet
- Resolve the exact Metro Inc. business first. A corporate parent, store banner, bill-to entity and physical destination can serve different roles. Give each a named field in the integration worksheet and preserve the retailer-assigned codes.
- Ask the buyer or onboarding owner which current technical packet applies to the agreed delivery lane. Record its title, version and account scope, including whether a province-specific instruction overrides a general supplier document.
- For a Quebec innovation submission, distinguish the product proposal from an authorized listing and technical activation. Prepare commercial, item-data and logistics questions without assuming that an acknowledgement of the proposal is an order.
- Have warehouse and finance staff reconcile one safe delivery example together. Include a changed case pack and a short receipt so they can identify where the original order, physical movement and billed quantity may diverge.
- Define a controlled process for future scope changes, such as adding a banner or switching from store delivery to a DC. Review identifiers, receiving evidence and correction rules before reusing a previously tested mapping.
EDI requirements quick reference
Document codes and the planning checklist for this partner also live on the Metro Inc. 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 plansPractice 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 Canadian entities and banners
Prepare a synthetic customer master containing two Canadian receiving locations and a deliberately unrelated business with a similar Metro name. For each, identify the legal customer, banner, province, bill-to account and ship-to code using approved records. Ask the order-routing owner to explain why a display name alone cannot select a destination or mapping.
What a useful result looks like
The wrong business cannot inherit the Canadian supplier setup. Each legitimate destination has a traceable account relationship, and any unconfirmed banner is held for review. The resulting worksheet identifies the exact scope that the current technical packet must cover.
Move from proposal to approved item
Take a hypothetical product through proposal, buyer review, item-data preparation and approval. Add a second packaging option while the proposal is still being discussed. Define which source controls the approved product identifier and how the integration distinguishes a draft case configuration from one that may actually be ordered.
What a useful result looks like
Only approved item data enters the order-processing example. The team can show who authorized the final configuration and which version was used. A proposed price or pack size cannot silently replace the approved value on an existing order.
Investigate quantity and tax differences
Build an internal sample with an order in cases, a short receipt and an invoice generated from the original ordered quantity. Ask operations to identify the physical difference and finance to explain the applicable billing and tax treatment under the current account instructions. Record the correction path without inventing a retailer tolerance or transaction code.
What a useful result looks like
The discrepancy is visible before submission and is assigned to the proper owner. The corrected commercial outcome is linked to the original documents. A quantity fix does not erase receipt evidence or make an unsupported assumption about taxes, credits or invoice consolidation.
Review a new distribution lane
Compare an existing hypothetical direct-store arrangement with a proposed DC delivery. List the data needed for each, including order references, packaging, appointment or delivery evidence and financial reconciliation. Ask the implementation owner to mark which details are confirmed, which remain questions and which existing tests must be repeated after the lane changes.
What a useful result looks like
The scope change produces a focused review instead of a brand-name copy of the old setup. Reusable components have an evidence-based reason to remain unchanged. New receiving and billing requirements are resolved before any claim of live trading readiness.
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.
- Metro Inc. supplier relations — Metro Inc.
Supports: Public supplier entry point, Quebec innovation program and October 2025 supplier-code update; reviewed November 9, 2026. Not a message specification.
- Metro Inc. food operations — Metro Inc.
Supports: Canadian food banners and provincial business context; page reports information as of July 4, 2026. Does not prove common EDI rules across banners.
- Metro Inc. Supplier Code of Conduct — Metro Inc.
Supports: Official responsible-procurement document linked from supplier relations; reviewed November 9, 2026. Commercial obligations are separate from technical message acceptance.
Metro Inc. questions
- Does Metro Inc. have one EDI specification for all banners?
- The public sources reviewed do not establish that. Obtain the packet assigned to your Canadian legal entity, banner, province and delivery program. Shared ownership is not evidence that order identifiers, receiving procedures or invoice rules are interchangeable. Keep any unresolved differences explicit before deciding which mapping components can be reused.
- Does submitting a product idea to Metro Inc. authorize electronic trading?
- No. A proposal is a commercial introduction, not proof that the product or supplier account is active. Track buyer approval, item setup, logistics arrangements and technical readiness as separate steps. Your implementation should not generate production documents from a draft listing or treat an introduction acknowledgement as a purchase order.
- What should Metro Inc. suppliers test when public EDI details are limited?
- Start with internal data consistency: account identity, approved products, destination references, pack conversions and the connection between receipts and invoices. Then apply the current assigned specification to partner-facing samples. Clearly label preparatory exercises so a useful internal result is never confused with retailer acceptance or completed certification.
Related EDI resources
- Customer requires EDI guide turns the buyer packet into a scoped implementation checklist.
- QuickBooks EDI integration explains supported accounting workflows. Confirm system edition and document scope; it does not establish a connector for this program.
- Managed EDI onboarding is an optional paid path when your team wants help coordinating the scoped partner workflow.
- Walmart EDI requirements covers publicly documented supplier interfaces and buyer-packet boundaries for Walmart programs.
- EDI requirements checker drafts a local readiness checklist without saving buyer data.
Prepare your side for partner testing
SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.
Connect nowTopics: Metro Inc. EDI requirements · Metro Inc. supplier EDI · Metro Inc. EDI CA