Single-Record vs. Dual-Record Systems

The GDSN Connect Item Database is designed as a dual-record system, which means that there are separate database tables for Menu Item (for use in recipes and menus, and commonly called Ingredients in other software applications) vs. Stock Items (for use in inventory and ordering).

GDSN Connect always sets up a Menu Item linked to a Stock Item record so that the full set of information from the GCDB is available to the Client App for each item.

NOTE: GDSN Connect can support one Menu item to multiple Stock Items or one Stock Item to multiple Menu Items in certain configurations. Please notify us if that is the case for your application.

Dual-Record Systems

For Client Apps that are dual-record systems, GDSN Connect will link the Client App ingredient or stock item record to the corresponding Menu Item or Stock Item records, as appropriate. GDSN Connect expects unique and distinct Client App Item IDs for each ingredient and stock item record from the Client App.

If the menu and stock item records are linked in the Client App, they will remain linked in GDSN Connect. If the item is set up as only an ingredient in the Client App (or only a stock item), GDSN Connect will store the corresponding Client App ID. The item with the Client App ID will be considered an "Existing Item" and the complementary item will be considered a "New Item" that the Client App.

When syncing data from GDSN, there is the concept of a "Base Unit" and a "Purchase Unit" (technically called an Orderable Unit). This could be a single GTIN....

It also supports one Menu Item linked to a single Stock Item, which could be a

Many K-12 back of the house software applications are set up in this same structure.