EUDR URL Patterns
GS1 Digital Link URL patterns for EUDR implementations
Every entity in an EUDR implementation is identified by a GS1 Digital Link URL. This page lists the patterns for products, locations, organizations and devices and shows how they connect to master data, events and regulatory references.
Base URL Structure
All identifiers follow the same GS1 Digital Link structure:
https://id.gs1.org/{ai}/{value}
Product Identifiers (SGTIN)
A product is identified by its GTIN together with a serial number:
https://id.gs1.org/01/{GTIN}/21/{Serial}
The examples on these pages use the following products:
| Product | URL |
|---|---|
| Timber log | https://id.gs1.org/01/09521234000020/21/LOG-2025-001 |
| Furniture | https://id.gs1.org/01/09521234000037/21/TABLE-2025-001 |
The URL breaks down into these parts:
https://id.gs1.org/01/09521234000020/21/LOG-2025-001
│ │ │ │
│ │ │ └── Serial Number (AI-21)
│ │ └── Application Identifier
│ └── GTIN (14 digits)
└── Application Identifier
Location Identifiers (GLN)
Locations such as the plot of land or a processing facility are identified by a Global Location Number (GLN):
https://id.gs1.org/414/{GLN}
For example:
| Location | URL |
|---|---|
| Plot of Land | https://id.gs1.org/414/9521234000099 |
| Processing Facility | https://id.gs1.org/414/9521234000105 |
Organization Identifiers (Party GLN)
Organizations are identified by a Party GLN:
https://id.gs1.org/417/{GLN}
For example:
| Organization | URL |
|---|---|
| Timber Producer | https://id.gs1.org/417/9521234000006 |
| Furniture Manufacturer | https://id.gs1.org/417/9521234000105 |
Device Identifiers (GIAI)
GPS devices and sensors are identified by a Global Individual Asset Identifier:
https://id.gs1.org/8004/{GIAI}
For example:
https://id.gs1.org/8004/9521234000006-GPS-001
Content Negotiation
A GS1 Digital Link resolver supports content negotiation and answers the same URL in the format the Accept header asks for:
| Accept Header | Response |
|---|---|
application/ld+json | JSON-LD product data |
application/json | JSON product data |
text/html | Human-readable web page |
To request JSON-LD, for example:
curl -H "Accept: application/ld+json" \
https://id.gs1.org/01/09521234000020/21/LOG-2025-001
Link Types
Link types give access to related data:
| Link Type | Purpose | URL Pattern |
|---|---|---|
| EPCIS Events | Event history | ?linkType=epcis |
| Master Data | Product details | ?linkType=masterData |
| Certification | Certificates | ?linkType=certificationInfo |
| Recall | Recall info | ?linkType=recallStatus |
The ?linkType= query parameter takes the bare GS1 relation name (per the GS1 Digital Link spec). The same relations appear as full IRIs (https://ref.gs1.org/voc/epcis, …) when keyed in an IETF linkset response.
The EPCIS events of a timber log, for example, are available at:
https://id.gs1.org/01/09521234000020/21/LOG-2025-001?linkType=epcis
Event Identifiers
EPCIS events are identified by UUIDs:
urn:uuid:{uuid}
For example:
urn:uuid:550e8400-e29b-41d4-a716-446655440020
Business Transaction References
Business transactions reference their documents by URI:
| Transaction Type | Example URL |
|---|---|
| Purchase Order | https://example.com/orders/PO-2025-001 |
| Due Diligence Report | https://example.com/eudr/due-diligence/LOG-2025-001.pdf |
| Certificate | https://fsc.org/en/certificate/FSC-C123456 |
Master Data Linking
Link EPCIS events to master data using masterDataAvailableFor:
{
"epcList": [{
"@id": "https://id.gs1.org/01/09521234000020/21/LOG-2025-001",
"masterDataAvailableFor": {
"@id": "https://id.gs1.org/01/09521234000020/21/LOG-2025-001"
}
}]
}
This pattern indicates that detailed master data can be retrieved by resolving the @id.
Geolocation in URLs
Geolocation data lives in the master data of the plot of land, and the product links to the plot through its identifier:
{
"eudr:originDetails": {
"@id": "https://id.gs1.org/414/9521234000099",
"masterDataAvailableFor": {
"@id": "https://id.gs1.org/414/9521234000099"
}
}
}
Resolving the GLN returns the plot details including polygon coordinates.
Regulatory Reference Numbers
EUIS reference numbers are stored as plain strings:
{
"regulatoryIdentifier": [{
"regulatoryReferenceNumber": "EUIS-2025-DE-00012345",
"regulatoryIdentifierType": "DUE_DILIGENCE_STATEMENT"
}]
}
They follow the format EUIS-{YEAR}-{COUNTRY}-{NUMBER}.
Example URLs by Scenario
Timber Harvest Chain
Along a timber harvest chain, the identifiers fit together as follows:
Plot of Land: https://id.gs1.org/414/9521234000099
Producer: https://id.gs1.org/417/9521234000006
Timber Log: https://id.gs1.org/01/09521234000020/21/LOG-2025-001
Processing Plant: https://id.gs1.org/414/9521234000105
Manufacturer: https://id.gs1.org/417/9521234000105
Furniture: https://id.gs1.org/01/09521234000037/21/TABLE-2025-001
Querying Product History
With these identifiers, the resolver returns product master data, the EPCIS event history and the details of the source plot:
# Get product master data
curl -H "Accept: application/ld+json" \
"https://id.gs1.org/01/09521234000020/21/LOG-2025-001"
# Get EPCIS event history
curl -H "Accept: application/ld+json" \
"https://id.gs1.org/01/09521234000020/21/LOG-2025-001?linkType=epcis"
# Get source plot details
curl -H "Accept: application/ld+json" \
"https://id.gs1.org/414/9521234000099"
Best Practices
Build all identifiers on your GS1 Company Prefix and always include serial numbers, because traceability depends on them. Link master data consistently with masterDataAvailableFor, use the standard link types for content negotiation, and store EUIS references as plain strings.