Supplying Bunnings? We run the EDI integration and ongoing operations.
Managed end to end across the NZ and AU footprint, not handed back to your IT team.
If you supply Bunnings in NZ or Australia, you need EDI working and you need it to stay working. Flow handles the build, the day-to-day operations, and the ongoing changes. EDIFACT documents. Transport setup. Supplier portal coordination. Peppol where it applies. We’ve been doing this since 2014, across both markets.
Bunnings EDI is documented. The implementation work isn’t.
Bunnings has a published spec, a supplier onboarding portal, and a defined document flow. None of that does the integration work for you. Your ERP doesn’t speak EDIFACT D96A natively. The mappings have to land in your customer master correctly. The transport setup has to be right. Supplier performance is monitored, and it has to stay clean as the spec moves.
EDIFACT D96A is the standard
Bunnings sends ORDERS in EDIFACT D96A. Suppliers send INVOIC back in the same format. The spec is industry-standard, but most ERPs don’t read or write D96A natively. The integration layer has to translate both directions — accurately, every time.
NZ hardware sector context
If you’re supplying Bunnings alongside other NZ hardware retailers — PlaceMakers, Mitre 10, ITM — you’ll also encounter HIWG XML over Adaptiv VAN. That’s the wider NZ hardware-industry standard. An integration platform that handles both worlds keeps your retailer set on one stack.
Transport choice matters
Most Bunnings traffic runs over B2BE SFTP. Some suppliers use direct secure file transfer options. Peppol adoption is increasing across ANZ retail and procurement ecosystems. Picking the wrong path costs implementation time and ongoing maintenance.
Supplier performance matters
Bunnings tracks supplier performance against documented criteria. Supplier performance metrics may include document accuracy, timeliness, and fulfilment measures. The integration has to be right, and it has to stay right as the spec moves.
We run your Bunnings EDI integration. End to end.
Flow connects your ERP to Bunnings and manages the integration on an ongoing basis. Not a one-off build. Not a platform you have to learn. A managed integration partnership where we handle the EDI complexity so your team doesn’t have to.
EDIFACT D96A setup
We configure ORDERS, ORDRSP, DESADV, and INVOIC mappings between your ERP and the Bunnings spec. Validation against the Bunnings onboarding requirements before anything goes live.
HIWG / Adaptiv where it applies
Many Bunnings suppliers also supply PlaceMakers, Mitre 10, and other NZ hardware retailers, where HIWG XML over Adaptiv VAN is in play. Same platform handles both EDIFACT D96A and HIWG, so you don’t end up running two integration stacks.
B2BE VAN management
We handle the B2BE SFTP connection, the credential lifecycle, and the traffic routing. If your group already pays for B2BE, we work inside that. If not, we’ll advise on whether direct secure file transfer is the better path.
Onboarding portal coordination
Bunnings supplier registration goes through their portal. We work alongside it — handling the technical onboarding while you handle the commercial side. UAT runs against the Bunnings test endpoints.
Peppol readiness
Peppol adoption is increasing across ANZ retail and procurement ecosystems. Flow is ready to support Peppol where required, alongside the existing EDIFACT flow. Same platform handles both.
Performance monitoring
We watch the EDI flows and act on exceptions before they reach the supplier performance review. Document accuracy, timeliness, fulfilment — we monitor the metrics that matter and step in early.
Every Bunnings EDI document type. Covered.
Flow handles the full Bunnings EDI document flow across the EDIFACT D96A standard, plus the HIWG variant where NZ hardware applies, plus the emerging Peppol B2B layer.
| Document Type | What It Does |
|---|---|
| Purchase Orders (ORDERS / D96A) | Receive inbound orders from Bunnings stores or central buying via B2BE SFTP or direct SSH. Validated and posted into your ERP. |
| Order Response (ORDRSP) | Acknowledge receipt of the order back to Bunnings. Automated from your ERP confirmation step. Timing matters for supplier performance metrics. |
| Advance Ship Notice (DESADV) | Notify Bunnings of dispatch with SSCC tracking where used. Tied to the correct receiving store and delivery window. |
| Invoices (INVOIC / D96A) | Send compliant invoices electronically via B2BE or direct. Reduces manual processing and chargeback risk. |
| Statements | Inbound statements from Bunnings, parsed and posted into your AR for reconciliation. |
| Peppol (B2B) | Peppol adoption is increasing across ANZ retail and procurement ecosystems. Flow is ready to support Peppol where required, alongside the EDIFACT layer. |
| HIWG XML (other NZ hardware retailers) | Many Bunnings suppliers also supply PlaceMakers, Mitre 10, and other NZ hardware retailers where HIWG XML over Adaptiv applies. Handled in the same integration stack. |
Built for NZ and AU suppliers who’d rather run their business than manage Bunnings EDI.
Flow’s Bunnings EDI service is designed for ANZ manufacturers, distributors, and trade-retail suppliers who supply Bunnings — usually alongside other hardware and DIY retailers — and need compliant, monitored EDI without running it in-house.
You supply Bunnings (or are about to)
New supplier onboarding, existing supplier wanting cleaner supplier-performance metrics, or a NZ supplier expanding into the AU side of Bunnings.
You supply other ANZ retailers too
Most suppliers we work with run several retailers at once. We manage Bunnings alongside Mitre 10, PlaceMakers, Carters, ITM, The Warehouse, and others on a single integration platform.
You use an ERP (MYOB EXO, NetSuite, Greentree, Infor LN, Pronto, D365)
We connect to your existing system. No rip and replace. We’ve run Bunnings integrations on MYOB EXO and Exonet, NetSuite, Greentree, Exchequer, Dynamics SL, JDE Oracle, and Pronto.
You want someone to run it, not just set it up
A managed integration partnership, not a build-and-walk-away project. We stay accountable for the integration after go-live, including how it shows up in your supplier-performance metrics.
We know Bunnings EDI. We’ve been running it since 2014.
Flow started in New Zealand in 2005 building integration software for ANZ businesses. Bunnings EDI integrations have been part of that work since 2014, across both the NZ and AU operations. We’re not a global platform with a generic EDIFACT adapter. We’re an NZ-founded operator with deep Bunnings experience and customer evidence across both markets.
Bunnings depth, NZ and AU
EDIFACT D96A, HIWG / Adaptiv, B2BE, direct SSH, emerging Peppol. The integration patterns that come up with Bunnings, we’ve run.
We run it. You don’t have to.
We build it, operate it, and keep it running. You don’t need EDI expertise or Bunnings-specific knowledge on your team.
NZ founded. ANZ operated.
Started in Auckland. AWS ANZ hosting keeps your data in-region. Support from people in your timezone.
Fewer customers. Deeper responsibility.
We stay accountable for outcomes, not just uptime. Post go-live is where most integration relationships fall apart. It’s where ours start to prove themselves.
Get Bunnings EDI sorted. Talk to us.
Tell us about your Bunnings EDI requirements. We’ll come back to you within 2 business days with an initial assessment.