EDI Connection to Douglas in hours, not months
Streamline your supply chain with Douglas-specific EDIFACT integration — automate orders, ASNs, invoices, and inventory reporting with zero hassle. Join hundreds of beauty and wellness suppliers already delivering flawlessly to Europe’s leading retailer for cosmetics and fragrances.
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.
Douglas 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 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
Integration with Douglas is complicated by several factors. Douglas applies strict schema checks and retailer-specific segment extensions across all document types with custom EDIFACT validation. GS1 compliance is essential, as GLN, GTIN and SSCC accuracy is critical—incorrect values lead to rejections or blocked transactions. For shipping notices, DESADV must reflect exact shipment hierarchy—pallet, case, item—with NVE-level detail expected. Additionally, Douglas operates across multiple regions, each with their own individual EDI provider and requirements, meaning each region must be tested separately.
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 Douglas involves a demanding setup with strict format and data validation requirements:
AS2 Regional Connection
Mandates a direct technical connection using AS2 protocol with each region's EDI provider
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 Douglas:
- 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 VAT handling in INVOIC for cross-border or multi-currency transactions.
- Incorrect billing GLN across different regions
- Incorrect invoice value resolution of gross, net, tax or due amounts.
- 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; Douglas 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 Douglas compared to traditional EDI solutions:
How to connect with Douglas in 3 simple steps
Get started with Douglas 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 Douglas as a trade partner, and ensure all Douglas-specific fields are mapped correctly from your ERP.
2. Test your connection
Start exchanging test documents. Receive orders from Douglas, send back invoices and shipping notices via Procuros. All messages go through automated compliance checks based on GS1 and Douglas validation rules.
3. Go live
You’re ready to go live. After Douglas’s confirmation, you start trading in production. Procuros ensures continuous monitoring and troubleshooting, so everything runs smoothly.
Quantified Benefits for Douglas 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 Douglas companies simultaneously instead of managing separate implementations.
Guarantee Continuous Compliance
Automatic updates handle Douglas's continuous optimization requirements without additional costs or downtime.
Minimize Rejections
Procuros catches errors before your message is sent to Douglas. This allows you to immediately fix any errors and avoid rejections, penalties and delays.
.avif)
Frequently Asked Questions
How long does Douglas EDI certification take?
Traditional timeline: > 3 months. With Procuros: go-live in as little as 48 hours, including regional variation testing.
What EDIFACT documents are required?
ORDERS, DESADV, INVOIC.
Do we need barcodes and SSCCs?
Yes—GTIN/EAN-13 for all sellable units and SSCC-18 is mandatory in DESADV shipments
What transport protocol is used?
The technical protocol depends on the regions respective Douglas’ EDI provider, however most mandate AS2.
What happens when Douglas updates requirements?
Procuros tracks changes, automatically updates templates and validations—ensuring continuous compliance.
Is ERP integration required?
No. ERP integration is supported but optional—Procuros WebEDI interface enables low-volume suppliers to comply easily.
What support is offered?
24/7 Procuros support staffed by Douglas EDI specialists, VAT logic, GS1, naming, transport issues.
What if I supply multiple European regions?
Procuros handles region-specific variants automatically, adapting EDIFACT syntax, VAT, and tax logic by country.
How long does certification with Douglas 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 Douglas 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 Douglas 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.