Digital Facility Record (DFR)

A DFR identifies a physical facility or location — a factory, warehouse, farm, processing plant, or any site involved in your supply chain.

Why DFRs Come First

Facilities are the foundation of your credential ecosystem. Product passports (DPPs) and traceability events (DTEs) reference facilities. Registering your facilities first means your product credentials can properly link to where things are made, stored, or processed.

Creating a DFR

1. Navigate to Toolkit > Credentials > Issue
2. Select DFR as the credential type
3. Fill in the facility details:

Field	Description	Required
Facility Name	Human-readable name (e.g., "Brisbane Processing Plant")	Yes
Address	Street address of the facility	Yes
City	City/suburb	Yes
State/Province	State or province	No
Country	Country	Yes
Postal Code	ZIP/postal code	No
Latitude	Geographic latitude (decimal degrees)	No
Longitude	Geographic longitude (decimal degrees)	No

4. Review the draft
5. Click Issue to sign and publish

Identifiers

DFRs use GLN-13 (Global Location Number) identifiers. These are automatically generated from your organization's 7-digit prefix:

9347823 00001 2
│       │     └── Check digit (GS1 mod-10)
│       └──────── 5-digit counter (auto-incremented)
└──────────────── Your org prefix

You don't need to provide an identifier — DPP Kit generates it for you.

After Issuance

Once issued, the DFR:

• Gets a GLN-13 identifier assigned
• Is signed with your organization's DID
• Is stored in the credential storage service
• Is registered in the Identity Resolver at the GLN path
• Appears in your credential list with status Active

Re-issuing DFRs

DFRs always re-issue to the same resolver path, regardless of whether your organization is in pilot or production mode. This is intentional — a facility's identity shouldn't change, only its details should be updated.

Admin Only

Only organization Admins can create DFR credentials. Editors have read-only access to DFRs.