Skip to main content

Wesfarmers EDI requirements

Treat Wesfarmers as a group-level starting point, then identify the operating business and supplier account that actually owns your order, invoice and technical trading requirements.

Source-qualified document scope

Public sources reviewed 2026-11-09. These notes preserve the scope and access limits of the cited material; your current assigned packet controls implementation.

  • Commercial identity record: capture the exact buying entity, operating business, supplier number, country, currency and bill-to relationship from the agreement and order. Keep parent ownership as descriptive metadata rather than a routing key.
  • Business-specific implementation packet: request order, response, shipment, invoice and adjustment guides only for the actual workflow. Record message versions, transport, identifiers and approval requirements separately for each business that is in scope.
  • Product and destination master data: identify how each buyer recognizes trade items, pack sizes, delivery sites and supplier branches. A common internal SKU may map to different external identifiers without changing the underlying physical product.
  • Policy and operational evidence: retain relevant Group and business-specific supplier obligations alongside receiving, packaging and financial procedures. Distinguish governance compliance, item approval and technical acceptance rather than collapsing them into one onboarding status.

What the cited sources establish

  • Wesfarmers' current business directory lists distinct businesses including Bunnings, Kmart Group, Officeworks, Wesfarmers Health and Chemicals, Energy and Fertilisers. A group name is not enough to identify the buyer, receiving location, invoice account or technical interface.
  • The 2026 sustainability material describes Group minimum standards for ethical sourcing and supplier due diligence. These standards establish a governance context, not a shared EDI document matrix, transport endpoint or approval covering every business.
  • Wesfarmers' official demerger record documents Coles' separation in 2018. A historical Coles association must not be used to route today's Coles documents through an assumed Wesfarmers-wide configuration.
  • No universal Wesfarmers supplier message guide was established by the public sources reviewed on November 9, 2026. Obtain the current operating-business packet. This page provides scoping and validation advice, not SignalEDI certification, a ready-made group connection or an assertion that all divisions use the same standard.

Confirm in your current supplier packet

  • Ask who issues the purchase order and who is legally responsible for payment. Use those answers to establish the trading relationship before selecting software templates, endpoints or a testing contact.
  • Create a separate scope row for each operating business and country. Include explicit exclusions so a Bunnings pilot is not later described as approval for Officeworks, Kmart Group or an unrelated Coles account.
  • Compare candidate requirements field by field before reusing a map. Separate reusable transformations, such as internal product normalization, from buyer-specific envelope IDs, location codes, invoice grouping and correction behavior.
  • Have each business owner confirm its own approval evidence and operational readiness. A shared provider, common parent or successful message to a different account does not remove the need to verify the new scope.
  • Maintain a change register for acquisitions, divestments, account migrations and new buying entities. Review affected master data and retained historical records so corporate changes do not silently rewrite old transactions.

This is a preparation checklist, not an additional mandate, certified mapping or production approval. Confirm transport, document versions, deductions and timing for your program.

Sources and their limits

Read the full partner planning guide and preparation exercises

© 2026 SignalEDI Inc. All rights reserved.