EDI Connection to tegut in hours, not months
Achieve seamless tegut EDI integration – send EDIFACT Purchase Orders and receive Invoices, Acknowledgements, ASNs in days using our pre-built Procuros-optimized tegut maps and workflows. Join 100+ grocery & food suppliers already EDI‑connected to tegut across Germany and enjoy reliable grocery supply chain operations.
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.
tegut 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
- 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
Integration with tegut presents several challenges. Markant serves as a mandatory clearinghouse, meaning all EDI documents must go through Markant with no direct connection option. GS1 compliance is essential, as GLN, GTIN and SSCC accuracy is critical—incorrect values lead to rejections or blocked transactions. Additionally, discount structures, deposit fees, and item-level details (e.g., consumer units) must follow strict rules. The process requires manual testing with the Markant supplier portal and custom EDIFACT mapping specific to Markant and tegut requirements.
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 tegut involves a demanding setup with strict format and data validation requirements:
AS2 Protocol Requirement
Mandates a direct technical connection using AS2 protocol
EDIFACT Compliance Need
Requires EDIFACT standard with multiple mandatory segments and cross-references
Regional System Differences
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 tegut:
- 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; tegut 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 tegut compared to traditional EDI solutions:
How to connect with tegut in 3 simple steps
Get started with tegut 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 tegut as a trade partner, and ensure all tegut-specific fields are mapped correctly from your ERP.
2. Test your connection
Start exchanging test documents. Receive orders from tegut, send back invoices and shipping notices via Procuros. All messages go through automated compliance checks based on GS1 and tegut validation rules.
3. Go live
You’re ready to go live. After tegut’s confirmation, you start trading in production. Procuros ensures continuous monitoring and troubleshooting, so everything runs smoothly.
Quantified Benefits for tegut 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 tegut companies simultaneously instead of managing separate implementations.
Guarantee Continuous Compliance
Automatic updates handle tegut's continuous optimization requirements without additional costs or downtime.
Minimize Rejections
Procuros catches errors before your message is sent to tegut. This allows you to immediately fix any errors and avoid rejections, penalties and delays.
Frequently Asked Questions
What’s the tegut EDI go-live timeframe?
Traditional timeline: > 3 months. With Procuros: go-live in as little as 48 hours, including regional variation testing.
Which formats are mandatory?
Only EDIFACT, specifically formats ORDERS, DESADV, INVOIC, REMADV.
How do you handle GS1 requirements?
Procuros automatically validates SSCC, GTIN, and GLN alignment before sending.
What if tegut updates the EDIFACT standard?
We adapt the configuration immediately and re-certify without any effort required on your side.
Who supports troubleshooting?
You get a dedicated EDI specialist with hands-on assistance and next-day issue resolution.
Can I monitor message status?
Yes—Procuros offers a real-time dashboard with delivery logs and message analytics.
How long does certification with tegut 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 tegut 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 tegut 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.