EDI Connection to Rewe in hours, not months
Automate orders, invoices & deliveries instantly with Rewe-specific integration. Join hundreds of suppliers trading with Rewe’s 15,500+ stores across Europe—seamlessly.
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.
Rewe Supported Documents:
You Send:
- Dispatch Advice (DESADV)
- Invoice (INVOIC)
- Order Response (ORDRSP)
- Dispatch Advice (DESADV)
- Invoice (INVOIC)
You receive:
- Purchase Order (ORDERS)
- Remittance Advice (REMADV)
- Purchase Order (ORDERS)
- Remittance Advice (REMADV)
- Receipt Advice (RECADV)
Unique Document Requirements:
- Mandates compliance with EDIFACT standard retailer-specific segment and qualifier usage
- Requires GS1-compliant identifiers: GTIN, GLN, SSCC
- Document requirements may vary across regions, 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
Rewe's EDI integration presents several challenges. Legacy communication via X.400 protocols requires specialized setup for each document type. The retailer uses multiple standards with differing EDIFACT implementations across Rewe Germany, Rewe International (Billa), and the Dortmund branch. Valid 13-digit GS1 GLN identifiers are mandatory for all EDI messages, especially for dispatch advices and invoices. Suppliers must specify whether they have a contractual or non-contractual relationship for correct transmission. Additionally, Rewe requires a single daily transmission of invoices for all affiliated entities, and mandates manual testing through their supplier portal.
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 Rewe involves a demanding setup with strict format and data validation requirements:
Individual Mapping Logic
Per document with multiple mandatory segments and cross-document references
Single Transmission Only
All invoices across all REWE linked entities and subsidiaries in one transmission
Separate Document Systems
Different systems for orders, shipping notices, and invoices
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 Rewe:
- Missing SSCC/SSCC‑checksum causing DESADV rejections
- Incorrect GLN registration or UNB segment sender/receiver mismatch
- Missing or incorrect mandatory information (e.g., address info, VAT information, order numbers) leading to rejections and delays
- Not all invoices are sent as a single batch
- Sending to the wrong technical system
- 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; Rewe 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 Rewe compared to traditional EDI solutions:
How to connect with Rewe in 3 simple steps
Get started with Rewe 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 Rewe as a trade partner, and ensure all Rewe-specific fields are mapped correctly from your ERP.
2. Test your connection
Start exchanging test documents. Receive orders from Rewe, send back invoices and shipping notices via Procuros. All messages go through automated compliance checks based on GS1 and Rewe validation rules.
3. Go live
You’re ready to go live. After Rewe’s confirmation, you start trading in production. Procuros ensures continuous monitoring and troubleshooting, so everything runs smoothly.
Quantified Benefits for Rewe 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 Rewe companies simultaneously instead of managing separate implementations.
Guarantee Continuous Compliance
Automatic updates handle Rewe's continuous optimization requirements without additional costs or downtime.
Minimize Rejections
Procuros catches errors before your message is sent to Rewe. This allows you to immediately fix any errors and avoid rejections, penalties and delays.
Frequently Asked Questions
How long to certify with Rewe?
Traditional timeline: >4 months. With Procuros: go-live in as little as 48 hours, including regional variation testing.
What are Rewe’s technical protocols?
Supports EDIFACT EANCOM, AS2, X.400 (VAN) via X.400 gateway or SFTP, plus Web‑EDI REDI.
How does testing work with Rewe?
GLN for parties, GTIN for Sandbox testing of ORDERS → you send DESADV/INVOIC; Procuros handles all validations and error resolution., SSCC for logistics; all must be checksum valid.
What if Rewe changes requirements?
Procuros tracks Rewe spec changes (e.g., GS1 updates) and pushes auto-maps—no downtime or manual updates on your side.
Who supports error handling?
Our team monitors message flow, flags qualifier or regional compliance errors, and resolves issues within hours.
Is it suitable for small suppliers?
Yes. Even low-volume suppliers benefit from automated GS1 checks, qualifier logic, and support at a low cost.
How long does certification with Rewe 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 Rewe 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 Rewe 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.