ISO 25500-100:2026

• Abstract:

  This document supports supply chain interoperability and integration and provides the fundamental structure for exchanging verified data in an industrial internet. Identifiers, like part numbers, are the shorthand for datasets throughout the supply chain. This document provides methods to verify identifiers and datasets behind identifiers used in the supply chain, specifically the format of and automated request types (verify, resolve, and search) and replies to those requests. The following are within the scope of this document: the syntax requirements and application protocol interface (API) for a request and response to a request for the verification of identifiers formatted in accordance with ISO 8000-115 (verify); the syntax requirements and API for a request and response to a request for a dataset of an identifier formatted in accordance with ISO 8000-115 (resolve); the syntax requirements and API for a request and response to a request to search for an identifier formatted in accordance with ISO 8000-115 given characteristic data (search). The following are outside the scope of this document: the methods used for the resolution of identifiers by the identifier issuer; the data elements required for resolution of identifiers.

• Status: Published
• Publication Date: 03-Nov-2026
• ICS: 35.240.63 - IT applications in trade
• Technical Committee: ISO/TC 184/SC 5 - Interoperability, integration, and architectures for enterprise systems and automation applications
• Current Stage: 6060 - International Standard published
• Start Date: 04-Nov-2026
• Completion Date: 04-Nov-2026

ISO 25500-100 is an ISO standard for supply chain interoperability and integration. It specifies how to request and reply to verification, resolution, and search of supply chain data tied to identifiers formatted in accordance with ISO 8000-115, with replies in ISO 8000-114 format where applicable. It is intended for organizations that exchange identifier-based supply chain data through automated, verified interfaces.

What does ISO 25500-100 specify?

ISO 25500-100 specifies the request and response syntax, plus the application interface protocol (API), for exchanging verified supply chain data linked to ISO 8000-115 identifiers. It focuses on three automated processes: verify, resolve, and search.

The document covers:

• terms related to identifiers and the data set used for verification
• request and response syntax for verifying an ISO 8000-115 identifier
• request and response syntax for requesting data behind an ISO 8000-115 identifier
• request and response syntax for searching an identifier from characteristic data
• the API used for these requests and responses

It excludes the methods used by the identifier issuer to resolve identifiers, and the data elements required for that resolution.

Annex	What it covers
Annex A	Document identification, with an object identifier for the standard

What are the key requirements of ISO 25500-100?

ISO 25500-100 defines the minimum structure for automated verification exchanges between verified legal entities in an industrial internet environment. In practice, that means systems need to know what to send, where to send it, and which response codes or data formats to expect back.

1. Clause 4.1 sets the three exchange types

ISO 25500-100 organizes the work into verify, resolve, and search. Verify checks whether an identifier is valid and issued by the named entity, resolve asks for the dataset the issuer is willing to share for that identifier, and search asks the issuer to identify matching identifiers from characteristic data. This gives users three different tools depending on whether they already know the identifier or only know product or item characteristics.

2. Verify requests have a fixed set of fields

ISO 25500-100 requires a verify request to go to the confidential address in the ISO 8000-115 prefix record in the prefix name server (PNS). The request contains the requestor’s registered ISO 8000-115 prefix, the respondent’s registered ISO 8000-115 prefix, and the identifier to be checked. In practice, this lets a buyer or system confirm an identifier before using it in a purchase order or other business transaction.

3. Verify replies return a bounded result set

ISO 25500-100 limits the verify reply to five outcomes: syntax error, data error, request denied, timed out, or verified. That makes the result machine-readable and easy to automate in downstream systems.

4. Resolve replies return shareable data in ISO 8000-114 format

ISO 25500-100 requires a resolve reply to be sent back to the confidential address in the requestor’s PNS record and formatted in ISO 8000-114. A successful resolve reply can carry data in .idf form. In practice, this is the exchange used when the requester needs the dataset behind the identifier rather than just a yes-or-no check.

5. Search uses characteristic data to find identifiers

ISO 25500-100 requires a search request to carry item characteristic data instead of an identifier. The reply can return one or more quality identifiers, or one of the same status outcomes used by the other exchanges. This is useful when the requester knows the attributes of an item but not its identifier.

6. Conformance is based on applying the specified request and reply clauses

ISO 25500-100 states that conformance is achieved when the specified request and reply provisions in Clause 4 are applied. For implementers, this means interoperability depends on following the defined message structure and response behavior, not on a free-form exchange.

What terms does ISO 25500-100 define?

ISO 25500-100 uses several key terms from its ISO 25500 vocabulary context.

• Quality identifier - A definitive, resolvable identifier that includes a prefix element for the issuing legal entity and an identifier element for the object and its data.
• Prefix name server (PNS) - The server that holds prefix records and the confidential addresses used to route verification exchanges.
• International part number (IPN) - A part number in ISO 8000-115 format that can be resolved through a prefix record in a PNS.
• International business identifier (IBID) - The verified business identifier of the prefix owner made visible in prefix records.
• Requestor - The party that sends the request for verification, resolution, or search.
• Identifier issuer - The party that issued the identifier and receives the request.
• Respondent - The party named in the request as the one to which the request is addressed.

Who uses ISO 25500-100?

ISO 25500-100 is used by supply chain, procurement, manufacturing, warehousing, order processing, and logistics teams that need automated identifier checks. It is also relevant to trading partners that exchange data across companies and borders, and to organizations working on know your customer (KYC), know your supplier (KYS), and know your item (KYI) processes.

In practice, buyers can use verify before placing orders, data teams can use resolve to obtain the dataset behind an identifier, and master data teams can use search to find identifiers from item characteristics.

Which standards are used with ISO 25500-100?

ISO 25500-100 is used with:

• ISO 8000-114 - provides the format used for replies to resolve requests.
• ISO 8000-115 - provides the identifier syntax and the syntactic, semantic, and resolution requirements that the requests are built around.
• ISO 25500-2 - provides the vocabulary used for the terms in this part.
• ISO 25500-1 - provides the overview and principles of the industrial internet referenced in the introduction.
• ISO 10303-1 - defines the meaning of the object identifier used in Annex A.
• ISO/IEC 8824-1 - gives the ASN.1 notation referenced in the bibliography.

What does the ISO 25500-100 document contain?

ISO 25500-100 contains the scope, normative references, terms and definitions, the main process description for verify, resolve, and search, and a conformance clause. It also includes Annex A for document identification and a bibliography.

The core content is the request and reply structure for each exchange type, together with the expected response categories and the use of confidential routing through the PNS. Annex A adds an object identifier for unambiguous identification of the document in an open information system.

International
Standard
ISO 25500-100
First edition
Supply chain interoperability and
2026-11
integration —
Part 100:
Verification of supply chain data
Interopérabilité et intégration dans la chaîne
d'approvisionnement —
Partie 100: Vérification des données de la chaîne
d'approvisionnement
Reference number
© ISO 2026
All rights reserved.
This ISO publication is protected by copyright and is owned by ISO and/or its licensors.
The content of this ISO publication is provided under licence, not sold. Use is subject to the applicable licence terms issued by ISO,
an ISO member body, or an authorized third-party distributor.
Except as required for implementation or expressly permitted by a separate licence, no part of this ISO publication may be
reproduced, distributed, modified, used, or made available in any form or by any means – electronic or mechanical, including
photocopying, scanning, recording, or posting on internal or external digital platforms.
Any use beyond the scope of the granted rights is prohibited and may result in legal action.
ISO copyright office
CP 401 • CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Supply chain data: verification, resolution, and search processes . 2
4.1 General .2
4.2 Verify: request and reply for identifier verification .2
4.2.1 Request for identifier verification .2
4.2.2 Reply to request for identifier verification .2
4.3 Resolve: request and reply for dataset identifier represents .2
4.3.1 Request to resolve identifier to dataset .2
4.3.2 Reply to request to resolve identifier to dataset .3
4.4 Search: request for identifier .3
4.4.1 Request to search for identifier given characteristic data .3
4.4.2 Reply to request to search for identifier given characteristic data .3
5 Conformance . 3
Annex A (informative) Document identification . 4
Bibliography . 5

iii
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO’s adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 5, Interoperability, integration, and architectures for enterprise systems and automation
applications.
A list of all parts in the ISO 25500 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

iv
Introduction
The supply chain needs standard solutions to increase the effectiveness, efficiency, and security of business
through greater interoperability and integration across applications, facilities, companies, and borders.
Supply chain data is understood through identifiers; identifiers (for parts, products, services, materials,
certifications, legal entities, etc.) are found in every process of the supply chain from procurement to
warehousing, making, order processing, and logistics. Identifier resolution is essential to meeting know
your customer (KYC), know your supplier (KYS), and know your item (KYI) requirements. For interoperable,
integrated, sustainable, and efficient supply chains, identifiers and the datasets they represent need to be
verified through automated processing.
ISO 8000-115 describes a quality identifier as definitive, resolvable, and consisting of a prefix element
to represent the legal entity that issued the identifier and the identifier element assigned by the owner
to represent the object and the data describing it, along with any use restrictions. A part number in
ISO 8000-115 format, called an international part number (IPN), can be resolved through looking up the
prefix owner in a prefix record in an ISO 8000-115 prefix name server (PNS) and the addresses in that prefix
record can be used to request resolution of the part number.
The ability to verify the validity of and data represented by an identifier to support business
...