Skip to content
Marketing & campaignsFood & Beverage

Retail listing documents from one source

demi fills every retail chain's listing forms from recipe, specification and images and finds contradictions before they are sent.

Today

Every retail chain wants the same product data in its own form: nutrition values, allergens, GTIN, pallet pattern, shelf life, dimensions, images and certificates. The key account team gathers them from recipes, lab reports, the ERP and old e-mails and types them into spreadsheets and portals. A transposed digit in a GTIN or an allergen that is on the label but not in the form delays a listing by months.

An example

Tarvina is launching three new 250 g SC sauces for the chilled shelf, and two retail chains want to list them. One sends a spreadsheet with 186 fields, the other access to its supplier portal. The agent fills both from recipe, lab values, ERP and media library: nutrition per 100 g, allergens, GTINs for cup and case, 12 cups per case, 168 cases per pallet, remaining shelf life on delivery and storage at 0–4 °C. It finds two contradictions: according to the specification the curry sauce contains mustard, but the allergen matrix does not list it, and one case GTIN has a wrong check digit. The quality manager clears both in a morning, and both forms go out the same week.
Fictional company, typical workflow.

Your data, wherever it lives

Recipes and specifications live today in recipe management and Word files, nutrition values in lab reports as PDFs, GTINs, pallet patterns and prices in the ERP, product images in the media library and the chains' forms in spreadsheets, e-mails and supplier portals. demi reads, understands and links them, with your rights. The AI fills each listing form in minutes instead of hours, and your quality and sales teams decide what goes out.

Where the data lives today

  • PLM
  • ERP
  • QM system
  • PDFs
  • Office files
  • Photos, video & audio
  • E-mails
  • Web & portals
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from recipe and specification management, the ERP, the lab, the QM system, the media library and retailer portals. demi replaces nothing and links, per article, recipe, ingredients and allergens, nutrition values, GTIN, pallet pattern, shelf life, images and certificates. demi writes completed forms into the chain's template or portal only after approval.

  2. 2 · PermitPermission Layer

    Recipes and costings are visible only to development, quality and authorised key account managers; only data released for retail goes into a form. Each chain sees only its own terms. Quality management releases specification and allergens, sales releases the form, and both are recorded.

  3. 3 · ActIntelligence Layer

    The agent recognises the fields in each chain's form, even in unfamiliar spreadsheets and PDF templates, and fills every field with the value from the leading system, with its source. It calculates and checks nutrition values, weights and the GTIN check digit by fixed rules, never by estimate. It shows contradictions between label, specification and form side by side, and fields without a documented value stay open instead of being invented.

How it runs

  1. 1

    The retail chain sends its listing form as a spreadsheet, as a PDF or as access to its portal.

  2. 2

    The agent recognises each field and maps it to the value from recipe, ERP, lab or media library.

  3. 3

    It fills in the form, recalculates nutrition values and pallet pattern and checks every GTIN.

  4. 4

    It puts contradictions and open fields to quality and the key account team for clarification.

  5. 5

    After approval the form goes to the chain; if the article changes later, the agent shows every chain that needs new data.

What changes

  • Listings without queries about wrong or missing data

  • Every chain gets the same documented product data

  • Recipe and packaging changes reach every retail partner

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+173 hfreed per year

Assumptions and calculation

demi fills the chains' listing forms from recipe, ERP and lab data and checks them; you approve.

3 h → 1.8 h per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

12 listing forms × 3 h × 40% × 1.0 (manual) × 12 months = 173 h

Value per year, before demi costs

Freed per year+173 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€11,245

gained per year

173 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Can demi cope with each chain's different forms?

Yes. The agent reads spreadsheets, PDF forms and supplier portal screens and maps every field to a value in your systems. For a new form your team confirms the mapping once; after that the agent fills every later version on its own. Fields it cannot map are shown to you.

Where do the nutrition values in the listing form come from?

From your recipe and the lab reports, calculated per 100 g and per portion. Rounding follows the rules that apply to nutrition labelling in the EU. If a calculated value differs from the latest lab report, the agent shows both, and quality decides.

What happens when a recipe changes?

The agent shows which data change as a result and which retail chains list the article with the old data. It prepares the change notice for each chain in its own format. It goes out only after quality and sales approve it.

Can one chain see another chain's data?

No. Terms, promotions and agreements are kept separate per chain, and each form contains only what is released for that chain. Only the product data that is the same for everyone is shared.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases