# EDIFACT PARTIN: Party Information Message Guide

> EDIFACT PARTIN explained: how GLNs, store and DC addresses, delivery windows and parent links travel in EANCOM, with two examples and the X12 816 mapping.

<QuickAnswer>
EDIFACT PARTIN is the party information message, the closest equivalent of the X12 816. A trading partner sends it to set up or update the locations it trades from: each GLN with its name, address, function, parent organisation, contacts, bank and VAT details, and delivery schedule. BGM+10 identifies it, and one NAD group describes each location.
</QuickAnswer>

**PARTIN is the message that tells you what a GLN on an order actually means.** An EANCOM order names its delivery point as a 13-digit Global Location Number and nothing else. Your system can only ship it if that GLN is already on file with an address, a delivery window and the right parent account. PARTIN is how that location data arrives as EDI, and how it stays current when stores open, move or close.

This guide follows the [GS1 EANCOM 2002 PARTIN](https://www.gs1.org/sites/default/files/docs/eancom/ean02s3/part2/partin/toc.htm) layout: directory D.01B, subset version EAN009. EANCOM 2002 is GS1's current edition and the basis of the other EDIFACT guides on this site. A partner still on EANCOM 1997 will send D.96A, and its `UNH` segment says which.

<EDIGuideCTA
  badge="For EDIFACT PARTIN"
  transactionType="PARTIN"
  headline="Turn GLNs on orders into real delivery addresses"
  body="Paste a PARTIN into the free EDIFACT inspector to check the envelope, UNT count and every GLN check digit. OrderSync reads inbound orders in any format, from EDIFACT ORDERS and X12 850s to PDFs and emails, and matches each ship-to to the right customer location in your ERP."
  secondaryHref="/edifact-inspector"
  secondaryLabel="Try the free EDIFACT inspector"
/>

## What Is an EDIFACT PARTIN?

**PARTIN (party information) is the UN/EDIFACT message for "the transmission of basic information regarding locations and the related operational, administrative, commercial and financial data", as GS1 defines it.** It maintains each partner's master data file of locations, so that later messages can refer to a location by its number alone.

GS1 calls PARTIN "the first message exchanged between trading partners at the beginning of a commercial relationship", to be sent again whenever the details change. Its principles cover:

- **Physical and functional locations.** A store and a distribution centre are physical locations. An accounts payable department or an ordering desk is a functional location. Both get a GLN and both can be described.
- **One function per message.** GS1 requires a separate message for each message function: an addition, a change and a deletion go in three PARTINs, not one.
- **Central address catalogues.** Partners can use PARTIN to feed a central catalogue of addresses that other parties read.

**Who sends it?** Whichever side owns the locations. In retail that is usually the buyer sending its stores and DCs to suppliers. A supplier can also send its own despatch points, invoicing party and bank details.

**When?** At onboarding, then each time a location is added, changed or closed.

**Why does it matter?** An order to a GLN you do not hold cannot be shipped without someone looking it up. An order to a GLN with an out-of-date address gets shipped to the wrong place.

In practice PARTIN is less common than ORDERS or INVOIC. Many retailers send location lists as spreadsheets or portal downloads instead. Ask during onboarding which route your partner uses. For the full list of EDIFACT messages, see [EDIFACT message types](/guides/edi/edifact-message-types).

## PARTIN, GLNs and Location Master Data

A GLN is only a key. GS1 says a GLN can identify a legal entity, a function, a physical location or a digital location, and the [GS1 GLN standard](https://www.gs1.org/standards/id-keys/gln) sets management rules for what happens when a location is new, splits, merges, changes purpose, moves or changes name. None of that data is inside the number itself. It lives in each partner's location master file, and something has to keep the two files in step.

| Source of location data | How it reaches you | Good for |
|---|---|---|
| **PARTIN** | EDIFACT message from the partner | Full location records with addresses, functions, parents, schedules and bank or tax details |
| **[X12 816](/guides/edi/816-organizational-relationships)** | X12 message from the partner | The same job in North American retail |
| **TRADACOMS `CUSHDR`** | TRADACOMS customer information file | UK retailers still on TRADACOMS |
| Spreadsheet or supplier portal | File download, often monthly | Partners that do not send location data as EDI |
| GS1 lookup services | Look up a GLN yourself | Checking who a GLN belongs to; coverage varies by country and service |

Whatever the source, key your records on the GLN, store the partner's own store or DC number beside it, and validate every GLN's check digit before loading. The [check digit calculator](/tools/check-digit-calculator) validates a whole column of GLNs from a CSV.

## Example 1: A New Store and a New Distribution Centre

The fictional retailer Calder Row Markets (head office GLN 5412345000013) tells its supplier Ashby Mill Bakery (GLN 5412345000020) about two new locations. Store 0218 opens on 23 November 2026 and orders for itself. A new northern DC starts receiving on 16 November. Both sit under the head office. All GLNs use GS1's documented example prefix 5412345 with valid check digits; the addresses and postcodes are fictional.

<EdifactSample
  title="PARTIN adding a new store and distribution centre"
  description="BGM function 2 (addition): two NAD groups with addresses, start dates, IDE functions, HYN parent links, store numbers and delivery schedules."
  label="EANCOM D.01B EAN009"
  raw="UNA:+.? '
UNB+UNOC:3+5412345000013:14+5412345000020:14+261102:1400+CRM00402'
UNH+1+PARTIN:D:01B:UN:EAN009'
BGM+10+CRM-PI-0331+2'
DTM+137:20261102:102'
NAD+FR+5412345000013::9'
NAD+MR+5412345000020::9'
UNS+D'
NAD+SN+5412345000037::9++CALDER ROW MARKETS 0218+14 BRIDGE STREET+CALDERBRIDGE++ZZ1 4QT+GB'
DTM+194:20261123:102'
IDE+OB'
IDE+ST'
HYN+PA+1++5412345000013:GLN::9'
RFF+YC1:0218'
CTA+OC+:STORE 0218 ORDERING'
COM+orders0218@calderrow.example:EM'
SCC+1++W:11:D'
NAD+DP+5412345000044::9++CALDER ROW MARKETS NORTH DC+UNIT 7 MOORSIDE ESTATE+CALDERBRIDGE++ZZ1 8LN+GB'
DTM+194:20261116:102'
IDE+ST'
HYN+PA+1++5412345000013:GLN::9'
RFF+YC1:DC02'
SCC+1++Y:10:H'
DTM+2:06001400:501'
UNT+23+1'
UNZ+1+CRM00402'"
/>

| Segment | What it says |
|---|---|
| `BGM+10+CRM-PI-0331+2'` | Document `10` (party information), number CRM-PI-0331, function `2` (addition: new parties) |
| `NAD+FR` / `NAD+MR` | Message from the head office, to the supplier |
| `UNS+D'` | End of the heading, start of the detail section |
| `NAD+SN+5412345000037::9++...'` | A store, by GLN, with its name and structured address |
| `DTM+194:20261123:102'` | The location's start date |
| `IDE+OB'` and `IDE+ST'` | Its functions: it places orders, and goods are shipped to it |
| `HYN+PA+1++5412345000013:GLN::9'` | Its parent in the party hierarchy is the head office |
| `RFF+YC1:0218'` | Additional party identification: the retailer's own store number |
| `CTA+OC` / `COM` | The order contact and an email address |
| `SCC+1++W:11:D'` | Firm delivery schedule: weekly pattern, Monday to Saturday, mornings |
| `NAD+DP+5412345000044::9++...'` | The DC, as a delivery party |
| `SCC+1++Y:10:H'` then `DTM+2:06001400:501'` | Daily, Monday to Friday, with a requested delivery window of 06:00 to 14:00 |
| `UNT+23+1'` | 23 segments from `UNH` to `UNT` inclusive |

The order of segments inside each location group is fixed by the message structure: `NAD`, `DTM`, `FII`, `IDE`, `FTX`, `TAX`, `HYN`, then the `LOC`, `RFF`, `CTA`/`COM`, `SCC`, `TOD`, payment, characteristic and process groups. A strict translator can reject segments sent out of this order.

## Example 2: A Store Closing

Six weeks later, store 0146 is closing on 31 December. Calder Row sends a change (function `4`) that adds an end date to the location. Under GS1's rules for a change, only segments with modified data are sent, so the message is short.

<EdifactSample
  title="PARTIN change adding a store closing date"
  description="BGM function 4 (change): only the store GLN and its DTM+206 end date are sent."
  label="EANCOM D.01B EAN009"
  raw="UNA:+.? '
UNB+UNOC:3+5412345000013:14+5412345000020:14+261104:1100+CRM00409'
UNH+1+PARTIN:D:01B:UN:EAN009'
BGM+10+CRM-PI-0336+4'
DTM+137:20261104:102'
NAD+FR+5412345000013::9'
NAD+MR+5412345000020::9'
UNS+D'
NAD+SN+5412345000051::9'
DTM+206:20261231:102'
UNT+9+1'
UNZ+1+CRM00409'"
/>

| Segment | What it says |
|---|---|
| `BGM+10+CRM-PI-0336+4'` | Function `4` (change): modifies a party the supplier already holds |
| `NAD+SN+5412345000051::9'` | The store being changed, identified by GLN only |
| `DTM+206:20261231:102'` | End date for this location: 31 December 2026 |

When the store has actually closed and the partner wants the record gone, it sends function `3` (deletion) in a separate message. Do not delete a location the moment you receive an end date: open orders, deliveries and invoices can still reference it, and GS1's GLN rules restrict reusing a GLN once it is retired.

## PARTIN Structure at a Glance

Status and repeats follow the EANCOM 2002 structure chart. M is mandatory, C conditional.

| Section | Segment | Name | Status | Repeats | Carries | X12 816 equivalent |
|---|---|---|---|---|---|---|
| Heading | `UNH` | Message header | M | 1 | `PARTIN:D:01B:UN:EAN009` | `ST` |
| Heading | `BGM` | Beginning of message | M | 1 | `10`, number, function | `BHT` |
| Heading | `DTM` | Date/time/period | M | 5 | `137` message date, `194`/`206` validity | `DTM` |
| Heading | `FII`, `FTX` | Bank details, free text | C | 10 / 5 | Sender-level details | |
| SG1 | `RFF`, `DTM` | Reference | C | 5 | A previous message, for replace or cancel | `REF` |
| SG2 | `NAD` | Name and address | C | 2 | `FR` from, `MR` recipient | Heading `N1` loop |
| SG3 | `CTA`, `COM` | Contact | C | 5 | Sender's contact | `PER` |
| Heading | `UNS` | Section control | M | 1 | `UNS+D` | |
| SG4 | `NAD` | Name and address | M in group | 200000 | One location per group | Detail `HL` and `N1` loops |
| SG4 | `DTM` | Date/time/period | C | 5 | `194` start, `206` end | `DTM` |
| SG4 | `FII` | Financial institution | C | 10 | Bank account for this party | |
| SG4 | `IDE` | Identity | C | 9 | The location's functions | `N101` entity code |
| SG4 | `TAX` | Duty/tax/fee details | C | 9 | Usual VAT situation | |
| SG4 | `HYN` | Hierarchy information | C | 9 | Parent or child GLN | `HL02` parent ID |
| SG5 | `LOC` | Place/location | C | 99 | Coordinates when no address exists | |
| SG6 | `RFF`, `DTM` | Reference | C | 15 | VAT number, store number, registration | `REF` |
| SG7 | `CTA`, `COM` | Contact | C | 5 | Order or sales contact | `PER` |
| SG8 | `SCC`, `DTM` | Scheduling conditions | C | 10 | Delivery days and windows | |
| SG9 | `TOD`, `LOC` | Terms of delivery | C | 1 | Delivery terms for this party | |
| SG10 | `PAI`, `PAT`, `CUX` and more | Payment details | C | 999 | Payment terms for this party | |
| SG13 | `PRC`, `LIN`, `NAD`, `DOC` | Process identification | C | 999 | Who does what in a business process | |
| Summary | `UNT` | Message trailer | M | 1 | Segment count | `SE` |

PARTIN has no `CNT` and no summary `UNS`. The detail section ends with the last location group and goes straight to `UNT`.

## Key Segments Explained

### BGM: Message Function

```
BGM+10+CRM-PI-0331+2'
```

| Code (1225) | Meaning in EANCOM PARTIN |
|---|---|
| `9` | Original transmission |
| `2` | Addition: new parties, or existing parties sent to this partner for the first time |
| `4` | Change: only segments with modified data are sent, each with all its previous data and all its repetitions |
| `3` | Deletion: remove the party records from the receiver's file |
| `5` | Replace a previous message, identified in the heading `RFF` |
| `1` | Cancellation of a previous message, identified in `RFF` |
| `6` | Confirmation: party data sent again to confirm it |

The document code in the first element is always `10` (party information).

### NAD: The Location

```
NAD+SN+5412345000037::9++CALDER ROW MARKETS 0218+14 BRIDGE STREET+CALDERBRIDGE++ZZ1 4QT+GB'
```

| Element | Example | What it means |
|---|---|---|
| 3035 | `SN` | Party function. See the qualifier table below |
| C082 / 3039 | `5412345000037` | The GLN. GS1 recommends GLN, format n13 |
| C082 / 3055 | `9` | Code list agency: GS1 |
| C080 | `CALDER ROW MARKETS 0218` | Party name in clear text |
| C059 | `14 BRIDGE STREET` | Street |
| 3164 | `CALDERBRIDGE` | City |
| 3251 | `ZZ1 4QT` | Postal code |
| 3207 | `GB` | ISO 3166 country code |

Detail-level `NAD` qualifiers in EANCOM 2002 PARTIN:

| Qualifier | Meaning |
|---|---|
| `BY` | Buyer |
| `SU` | Supplier |
| `DP` | Delivery party |
| `SN` | Store number |
| `IV` | Invoicee |
| `DGB` | Invoice processing party |
| `DFZ` | Article information responsible party |
| `DGA` | Price information responsible party |
| `SR` | Supplier's agent or representative |
| `IPA` | Party information party (GS1 temporary code) |
| `X48` | Corporate identity (GS1 temporary code) |

In the heading, only `FR` (message from) and `MR` (message recipient) are used, and GS1 makes both mandatory.

### IDE: What the Location Does

```
IDE+OB'
IDE+ST'
```

`IDE` adds functions to the party named in `NAD`. One location can have several: a store can order (`OB`), receive goods (`ST`) and be invoiced (`IV`). EANCOM lists `BY`, `CO` (corporate office), `DP`, `II` (issuer of invoice), `IV`, `NFP` (no function priority), `OB`, `PE` (payee), `PR` (payer), `QP`, `SE`, `SF` (ship from), `SH`, `ST`, `SU` and `X48`. Map these to the roles your ERP holds against a customer: sold-to, ship-to, bill-to and payer.

### HYN: Parent and Child Locations

```
HYN+PA+1++5412345000013:GLN::9'
```

| Element | Example | What it means |
|---|---|---|
| 7173 | `PA` | Party or location hierarchy link (GS1 temporary code) |
| 7171 | `1` | The GLN in this segment is the **parent** of the party in `NAD`. `2` would make it a child |
| C212 / 7140 | `5412345000013` | The related GLN |
| C212 / 7143 | `GLN` | Item type: Global Location Number |
| C212 / 3055 | `9` | GS1 |

The fourth element (1229) is empty; the GLN sits in the fifth. GS1's own worked example in the PARTIN manual puts the GLN one position early, but its segment layout and segment example both use the position shown here, so follow the layout and check your partner's sample files.

### RFF: Store Numbers and Registration Numbers

```
RFF+YC1:0218'
```

`YC1` (additional party identification, a GS1 temporary code) carries the partner's own number for the location, such as a store or DC number. Other qualifiers include `VA` (VAT registration number), `FC` (fiscal number), `XA` (company or place registration number), `CR` (customer reference number) and approval numbers for slaughterhouses and meat cutting plants. Store the `YC1` value alongside the GLN; some orders and paper documents will use only the store number.

### SCC and DTM: Delivery Schedules

```
SCC+1++Y:10:H'
DTM+2:06001400:501'
```

| Element | Example | What it means |
|---|---|---|
| `SCC` 4017 | `1` | `1` firm, `4` planning or forecast |
| `SCC` 4493 | (empty) | Optional: `DA` do not deliver after, `DB` do not deliver before |
| `SCC` 2013 | `Y` | Frequency: `Y` daily, `W` weekly, `M` monthly, `Q` quarterly, `S` semi-annually |
| `SCC` 2015 | `10` | Pattern: `10` Monday to Friday, `11` Monday to Saturday, `12` Monday to Sunday, `13` to `17` single weekdays |
| `SCC` 2017 | `H` | Timing: `D` morning, `E` afternoon, `H` 24-hour clock |
| `DTM` 2005 | `2` | Requested delivery date/time. Also `4` order date/time, `63` latest, `64` earliest |
| `DTM` 2379 | `501` | Format `HHMMHHMM`: a time window, here 06:00 to 14:00 |

Delivery windows from PARTIN are worth loading into your transport planning. What happens to a delivery outside the window is set by the trading agreement, not by EANCOM.

### FII and TAX: Bank and VAT Details

`FII` gives the bank account for the party (`PB` paying or `RB` receiving financial institution) and `TAX` its usual tax situation, for example `TAX+7+VAT+++:::20+S'` for a standard-rated party. Bank details in PARTIN deserve the same care as any change of bank details: confirm a new or changed account through a channel you already trust before you pay to it. VAT numbers in `RFF+VA` can be checked with the [VAT number checker](/tools/vat-number-checker).

## PARTIN vs the X12 816 and TRADACOMS CUSHDR

In TRADACOMS, location master data travels in the customer information file: a `CUSHDR` header with `CUSINF` detail messages. The table below compares PARTIN with the X12 816 field by field.

| Data | EDIFACT PARTIN | X12 816 |
|---|---|---|
| Message | `UNH` `PARTIN` | `ST*816` |
| Purpose of the file | `BGM` function: `2`, `4`, `3`, `9` | `BHT` purpose code, for example `00` original or `04` change |
| Sender | `NAD+FR` | Heading `N1*FR` |
| One location | `NAD` group (SG4) | `HL` loop with `N1` |
| Location ID | GLN in `NAD` C082 | `N103` qualifier and `N104`, for example `UL` with a GLN |
| Store number | `RFF+YC1` | `REF` |
| Address | `NAD` structured name and address | `N3`, `N4` |
| Parent | `HYN+PA+1` | `HL02` parent ID |
| Function | `IDE` | `N101` entity identifier code |
| Effective dates | `DTM+194` / `DTM+206` | `DTM` |
| Contact | `CTA`, `COM` | `PER` |
| Delivery schedule | `SCC` group | No dedicated segment in the 816 |

The biggest difference is how the hierarchy is built. The 816 nests locations under parents with `HL` levels, so the parent usually comes before its children in the file. PARTIN lists each location flat and points to its parent by GLN in `HYN`, so a child can arrive before its parent or in a different message. Load all locations first, then resolve the parent links.

Some mapping tables pair PARTIN with the X12 838 trading partner profile. In retail, the 816 is the closer match: both carry a partner's location list. The [EDI 816 guide](/guides/edi/816-organizational-relationships) covers the X12 side, and [TRADACOMS file types](/guides/edi/tradacoms-file-types) lists `CUSHDR`.

## Where PARTIN Sits in the Flow

| Step | Message | What it depends on |
|---|---|---|
| 1 | **PARTIN** | The partner's location master |
| 2 | [PRICAT](/guides/edi/edifact-pricat) | Your product master and agreed prices |
| 3 | [ORDERS](/guides/edi/edifact-orders) | GLNs from step 1 and GTINs from step 2 |
| 4 | [DESADV](/guides/edi/edifact-desadv) | The delivery point GLN from the order |
| 5 | [INVOIC](/guides/edi/edifact-invoic) | The invoicee and buyer GLNs on file |

PARTIN and PRICAT are master data: they come before the order cycle and make it possible. If either is missing or stale, the symptom shows up later, as an order for an unknown delivery point or an invoice sent to the wrong invoicee.

## Common PARTIN Errors and Fixes

| Problem | What you see | Fix |
|---|---|---|
| GLN check digit wrong | Location fails to load, or loads under a mistyped key | Validate every GLN before loading |
| Order to an unknown GLN | An ORDERS message references a delivery point you do not hold | Ask for a PARTIN, or the partner's location file, before go-live; hold the order rather than guessing |
| Change treated as a full record | Fields you hold are blanked | Under function `4`, only changed segments arrive. Update those and keep the rest |
| Mixed functions in one message | Additions and deletions in the same PARTIN | GS1 requires one message per function. Ask the partner to split them |
| Deleting on an end date | Open orders and invoices lose their location | Keep the record until the end date has passed and open documents are closed |
| Parent not found | `HYN` points to a GLN not yet loaded | Load all `NAD` groups first, then resolve `HYN` links |
| Store number lost | Paper documents or portals quote a number you cannot match | Store `RFF+YC1` beside the GLN |
| Wrong `UNT` count | Translator rejects the message | Count every segment from `UNH` to `UNT` inclusive |

## PARTIN Implementation Checklist

1. Ask whether the partner sends location data by PARTIN, another EDI message, a spreadsheet or a portal.
2. Get its PARTIN guide and confirm the directory, the EANCOM version in `UNH`, and which `NAD`, `IDE` and `RFF` qualifiers it uses.
3. Decide how each function maps to your customer roles: sold-to, ship-to, bill-to, payer.
4. Key every location on GLN, with the partner's store or DC number alongside.
5. Handle additions, changes and deletions as separate flows, and keep closed locations until their documents are settled.
6. Route bank detail changes to a person for confirmation.
7. Check each test file's envelope, `UNT` count and GLN check digits in the [EDIFACT inspector](/edifact-inspector).

## Where OrderSync Fits

OrderSync does its work on the orders that use these locations. It reads inbound orders in any format, including EDIFACT ORDERS, X12 850s, PDFs, emails and spreadsheets, and matches each customer, ship-to, item and unit to the records in your ERP before the order is created.

The free [EDIFACT inspector](/edifact-inspector) checks PARTIN files, and the [EDI inspector](/edi-inspector) does the same for an X12 816. To see order matching on your own customers' orders, [book a 15-minute walkthrough](/book-call).

## Frequently Asked Questions

<div className="not-prose">

### What is PARTIN in EDI?

PARTIN is the UN/EDIFACT party information message. A trading partner uses it to send master data about its locations: GLNs, names and addresses, functions such as delivery point or invoicee, parent organisations, contacts, bank and tax details, and delivery schedules.

### What is the X12 equivalent of PARTIN?

The closest is the X12 816 Organizational Relationships, which retailers use to send store and DC lists. Some mapping tables pair PARTIN with the X12 838 trading partner profile, but for location master data the 816 is the usual match.

### What is a GLN in a PARTIN message?

A Global Location Number is a 13-digit GS1 identifier for a legal entity, function, physical location or digital location. In PARTIN it sits in the NAD segment with agency code 9, and the rest of the message describes what that GLN is.

### How do I add a new store with PARTIN?

Send a PARTIN with BGM function 2 (addition), and one NAD group for the store with its GLN, address, start date in DTM+194, its functions in IDE, and its parent in HYN.

### How is a closed location shown in PARTIN?

A change message (BGM function 4) can add an end date with DTM+206. A deletion message (function 3) removes the party record. GS1 requires a separate message for each function.

### Is PARTIN widely used?

Less than ORDERS, DESADV or INVOIC. GS1 positions it as the first message in a new relationship, but many retailers share location lists through portals or spreadsheets. Check each partner's onboarding pack.

### What is the TRADACOMS equivalent of PARTIN?

The customer information file, CUSHDR, with CUSINF detail messages. It carries the customer's locations so that the location codes on its orders resolve to real addresses.

</div>

## Related guides

- **[EDIFACT explained](/guides/edi/edifact)**: syntax, envelopes and the full X12 mapping
- **[EDIFACT ORDERS](/guides/edi/edifact-orders)**: the orders that quote these GLNs
- **[EDIFACT PRICAT](/guides/edi/edifact-pricat)**: the product master that sits beside PARTIN
- **[EDIFACT DESADV](/guides/edi/edifact-desadv)**: despatch advice to the delivery point
- **[EDI 816 organizational relationships](/guides/edi/816-organizational-relationships)**: the X12 counterpart
- **[TRADACOMS file types](/guides/edi/tradacoms-file-types)**: CUSHDR and the rest of the UK files
- **[EDIFACT message types](/guides/edi/edifact-message-types)**: every message and its X12 equivalent

## Sources

- [EANCOM 2002 S3: PARTIN party information message](https://www.gs1.org/sites/default/files/docs/eancom/ean02s3/part2/partin/toc.htm), GS1: structure chart, segment layouts, code lists and worked example
- [EANCOM 2002 S3 Part I: message descriptions](https://www.gs1.org/sites/default/files/docs/eancom/ean02s3/part1/part1_02.htm), GS1
- [Global Location Number (GLN)](https://www.gs1.org/standards/id-keys/gln), GS1: what a GLN identifies and the GLN management rules
- [UN/EDIFACT D.01B PARTIN message](https://service.unece.org/trade/untdid/d01b/trmd/partin_c.htm), UNECE

Check any PARTIN's structure, counts and GLN check digits in the free [EDIFACT inspector](/edifact-inspector).