PrimeroEdge > PrimeroEdge-specific Information

What product is this article for? 

YesGDSN Connect

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

Attribute Mapping

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

Record Types

GDSN Connect and PrimeroEdge have a similar structure but have different terminology for the records.  

  • Ingredient = Menu Item
  • Stock Item = Item

If you're only using PrimeroEdge Menu Planning without Inventory, GDSN Connect will still contain the information to setup the Stock Items at a later point, making this upgrade easier to implement at your convenience.

Stock Item & Inventory Setup

  • Whole Unit:  This corresponds to the "Purchase Unit" in GDSN Connect
  • Broken Unit:  This corresponds to the "Inventory Unit" in GDSN Connect
    • Broken Unit Description* = [Inventory Unit]
    • Broken Units per Whole Unit* = [Inventory Units per Purchase Unit]
    • Broken Unit Weight = [Net Weight As Served] / [Inventory Units per Purchase Unit]

NOTE: These attributes cannot be changed in PrimeroEdge by GDSN Connect.  The items with an asterisk (*) can only be changed by submitting a support ticket to PrimeroEdge. The Broken Unit Weight can be changed in PrimeroEdge using values from GDSN Connect, which will guide the user through some additional validations.  

Net Weight

Within GDSN Connect, there are two Net Weight attributes, both entered in a unit of "Pounds". 

  • Nominal: This is the value that is provided by the manufacturer and represents the "As Purchased" weight of the purchase unit.
  • As Served: This is a calculated value that is equal to the [Servings Per Purchase Unit] x [Serving Size-Weight].

Ingredient Serving Size

  • Serving Size-Weight:  This corresponds to the Serving Size-Weight in GDSN Connect. 


GDSN Connect and PrimeroEdge exchange data for only the standard Big 9 Allergen Types. 

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

For the standard Existing Item update through Global Catalog, PrimeroEdge only supports Allergen Claim values of "Contains" and "May Contain".  Any other claims from the manufacturer, such as "Does Not Contain" or "Free From",  will not be synced into PrimeroEdge, but these values will still be available within GDSN Connect as a reference.  

For the New Ingredient file generated by GDSN Connect, claims of "Free From" and "Does Not Contain" will appear as "None" within the file. "Contains" and "May Contain" will be populated, and any other claim values from the manufacturer will be ignored and left blank.   

Exchanging Data 

Inventory Setup Values

GDSN Connect converts the corresponding attributes in PrimeroEdge to those used within GDSN Connect. 

NOTE: Updating and syncing most of these inventory setup values back into PrimeroEdge is not yet supported.  

CN Database

Since PrimeroEdge does not send information about the source of the nutrients (e.g., CN Database), GDSN Connect will always overwrite nutrient values from the file with those from the N2F Database.  

New Ingredient vs. Existing Items

The standard Existing Items update will update most of the Ingredient attributes and some of the Stock Item attributes, but it will not create any new records, nor will it link any Ingredients or Stock Items that are linked in GDSN Connect. 

The New Ingredient file will allow users to create new Ingredients in PrimeroEdge and add basic information to that record, including nutrients and allergens.  Once the Ingredient has been added to PrimeroEdge, then a full Existing Items update can be run to add the additional attribute information.  

Adding new Stock Items or linking Ingredients to Stock Items is not currently supported.  

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