Skip to main content
Skip table of contents

eECD Product master data

To ensure common and consistent product master data are being exchanged the following product master data structure has been agreed. As explained above the product master data and specific product articles do also refer to meta data like safety data sheets and product loading location data.

Field

Type

Description / comments

internalProductID

GUID

Internal reference, automatically attributed by the platform

sellerId

GUID

reference to the Seller, automatically added by the platform using the organization providing the upload or entering the data

articleNumber

String

a reference to the product of the Seller (eg SAP article nr)

articleName

String

the product name and description which is typically used on the transport
instruction to the EquipmentOperator

subgroup

String

Free text field (optional) which will allow filtering of products for easier master data
management

productType

Enum

Referring to the EFTCO product groups : Chemical, food, feed, pharma , other– default is chemical

maximumEcdValidity

Integer

optional field to indicate maximum ECD validity time (in hours) for certain products/article numbers (see step D); ECD validity time is the time the eECD is valid after the equipment leaves the cleaning bay.

uniqueReference

String

The unique reference for the product as loaded in the import file format (blank if created using the API).

The following rules are applied to ensure uniqueness of product information within a Seller’s product catalog:
- if an articleNumber if specified, it must be unique for this Seller
- if no articleNumber is specified, the articleName must be unique for the Seller

Product data can be uploaded via the eECD application and using the CSV product master data template.

Re-using this CSV upload template : Feel free to overwrite with your product records as of row 2; Do not change the title row!

eECD Product master data set_template_product user guide example.xlsx

These product master data serve also 2 other meta data structures used within the digital eECD process:

  1. product safety data describing the product characteristics

  2. loading location data describing the loading place where products can be loaded.

1. SDS master data

The SDS or safety data sheet information is provided by the Seller. This can happen by providing the SDS info per language and per article number or a Seller can refer to a public website url link where SDS information can be searched for using the commercial product description as used on the transport order. The SDS data structure looks as follows:

Field

Type

Description / comments

internalProductID

GUID

Internal reference, automatically attributed by the platform

SdsVersion

String

the version of this SDS

language

Enum

Currently EN, DE, NL, FR

sdsDate

Date

the date at which this SDS became validsdsDate Date the date at which this SDS became valid

linkType

Enum

Type of method used: SDS document or filename OR SDS url website link

link

String

Description of the actual document location

There is a SDS CSV file template available to upload weblinks per product. SDS pdf versions need to be uploaded manually

eECD Product SDS master data set_template user guide example.xls

Note: we work on a third SDS sharing option where SDS company info will be shared via a private cloud application.

2. Loading locations

This is an optional table for non integrated sellers to simplify the work of the EqOp/despatcher.

For non-integrated loaders, the seller maintains a list of permitted loading locations as they are known within their system. An equipment operator requesting a load can then select a product and loader, after which the
(list of) permitted loading location(s) is/are shown on screen. This loading location is nothing more than a string value, that the Seller has uploaded to the eECD application. If needed, the full address details of the
loader can still be requested.

Loading locations can be simply uploaded with a CSV file. Within the CSV file the following structure applies

  • UniqueReference : this is the unique article number or unique product description

  • Codetype: this refers to the code type used to identify the loader organization (eg VAT, DUNS,..)

  • Code: this refers to the code number used used to identify the loader. This code can be requested from the loader.

  • Description: this refers to the description of the loading place or loading location at the Loader and as the EqOp will see it when he drills down to select the loading location when assigning the load.

A CSV template example can be find here.

Chemco1 loading location master data template example.xlsx

Note : integrated Sellers, who share their transport orders via Elemica with the ECLIC platform, do provide already this information so that can skip to complete this table.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.