EDI Connection to OBI in hours, not months
Leverage our prebuilt OBI EDI integration to automate orders, invoices, ASNs, and inventory with minimal effort—no more manual processes slowing you down. Join hundreds of suppliers already powering Europe’s top DIY retailer—OBI—with frictionless, fully compliant EDI.
Seamlessly automate purchase orders, shipping notices, invoices, and other documents with retailer-ready EDI connectivity—without the usual delays or manual work. Trusted by suppliers scaling across Europe’s largest retail networks.
OBI Supported Documents:
You Send:
- Dispatch Advice (DESADV)
- Invoice (INVOIC)
- Order Response (ORDRSP)
- Dispatch Advice (DESADV)
- Invoice (INVOIC)
You receive:
- Purchase Order (ORDERS)
- Purchase Order (ORDERS)
- Remittance Advice (REMADV)
- Receipt Advice (RECADV)
Unique Document Requirements:
- Mandates compliance with OBI EDIFACT standard specific segment and qualifier usage
- Requires GS1-compliant identifiers: GTIN, GLN, SSCC
- Document requirements may vary across regions (Germany, Austria, Switzerland), subsidiaries, or fulfillment models (e.g., warehouse vs direct-to-store)
- Based on UN/EDIFACT (EANCOM) with retailer-specific segment and qualifier usage
- Requires GS1-compliant identifiers: GTIN, GLN, SSCC
- Document mappings may vary across regions, subsidiaries, or fulfillment models (e.g., warehouse vs direct-to-store)
Integration Challenges
OBI's EDI integration presents several challenges. Manual testing bottlenecks exist as all go-live approvals must pass through OBI's supplier portal, with test cycles often involving multiple iterations and wait times. OBI regularly modifies its EDIFACT naming conventions and validation rules—sometimes without prior notice. GS1/EAN-13 barcode formats are mandatory and strictly validated, with common rejections stemming from incorrect lengths, duplicates, or non-standard vendor codes. Custom EDIFACT mapping specific to OBI requirements is necessary. GLN, GTIN and SSCC accuracy is critical for GS1 compliance—incorrect values lead to rejections or blocked transactions. Discount structures, deposit fees, or item-level details (e.g., consumer units) must follow strict rules. The process requires manual testing via email with the OBI IT/EDI department and separate testing with each OBI region (Germany, Switzerland, Austria).
Retailers often require custom EDIFACT mappings that include non-standard use of segments, making integration more complex. Accuracy in GLN and GTIN values is critical—any mistakes can lead to document rejections or even blocked goods. Additionally, elements like discount structures, deposit fees (Pfand), and unit-level details such as consumer units must follow strict formatting and logic rules. Depending on the sales channel or fulfillment center, you may also encounter multiple regional formats or different clearinghouses. Without automation or expert guidance, long test cycles and manual validations can significantly delay your go-live timeline.
Technical Complexity
Integrating with OBI involves a demanding setup with strict format and data validation requirements:
AS2 Protocol Mandate
Mandates a direct technical connection using AS2 protocol
EDIFACT Standard
Requires compliance with EDIFACT standard with mandatory segments and cross-references
Regional System Variance
Different (test) systems for orders, shipping notices, and invoices by region
Complex Mapping Logic
Mandatory qualifiers and cross-document references must be applied correctly.
Protocol Configuration
AS2, SFTP, or VAN setup often involves certificates and troubleshooting connectivity.
Strict GS1 Validation
All identifiers—items, parties, and logistics—must pass checksum enforcement.
Common Onboarding Failures
A number of common issues can lead to invoice rejections or processing delays when working with OBI:
- Missing or incorrect mandatory information (e.g., address info, VAT information, order numbers) leading to rejections and delays
- Missing or incorrect SSCC label on shipping notices
- Incorrect labelling of item numbering
- Mismatch between ordered and shipped SKU quantity and unit of measure
- Incorrect invoice matching logic (e.g., mismatch with order or shipping advice)
- Incorrect invoice value resolution of gross, net, tax or due amounts.
- Missing payment terms or mandated discounts (e.g., Skonto)
- Missing mandatory fields (e.g., address info, order numbers) leading to auto-rejection
- Incorrect invoice matching logic (e.g., mismatch with order or shipping advice)
- Security certificate mismatches or expired AS2 credentials
- Mixed product batches or missing SSCCs in dispatch advices
- Inconsistent barcode labeling or non-conforming formats in product catalog data
Industry Timeline & Failure Rates
EDI integrations typically require months; OBI specific requirements drive higher error rates without expert integration tools and knowledge. Manual document review during onboarding requires buffer time for feedback cycles.
The Procuros Way
Procuros simplifies the way you connect with OBI compared to traditional EDI solutions:
How to connect with OBI in 3 simple steps
Get started with OBI integration in just a few days
1. Connect to Procuros
Connect your system to Procuros using native connectors. Configure the data exchange (JSON, XML, CSV), request OBI as a trade partner, and ensure all OBI-specific fields are mapped correctly from your ERP.
2. Test your connection
Start exchanging test documents. Receive orders from OBI, send back invoices and shipping notices via Procuros. All messages go through automated compliance checks based on GS1 and OBI validation rules.
3. Go live
You’re ready to go live. After OBI’s confirmation, you start trading in production. Procuros ensures continuous monitoring and troubleshooting, so everything runs smoothly.
Quantified Benefits for OBI Suppliers:
Reduce Integration Costs by 85%
Traditional EDI requires custom projects and unpredictable costs. Procuros enables integration with minimal setup and transparent pricing.
Access All Regional Markets
Connect to all OBI companies simultaneously instead of managing separate implementations.
Guarantee Continuous Compliance
Automatic updates handle OBI's continuous optimization requirements without additional costs or downtime.
Minimize Rejections
Procuros catches errors before your message is sent to OBI. This allows you to immediately fix any errors and avoid rejections, penalties and delays.
Frequently Asked Questions
How long is OBI EDI certification?
Traditional timeline: >4 months. With Procuros: go-live in as little as 48 hours, including regional variation testing.
What documents types are required?
EDIFACT ORDERS, DESADV, INVOIC are mandatory. Inventory reporting (INVRPT) and remittance (REMADV) depend on product category or agreement.
What transport protocol is needed?
AS2 with MDNs is preferred; SFTP or VAN acceptable if aligned with OBI TP agreement.
What’s the cost?
OBI charges no supplier EDI fees. Procuros offers a monthly subscription covering unlimited message volume & updates without any up-front costs.
How is compliance ensured?
Procuros ensures EDIFACT conformance and provides detailed data checks preventing you from sending wrong data (e.g., validating all GLNs). Failed messages flagged instantly; no manual rework.
Was ist, wenn OBI die EDI-Spezifikationen aktualisiert?
Procuros tracks all OBI schema changes; updates are auto-deployed to your integration at no extra cost—you’re always compliant.
Who supports me during issues?
24/7 Procuros support team conversant with OBI’s EDI landscape—certificate issues, MDNs, reconciliation, and protocol errors.
Can I onboard low-volume suppliers?
Yes—Procuros WebEDI interface supports lightweight suppliers unable to automate via ERP, yet still compliant with OBI’s protocols.
How long does certification with OBI take?
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Which formats does OBI support?
Most retailers require UN/EDIFACT (EANCOM). XML or WebEDI may be used in low-volume cases or through middleware.
What GS1 identifiers are required?
GLN (business locations), GTIN (products), and SSCC (logistics units)—all must pass checksum validation.
Which protocols are used?
Common options include AS2, SFTP, or legacy X.400 via VANs. Procuros configures all channels.
How complex is regional dispatch advice?
Procuros maps all formats upfront—suppliers avoid manual adaptation.
What happens if OBI updates their requirements?
Procuros auto-updates mapping logic and segment rules to avoid disruptions.
How are document or delivery errors handled?
Our team monitors message flow, flags issues (e.g., GLN mismatch or missing qualifiers), and resolves them in hours—not days.
Can small or seasonal suppliers use this?
Yes. Whether you’re sending 5 or 5,000 documents, Procuros adapts to your volume and ERP capabilities.
What do I need to get started?
Submit your GLN and ERP interface details—our team guides you through every step to go live quickly and painlessly.