Quick answers
- Can SignalEDI help me connect to Woolworths Group?
- SignalEDI helps prepare mappings, sample validation, and the workflow required for your Woolworths Group 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 Woolworths Group 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 Woolworths Group?
- 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
- The Australian Partner Hub EDI article, last modified December 22, 2025, describes messages derived from EANCOM2002 D.01B and exchange through accredited value-added networks. Its indexed official content was reviewed on November 9, 2026; direct retrieval returned a page-rendering error, so linked technical files were not inspected.
- The published matrix lists orders and invoices for DC, direct-to-store and fresh-produce flows. It lists order responses and ASNs for DC delivery, and order changes for DC and fresh produce. It also identifies a fresh-produce delivery schedule guide. This category distinction is more useful than a universal five-message claim.
- Partner Hub separately describes browser-based Webforms and integrated electronic trading. Primary Connect's delivery-support page addresses physical supply standards and supplier collaboration. An electronic message choice does not settle packaging, transport or receiving compliance.
- This page concerns Woolworths Group in Australia, not Woolworths South Africa. Confirm the assigned Australian business, category, current guide and accreditation process; the public sources do not certify SignalEDI or establish an active 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.
- Orders and changes: use the matrix as a scoping starting point, then obtain the exact assigned implementation guide. Record the delivery category and business identifiers before deciding which order-change messages the workflow must handle.
- Responses and shipment notices: include them according to the actual Australian program, rather than assigning a DC message set to every direct-to-store or produce account. Define how quantities and packaging originate in operational systems.
- Invoices and payment references: ask for the current billing guide, tax representation, grouping and correction rules. Keep invoice transmission, business acceptance and subsequent payment evidence as distinct events in the reconciliation plan.
- Delivery schedules and physical standards: obtain the applicable fresh-produce schedule materials where relevant and the current delivery requirements. Record which planning data is informative and which document actually authorizes fulfillment.
Connectivity and testing requirements
Connectivity
Confirm whether the current Woolworths Group 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.
- The Australian Partner Hub EDI article, last modified December 22, 2025, describes messages derived from EANCOM2002 D.01B and exchange through accredited value-added networks. Its indexed official content was reviewed on November 9, 2026; direct retrieval returned a page-rendering error, so linked technical files were not inspected.
- The published matrix lists orders and invoices for DC, direct-to-store and fresh-produce flows. It lists order responses and ASNs for DC delivery, and order changes for DC and fresh produce. It also identifies a fresh-produce delivery schedule guide. This category distinction is more useful than a universal five-message claim.
- Partner Hub separately describes browser-based Webforms and integrated electronic trading. Primary Connect's delivery-support page addresses physical supply standards and supplier collaboration. An electronic message choice does not settle packaging, transport or receiving compliance.
- This page concerns Woolworths Group in Australia, not Woolworths South Africa. Confirm the assigned Australian business, category, current guide and accreditation process; the public sources do not certify SignalEDI or establish an active connection.
Questions to resolve from the current buyer packet
- Identify the Australian legal customer, merchandise category, delivery route and receiving locations. Do not reuse a configuration based only on the Woolworths brand or assume that every Group business has the same gateway and operating rules.
- Compare your required messages with the official category matrix and mark differences for confirmation. Keep a dated copy of the assigned guide and sample files rather than relying on an old provider checklist or an unversioned screenshot.
- Choose the approved electronic trading route with your onboarding owner. If evaluating Webforms versus integration, compare operational ownership, duplicate prevention and data entry responsibilities without promising a fixed implementation duration.
- Bring warehouse staff into the mapping review. Link the shipped quantities, package identifiers and transport references to the same physical load, and reconcile any change made after the original picking plan.
- Define the evidence required for test completion and production approval. Separate syntax validation from category-specific business scenarios, delivery readiness and account accreditation; record unresolved exceptions before live trading begins.
EDI requirements quick reference
Document codes and the planning checklist for this partner also live on the Woolworths Group 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.
Select the correct delivery category
Prepare three internal scope cards representing DC delivery, direct-to-store delivery and fresh produce. Compare each proposed document list with the published matrix and the current assigned packet. Mark any unsupported message as a question, and identify which account and destination each card is intended to represent.
What a useful result looks like
The review produces a clear message scope for each actual lane. A document required for one category is not silently promoted to a universal mandate. Missing account-specific guidance remains visible instead of being replaced with a generic X12 or overseas template.
Distinguish schedule from fulfillment authority
For a hypothetical produce item, create a planning schedule, an order and a subsequent change. Ask the supply planner which record governs packing and dispatch under the assigned specification. Introduce a change after picking has begun and document the point where a person must resolve the conflict before shipment.
What a useful result looks like
The example does not ship twice because two records refer to the same demand. Staff can explain which quantity and date are authoritative and which information is only planning input. The decision is supported by the account's instructions, not an assumed interpretation of a message name.
Reconcile a changed physical load
Create a synthetic dispatch record, then remove a damaged case before loading. Trace the affected quantity through the warehouse record, any required shipment notice and the invoice preparation worksheet. Ask the team to show where the change is captured and how it avoids retaining the original expected quantity as if it shipped.
What a useful result looks like
Physical and electronic records describe the same final load. Any message already sent follows the assigned correction process rather than an improvised replacement. The record preserves who changed the quantity and why, enabling receiving and finance staff to understand the difference.
Control a trading-route transition
Plan a hypothetical move from manually operated Webforms to an approved integrated route. Identify a final document owned by the old process and a first document owned by the new process, then simulate a delayed order arriving near the boundary. Describe rollback and reconciliation without transmitting anything to production.
What a useful result looks like
Each business document has one submission owner and one traceable history. The transition cannot create duplicate invoices merely because both routes remain accessible. Readiness depends on confirmed account approval and reconciled exceptions rather than a promised calendar duration.
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.
- Woolworths Australian EDI overview — Woolworths Group
Supports: Official indexed article dated December 22, 2025: EANCOM2002 D.01B, network-provider model and delivery-category matrix. Direct page rendering failed on November 9, 2026; linked MIG contents were not inspected.
- Woolworths electronic transacting options — Woolworths Group
Supports: Official indexed supplier onboarding material distinguishes Webforms and integrated B2B trading. Published duration estimates are not used as project promises.
- Primary Connect delivery support — Primary Connect
Supports: Official Australian supply-chain entry point for delivery standards and supplier collaboration; reviewed November 9, 2026.
Woolworths Group questions
- Does every Woolworths Group Australian supplier exchange the same messages?
- No universal set is supported by the published category matrix. Begin with your delivery model, then confirm the current packet for the assigned business. Treat optional or out-of-scope documents explicitly so a configuration cannot accidentally demand a shipment notice or response intended for a different lane.
- Can Woolworths Group Webforms replace an integrated EDI project?
- The public onboarding material describes both routes, but the appropriate choice depends on the account and operating process. Confirm which route is approved, who enters or exports information, and how you avoid duplicate documents if moving between them. A portal account alone does not prove an integrated connection is accredited.
- What should Woolworths Group fresh-produce suppliers clarify first?
- Confirm the relationship between schedules, orders, changes and invoices in the assigned fresh-produce guide. Ask which message governs the quantity and date to fulfill, then test changes before dispatch. Keep product condition and physical receiving requirements in scope without borrowing an unrelated DC message matrix or South African supplier handbook.
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: Woolworths Group EDI requirements · Woolworths Group supplier EDI · Woolworths Group EDI AU