Titan > Titan-specific Information

What product is this article for? 

YesGDSN Connect

This document describes some of the specific details about the integration with Titan. 

Attribute Mapping

Most of the attribute within Titan and GDSN Connect are pretty similar to each other. However, some attributes may have different names or terminology, and this article describes those differences. 

Titan Units of Measure

  • Base Unit:  This corresponds to the "Inventory Unit" within GDSN Connect
    • UOM Description = [Inventory Unit]
    • UOM Weight = [Net Weight as Served] / [Inventory Units per Purchase Unit]
  • Preferred Unit:  This corresponds to the "Purchase Unit" within GDSN Connect
    • UOM Description = [Purchase Unit]
    • UOM Quantity = [Inventory Units per Purchase Unit]
  • Serving Size:  This corresponds to the "Serving Size" of the nutrients within GDSN Connect
    • UOM Description = [Serving Size Measure] if present, otherwise [Serving Size Weight]
    • UOM Weight = [Serving Size Weight]


  • Base Weight:  [Serving Size-Weight]

Allergen Types

GDSN Connect exports the Big 9 allergens using these standard values. 

  • Milk
  • Peanut
  • Fish
  • Soy (mapped to Soybean in GDSN Connect)
  • Egg
  • Tree Nut
  • Shellfish
  • Wheat
  • Sesame

NOTE: It's recommended that a district update their allergen text to use these values to align with industry and GDSN standards. If there are different values for the same allergen type (Eggs vs Egg), then both will appear.

In GDSN, manufacturers specify a specific Allergen Claim for each Allergen Type. To be included as an exported Allergen from GDSN Connect, the Claim must be either "Contains" or "Does Not Contain".  Other claim values, such as "Free From", "Does Not Contain", "Undeclared", etc. will be excluded from the import file.  

Exchanging Data 

Serving Size

Since Titan does not send Base Weight or Serving Size UOM values in the import file, the Serving Size of the records in GDSN Connect will use the values from the Nourish to Flourish (N2F) Database record.  

Upon import back into Titan, this Serving Size will update the Base Weight value of the nutrients.

CN Database

Since Titan does not send any nutrients values to GDSN Connect, GDSN Connect will setup all nutrients using values from the N2F Database.  

Upon import back into Titan, if that item had already been associated with a CNDB record, Titan will retain the associated CNDB record and not update the nutrients and base weight using values from GDSN Connect.  This will mean that there could be different nutrient values in each system.  

Ingredients and Meal Components

Titan does not currently import ingredients or meal components into the records within Titan. They can be accessed within GDSN Connect as a reference.

Was this article helpful?
0 out of 0 found this helpful