What product is this article for?
GDSN 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 = Stock Item (sometimes just referred to as 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.
Item Type
GDSN Connect classifies items as either "Food" or "Non-Food", but PrimeroEdge does not have this explicit field. Instead, PrimeroEdge applies the following logic to determine if the record is a Food item.
If any of the following attributes in PrimeroEdge have a value, then the record will be classified as Food when imported in GDSN Connect:
- Serving Measure: If any serving measure is setup
- Nutrients: Any nutrient value is populated (this requires a Serving Measure)
- Meal Contributions: Any contributable component is setup (this requires a Serving Measure)
- Allergens: If any allergen has been added
NOTE: This logic could cause some food items to be setup as Non-Food in GDSN Connect if there are no Serving Measures or Allergens added to the record in PrimeroEdge.
Stock Item & Inventory Setup
There are a few attributes on the PrimeroEdge Stock Item that are mapped to records in GDSN Connect.
- 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 directly by the user using GDSN Connect as a reference.
Net Weight
Within GDSN Connect, there are two Net Weight attributes, both entered in a unit of "Pounds".
- Nominal Net Weight: This is the value that is provided by the manufacturer and represents the "As Purchased" weight of the purchase unit.
- Net Weight As Served: This is a calculated net weight that is equal to the [Servings Per Purchase Unit] x [Serving Size-Weight]. This is sometimes called a "drained weight".
In the information that GDSN Connect exports to PrimeroEdge, the Stock Item's Broken Unit Weight is setup using the Net Weight As Served (instead of the Nominal Net Weight). This is done so the "as served" weight that is set up on an Ingredient's Serving Measure will calculate the correct number of servings for the Broken Unit and Whole Unit. This will aid in more accurate inventory and ordering using forecasted menu plans.
Ingredient Serving Measure & Nutrients
For Ingredients that get its nutritional information from GDSN, the serving size and nutrients are updated as a set. When this is imported into PrimeroEdge, the Serving Size from the manufacturer will be setup as a new "Serving Measure", and the nutrients will be setup using that Serving Measure.
In GDSN Connect, the Serving Size Description will provide the description of the Serving Measure, and the Serving Size-Weight value will provide the weight of that Serving Measure.
Allergens
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, as most of the values are on the Stock Item.
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.