Skip to content

Register facilities

To trace and share product information with your IBM Food Trustâ„¢ supply chain partners, you must first register your organization's facilities (locations). A registered facility can be any physical location with a unique ID, including farms, processing plants, warehouses, and packaging centers. Sublocations, or zones within a facility, are also supported. Multiple facilities can be defined at the same physical location and address, as long as each one has a unique identifier. An IBM Food Trust product ID is required to register each facility; this ID can be either a GS-1 GTIN and URN or an IBM Food Trust identifier.

IBM Food Trust supports multiple GS-1 Facility ID formats, including the GS-1 URN format. If your facility is not registered with GS-1, you can request an IBM Food Trust facility ID. Once you have your IBM Food Trust facility IDs, register each facility using one of the methods described below.

Watch the video

Please take two minutes and watch the facility registration video to preview the steps for adding your facilities to IBM Food Trust.

GDPR notice

Attention: To comply with EU General Data Protection Regulation (GDPR) data privacy requirements, you must ensure that no personal data is uploaded to IBM Food Trust in any free-form text fields or in any comments.

Registration methods

As shown in the video, you can quickly register facilities using the UI Onboarding Module. Note: The identical facility registration functionality is also available in the UI Data module.

As an alternative to the UI, your Data integration experts may choose to use the Spreadsheets method or the Connector API method to register large numbers of facilities.

Using the UI

Use the Onboarding module or the Data module to quickly register your facilities.

Using spreadsheets

Use the UI Spreadsheet templates page to register your facilities using Microsoft® Excel&tm; files. After downloading and completing your spreadsheets, you will submit them to the Converter API for conversion to XML and uploading to IBM Food Trust.

Refer to the Using spreadsheets documentation for complete usage details.

Using the Connector API

To register facilities using the Connector API, you will use the XML Master Item Data type. The Master Item Data message type is derived from the GS1 Item Data Notification XML message type, and is used for registering locations (facilities) on IBM Food Trust.

Master item data is class-level master data corresponding to a GLN (Global Location Number) or IBM Food Trust facility ID, is typically uploaded by the creator of the facility in IBM Food Trust, and consists of the following data points:

To use the following Master item data example XML, replace the bold items with your information:

The following XML shows the specific mandatory and optional fields in the annotated facility master data file:

<?xml version="1.0" encoding="UTF-8"?>
    xmlns:xsi="" xsi:schemaLocation="urn:gs1:gdsn:basic_party_registration:xsd:3 ../Schemas/gs1/gdsn/BasicPartyRegistration.xsd">
            <sh:Identifier Authority="GS1">8712345678913</sh:Identifier>
            <sh:Identifier Authority="GS1">9712345678912</sh:Identifier>
            <!--Mandatory, but can be left empty.-->
    <!--Party here refers to a Facility, as well.-->
        <!--MANDATORY: isPartyActive will be set to False, if a facility is closed etc.-->
        <!--MANDATORY: Organization's corporate identity GLN-->
        <!--MANDATORY: GLN or IBM Food Trust Facility ID of the party (location) being registered-->
        <!--IBM Food Trust Facility ID format: urn:ibm:ift:location:loc:<Company Prefix>.<Location Reference>-->
            <!--MANDATORY: This section is Mandatory; However, some of the fields below are optional.-->
            <!--MANDATORY: ISO 3166-1 numeric-3 code>
            <!--Numeric-3 country codes offer script-independence, and are consistent with GDSN 3.1.-->
            <name>Mondial Distribution</name>
            <!--MANDATORY: Name of the facility-->
            <!--ISO 639-1 alpha-2 code>
            <!--Use complete state name, if applicable.-->
            <streetAddressOne>1 Peachtree Avenue</streetAddressOne>
            <streetAddressTwo>Suite 911</streetAddressTwo>
            <!--MANDATORY: The section below describes the role that this location/facility is playing.-->
            <!--For example, whether this is a DC or a store or corporate-identity, etc.-->
            <!--MANDATORY: Name of the owning entity.-->
            <!--MANDATORY: Role of this facility.-->
            <!--Value from standard GS1 code-list: -->
            <!--Use partyRoleCode=CORPORATE_IDENTITY for organization's identity/headquarters.-->
            <!--A value from the IBM Food Trust custom partyRole code-list can also be used:-->
            <!-- -->
            <!--Note: The IBM Food Trust custom code-list includes the standard GS1 code-list as a subset.-->

Once you have created your XML, use the Connector API to register your products with IBM Food Trust. You must authenticate first to use the Connector API via Swagger. Without this step, all attempts will result in a 401 Not Authorized error. After authenticating successfully, Swagger will redirect you to an authenticated session; Swagger only notifies users in the case of authentication failures.

When calling the Connector API outside of Swagger, (e.g. via curl, postman or programmatically), you must include your access token in the Authorization header of the request. For example, for access token xyz**, specify Bearer xyz in the Authorization header.

For compliance with data privacy laws, including GDPR, do not submit any data that personally identifies an individual to IBM Food Trust.

Attention: Clicking the Swagger Try it out button submits your API call to the IBM Food Trust network and permanently writes your data to the blockchain ledger. This is not a test.

Implementation notes

  • An IBM Food Trust asset is data that has been uploaded, by an authorized user, as one of the supported document types. Call the Asset endpoint to create an asset for the following data types: Purchase Order, Despatch Advice, Receive Advice, EPCIS Events, Master Data Item, or Master Data Facility.
  • Refer to the supported schema and example XML data types as needed. IBM Food Trust verifies the submitted XML with the corresponding schema. The response will describe any errors.
  • Review Data entitlement mode for details on sharing data with your IBM Food Trust supply chain partners.
  • Review Cryptographic signatures for details on signing XML documents for authenticity and chain of custody.
  • Response Class (Status 201) Asset Creation Submitted - A successful response will return an array of URNs. A URN will be in the format urn:ibm:provenance:asset:layer:label:org:channel:namespace:instance. Please ensure these URNs are retained.

Connector API - upload XML

Use the following procedure to upload XMl through the Connector API:

  1. Log in to the Connector API:
    Figure 1. Connector API
    Swagger Connector API
  2. Select Authenticate here first to log in to the environment with your IBMid:
    Figure 2. Swagger authentication
    Swagger authentication
  3. Select your organization and authenticate with your IBMid. Then select "Expand Operations" from the bottom right:
    Figure 3. Swagger expand
    Swagger expand
  4. Click Expand operations for the Assets endpoint:
    Figure 4. Swagger expanded options
    Swagger options
  5. Edit the mandatory fields, and any optional fields, in your XML file:
    Figure 5. Swagger XML Master data example
    Swagger XML
  6. Paste your XML into the Asset field, under Parameters:
    Figure 6. Swagger XML pasted into asset field
    Swagger asset XML
  7. Optionally, set the data entitlement mode, which dictates which of your supply chain partners can view the uploaded data. On Swagger the default value is None, which means data sharing defaults to your organization's data access control policy.
  8. Click the Try it Out button. If successful, the data will upload to IBM Food Trust with a response code of "201":
    Figure 7. Swagger Try it out! button Swagger Try it out

A response of 201 is returned for a successful data upload; anything other than 201 indicates the described error:
Figure 8. Swagger Try it out success
Swagger Try it out expanded

Error 400

If the body content is malformed or missing any required fields, a 400: Bad Request response error will be returned with JSON describing the error:
Figure 9. Swagger input error example
Swagger error


{ "message": "XML document structures must start and end within the same entity.", "traceId": "8e26df0c-e769-46a4-a066-b66189922f50" }