PIMvendors

Knowledge Base · Core ·

Core · Guide

Foodservice Product Data in the Netherlands: What Wholesalers and Caterers Need

  1. 01Model
  2. 02Fill
  3. 03Check
  4. 04Publish
  5. 05Maintain

A food manufacturer that sells to supermarkets has usually learned what retail wants from its product data. Foodservice asks different questions: how a product is prepared, how many portions a case gives, and what goes on the allergen card in the kitchen. This guide is for food and beverage manufacturers and brand owners in the Netherlands, Belgium and Germany that supply Dutch foodservice wholesalers, caterers and out-of-home operators. It is not legal advice: confirm the rules with your quality or legal team. The wider product data challenges in food are on our food and beverage hub.

How foodservice differs from retail

In retail, the reader of your product data is a shopper. In foodservice, it is a professional: a chef planning a menu, a catering buyer, a dietitian in a care home. They need the same label data, plus data about how the product behaves in a kitchen.

QuestionRetail shelfFoodservice kitchen
Who reads the dataConsumerChef, caterer, buyer, dietitian
Unit that mattersConsumer unitCase, inner pack and the unit inside
UseReady to eat or simple home preparationPreparation method, regeneration, use in dishes
QuantityNet quantityPortions per pack, portion size, yield
StorageStorage conditions and date markingAlso storage after opening or thawing
AllergensOn the label for the shopperPassed on by the caterer to its guests

In practice, foodservice buyers look for these attribute groups:

  • Preparation and use. Method (oven, combi steamer, fryer), from frozen or thawed, times and temperatures, suitable applications.
  • Portions and yield. Portions per pack, portion weight and yield after cooking or thawing, so a kitchen can calculate its cost per portion.
  • Pack configuration. Unit, inner pack and case, each with its own GTIN where it is traded, plus dimensions, weights and the count per level.
  • Storage and shelf life. Storage temperature, remaining shelf life at delivery, and shelf life after opening or thawing.
  • Allergens and diets. The 14 allergen categories of Annex II, with "contains" kept apart from "may contain".
  • Documents. The product specification, certificates and evidence for claims; see food claims and evidence under EmpCo.

The general food record is covered in PIM for food and beverage.

Allergen information out of home

Regulation (EU) No 1169/2011 treats food sold without prepackaging differently from food on a shelf. Under Article 44, when food is offered to the final consumer or to mass caterers without prepackaging, the allergen particulars of Article 9(1)(c) are mandatory, and member states may set how the information is made available. Article 2(2)(d) names restaurants, canteens, schools, hospitals and catering enterprises as examples of mass caterers.

Two other provisions reach the supplier directly. Article 8(6) requires operators to pass information about non-prepacked food intended for the final consumer or for mass caterers on to the operator that receives the food. Article 8(7) allows the mandatory particulars of prepacked food supplied to mass caterers for preparation, processing, splitting or cutting up to appear on commercial documents that accompany the food or were sent before or with the delivery; the name, date marking, storage or use conditions and the operator's name and address must still be on the outer packaging. For a foodservice supplier, the product specification and its data feed are part of the legal information chain.

The Netherlands fills in Article 44 in two instruments. The Warenwetbesluit informatie levensmiddelen makes Article 44(1)(a) enforceable and lets the minister set rules on the means. The Warenwetregeling allergeneninformatie niet-voorverpakte levensmiddelen, in force since 13 December 2014, requires a clearly visible notice of where the allergen information is available, and that information in writing or electronically. Oral information is allowed only when staff can give it before the purchase, the information is available in writing or electronically for staff and the NVWA, and a visible notice asks guests to ask for it.

The NVWA's guidance on allergens in unpacked food addresses suppliers directly: a supplier of unpacked food must give its customers enough information for them to inform their own customers about allergens. A caterer's allergen card is only as good as the data its suppliers send.

For prepacked products, the NVWA announced on 18 December 2025 that new rules on precautionary allergen warnings ("may contain") apply from 1 January 2026 and that its inspections check labels against them; whether to warn follows from a risk analysis against reference values. The data model for both kinds of allergen information is in allergen data management in a PIM.

Where foodservice product data is exchanged as of November 2026

Two exchange points come up in Dutch foodservice: PS in foodservice and GS1 Data Source. Both are in operation as of November 2026.

PS in foodservice

PS in foodservice is a Dutch product information database for the foodservice market. In its announcement of its new owner, it describes itself as the central product specification database and market standard for product and chain information in Dutch foodservice. Producers supply their product information once, according to its page for producers, and wholesalers connect their webshop or system to the PS database, according to its page for wholesalers. Its public product search is branded Foodbook.

Matilda FoodTech announced that PS in foodservice becomes part of the Swedish company. PS in foodservice wrote that its current management team stays in charge and that nothing changes for customers and partners. In a release dated 2 December 2025, on its purchase of Erudus in the UK, Matilda FoodTech said it now has Erudus, Dabas in Sweden and PS in foodservice under one roof.

PS in foodservice says on its page for producers approached by a customer that it links with ERP and PIM systems and with GS1. On its page about Sligro's request to suppliers, it adds that product information supplied through GS1 lacks some details its PS Impact Score needs (the country of origin per ingredient and the ingredient percentages), which suppliers add in PS in foodservice.

GS1 Data Source

GS1 Nederland describes GS1 Data Source as the data pool for sharing product information: manufacturers and wholesalers share with their customers, and retailers, wholesalers and hospitals receive. For food, GS1 Nederland runs the pool for its food, health and beauty sector and lists a release on 14 November 2026. GS1 Belgium and Luxembourg publishes the GS1 Benelux data model for the FMCG and foodservice sector, for product data exchanged through GDSN. How the pool works for supermarkets is explained in GDSN for food in the Netherlands.

What this means for a supplier

A customer may name either of the two, another pool or its own portal. Before you build a feed, ask which pool or portal, which data standard and which GLN or account.

What a wholesaler asks for: one public example

Sligro Food Group publishes its requirements in a supplier handbook. The January 2026 edition sets out:

  • Data before listing. Suppliers register complete, correct and timely item data in the data pool agreed with their purchasing contact, before the product enters the range.
  • Routes. GS1 is Sligro's strong preference. The handbook lists Superunie (only for items bought through Superunie), GS1 (logistics data for food and non-food and label data for food, published to Sligro's GLN), My Product Manager, PS in foodservice and Sligro's own supplier portal.
  • Exclusive brands. Data for Sligro's exclusive-brand food and fresh items always goes through PS in foodservice, and suppliers publishing there are asked for data for the PS Impact Score, which calculates the CO2 emissions of the product.
  • Data guidelines. A unique valid GTIN, a GPC brick code, the TARIC code, readiness for data in Dutch, English, German and French, packshots of at least 2401 pixels on a white or no background with the GTIN in the file name, and packaging element, weight and material.
  • Costs. Costs caused by incorrect or incomplete item data are recharged to the supplier, for example a packaging tax assessment caused by wrong packaging data.
  • Notice. Changes to an item or its delisting are announced at least nine weeks ahead.

The handbook also asks suppliers of products under the EU Deforestation Regulation for the information Sligro needs; see EUDR and food product data.

This is one wholesaler's rulebook, not a sector standard. Other customers set their own requirements, so keep a requirement profile per customer rather than one generic export.

Five steps to foodservice-ready product data

  1. Model

    Add a foodservice attribute group: preparation, portions and yield, pack levels, storage after opening, and allergens as controlled values with "contains" and "may contain" apart. Add the classification codes customers ask for, such as the GPC brick; see product classification: GS1, ETIM and ECLASS.

  2. Fill

    Take each value from the team that owns it: specification from product development, allergens from quality, pack measurements from logistics, images from marketing. Record the owner per attribute, so every gap has a name.

  3. Check

    Validate before anything leaves: allergens consistent with the ingredient list, pack counts that add up from unit to case, a GTIN for every traded level, and each customer's mandatory fields. See product data quality and governance.

  4. Publish

    Send the approved version to the exchange point each customer named and to the right GLN or account. Publish retail and foodservice from the same approved record.

  5. Maintain

    Treat a recipe change as a data change: update allergens and specification first, publish to every pool on the same day, and respect customer notice periods. Recheck your mappings when a pool publishes a new release.

Where the PIM fits

A PIM does not replace the data pools; it feeds them. A layout for a supplier selling to both retail and foodservice:

One product record feeding retail and foodservice exchange pointsData flows from Recipes, Quality, Packaging, Logistics and ERP into the PIM. The PIM steps are model, fill, check, publish and maintain. The approved record is then published to GS1 Data Source, PS in foodservice, Wholesaler portals, Retail and Webshop.SourcesChannelsRecipesQualityPackagingLogisticsERPGS1 Data SourcePS in foodserviceWholesaler portalsRetailWebshopPIM1Model2Fill3Check4Publish5MaintainOne product record feeding retail and foodservice exchange pointsData flows from Recipes, Quality, Packaging, Logistics and ERP into the PIM. The PIM steps are model, fill, check, publish and maintain. The approved record is then published to GS1 Data Source, PS in foodservice, Wholesaler portals, Retail and Webshop.SourcesChannelsRecipesQualityPackagingLogisticsERPGS1 Data SourcePS in foodserviceWholesaler portalsRetailWebshopPIM1Model2Fill3Check4Publish5Maintain
One product record feeding retail and foodservice exchange points
  • One record with a shared core. Identity, ingredients, allergens, nutrition and label data are maintained once for every channel.
  • Channel-specific attribute groups. Consumer copy sits in one group; preparation, portions and case data in another. Each customer profile states which fields are mandatory.
  • Assortments per channel. Catering packs are trade items in their own right, so the PIM decides which items go to which pool and customer.
  • The pool is the exchange point. Edit in the PIM, not in the pool's web screens, or the two will drift. See PIM vs PXM vs syndication tools.
  • ERP holds prices and conditions. Prices, conditions and orders stay in ERP; see where ERP stops and PIM starts.

Checklist for suppliers

  • Ask every foodservice customer which pool or portal, data standard and GLN or account it expects.
  • Add a foodservice attribute group: preparation, portions and yield, pack levels, storage after opening.
  • Keep allergens as controlled values, with "contains" and "may contain" apart and a risk analysis behind every warning.
  • Give every traded pack level a GTIN with dimensions, weights and counts.
  • Link the specification and certificates to the record, with validity dates.
  • If you publish through GS1 and a customer uses the PS Impact Score, check which extra data PS in foodservice asks for.
  • Agree who updates what when a recipe changes, and how fast every channel follows.

Where to go from here

Both tools are free and independent of any vendor.

Not sure you need a PIM yet?

A short check that shows whether a dedicated PIM helps your catalog, or whether spreadsheets and ERP still do the job.

Check if a PIM fits

Ready to compare vendors?

Answer questions about your scale, sector and must-haves and get a ranked shortlist.

Build my vendor shortlist

Frequently asked questions

How is foodservice product data different from retail product data?

Retail data is written for a shopper reading a shelf label or a webshop. Foodservice data is read by chefs, caterers and buyers who prepare, portion and serve the product, so it also needs preparation instructions, portions and yield, case and inner pack data, and storage after opening. The legal label data stays the same; the professional data comes on top.

Does a caterer need allergen information from its suppliers?

Yes. Article 44 of Regulation (EU) No 1169/2011 makes allergen information mandatory for food offered without prepackaging, such as dishes served in restaurants, canteens and care kitchens. The NVWA tells suppliers of unpacked food to give their customers enough information to inform their own customers, so the caterer's allergen card depends on the supplier's data.

What is PS in foodservice?

PS in foodservice is a Dutch product information database for the foodservice market: producers maintain their product specifications there and wholesalers connect their systems to receive them. Matilda FoodTech, a Swedish foodservice software company, announced that it has acquired PS in foodservice. As of November 2026 the database is in operation.

Is Dutch foodservice product data exchanged through GS1 Data Source or PS in foodservice?

As of November 2026, through both. GS1 Nederland describes GS1 Data Source as the data pool where manufacturers and wholesalers share product information with their customers, and Sligro Food Group's supplier handbook names GS1 as its strong preference while requiring PS in foodservice for its exclusive-brand food items. Ask each customer which route it expects.

What does a Dutch foodservice wholesaler ask its suppliers for?

Requirements differ per customer. As one public example, Sligro Food Group's January 2026 supplier handbook asks for complete item data in the agreed data pool, a valid GTIN, a GPC brick code, the TARIC code, packshots of at least 2401 pixels and packaging details, and it recharges costs caused by incorrect data to the supplier.

Do I need a separate PIM for foodservice?

Usually not. One product record can serve retail and foodservice when the model has a shared core (identity, ingredients, allergens, nutrition) plus channel-specific attribute groups and assortments. The PIM feeds each data pool or customer portal, and prices and conditions stay in ERP.

Diagnostic

Do you actually need a PIM?

Run the complexity index before you budget software or hire an SI.

Start assessment

Budget

Model a first-pass TCO

Translate catalog shape into a three-year cost range in under ten minutes.

Open cost calculator