How Allergen Matrix Integrates with ProductFlow for Full Compliance

The most common source of allergen information errors in food business content is not ignorance of the requirements — it is maintaining the same allergen data in multiple places. A spreadsheet for the kitchen. A table on the website. Text in individual product descriptions. When a recipe changes, all three need updating. In practice, updates are inconsistent. Discrepancies between sources are the compliance risk.

The integration between Allergen Matrix and ProductFlow eliminates that problem. Allergen Matrix is the single source. ProductFlow reads from it. When allergen data changes, product descriptions update from the same source.

The Single Source of Truth Problem

Consider a food business with 50 products in its Shopify catalogue. Each product has allergen declarations in three places:

1. The product description text ("Contains: wheat, milk, eggs")
2. An allergen table on the product page (managed separately)
3. The allergen section on the food business's dedicated allergen information page

When a supplier changes their milk powder formulation and the product's dairy status changes, which of these three places get updated? In most food businesses, the answer is: the ones the person handling the update knows about, remembers to update, and has access to edit.

This is how allergen errors happen. Not through malice or negligence, but through the natural entropy of maintaining the same information in multiple places with imperfect processes.

How Allergen Matrix Becomes the Single Source

Allergen Matrix stores one authoritative allergen record per product: the 14 UK allergens (or 9 US FALCPA allergens in US mode) with declared status — present, may contain, or absent — for each.

When a recipe changes, the Allergen Matrix record is updated once. That record update then propagates to every downstream system that reads from it:

• Customer-facing allergen display on product pages updates automatically
• ProductFlow uses the updated record the next time a product description is generated
• SaltAI Subscriptions uses the updated record for swap management filtering

One update. Every touchpoint corrects.

How ProductFlow Reads Allergen Matrix Data

ProductFlow is SaltAI's AI product description generator for food businesses. When generating a description for a product, ProductFlow queries the Allergen Matrix record for that product and incorporates the actual allergen data into the generated text.

The practical output: a ProductFlow-generated description for a chocolate brownie with recorded allergens (milk, eggs, wheat, gluten) and a nut-free status will include accurate statements about those allergens and that nut-free status — not AI-inferred content, but actual data from your compliance record.

For a food business generating descriptions for 50 products, this means 50 allergen-accurate descriptions without manual cross-referencing each description against a separate allergen spreadsheet. The data integration does that work.

The Compliance Value Chain

The full integration creates a compliance value chain across a food business's Shopify operation:

Input: Allergen records maintained accurately in Allergen Matrix Product pages: Allergen Matrix displays correct allergen information on product pages (Natasha's Law / FALCPA compliance) Product descriptions: ProductFlow generates descriptions that incorporate Allergen Matrix allergen data (accurate marketing copy) Subscription management: SaltAI Subscriptions uses Allergen Matrix data to filter swap options per subscriber's allergen profile (operational safety)

Each step is only as good as the allergen data at the source. Maintaining that source accurately in Allergen Matrix is the foundation for compliance across the full stack.

Practical Setup

The integration between Allergen Matrix and ProductFlow is managed within the SaltAI app settings — both apps connect to the same Shopify store and the same Allergen Matrix data store. No separate API configuration or technical setup is required for merchants installing both apps from the SaltAI suite.

For food businesses starting from scratch, the recommended setup order is:

1. Install Allergen Matrix and build allergen records for all products
2. Install ProductFlow and generate initial product descriptions (which read from the Allergen Matrix records)
3. Set up a process for updating Allergen Matrix records when recipes change
4. Run ProductFlow to refresh descriptions for any product whose allergen record has changed

The maintenance process is then: recipe changes → Allergen Matrix update → ProductFlow refresh for affected products. A 5-10 minute process for any individual product change.

For food businesses with larger catalogues doing periodic recipe reviews, bulk regeneration in ProductFlow ensures all descriptions stay current with the Allergen Matrix records.

Why Manual Cross-Referencing Creates Compounding Risk

The alternative to a data integration like this is manual cross-referencing — a process that works until it does not. A staff member generating a product description for a new seasonal product checks the allergen spreadsheet, transcribes the relevant allergens into the description copy, and publishes. The process feels controlled. But it depends entirely on the spreadsheet being current, the person knowing to check it, and the transcription being accurate. Each of those three dependencies is a potential failure point operating independently.

Compounding risk is the real danger in manual allergen management. A single missed update to one document creates divergence between sources. That divergence persists silently until a customer with a food allergy reads the outdated information and makes a purchasing decision based on it. By that point, the compliance failure has already occurred — and the business has no mechanism to know the divergence existed until a complaint or incident surfaces it.

The architectural shift that Allergen Matrix and ProductFlow together represent is moving allergen accuracy from a process discipline problem to a systems problem. Process discipline is fallible because humans are fallible. Systems that make the correct outcome the default outcome are structurally more reliable. When ProductFlow cannot generate a description without reading the current Allergen Matrix record, the possibility of an outdated allergen declaration in a generated description is eliminated by design rather than by vigilance.

What Accurate Allergen Data in Product Descriptions Actually Achieves

Allergen accuracy in product descriptions matters for two distinct reasons that are worth separating. The first is regulatory: food businesses selling prepacked food in the UK are required under Natasha's Law to provide full ingredient and allergen labelling. Product descriptions that include accurate allergen information support compliance with that obligation across the digital touchpoints where customers are making purchasing decisions. The second reason is commercial: customers with food allergies are actively filtering for trustworthy allergen information when they shop online, and a product description that clearly and accurately states allergen status converts better with that customer segment than one that does not.

These two reasons pull in the same direction, which makes investment in accurate allergen data unusually straightforward to justify. There is no trade-off between compliance and commercial performance. A product description that correctly states "gluten-free, contains milk and eggs" serves the customer with coeliac disease who needs to know it is safe, and it also gives that customer the confidence to purchase. A description that is vague, inaccurate, or missing allergen information serves neither purpose. The integration between Allergen Matrix and ProductFlow produces descriptions that achieve both objectives simultaneously, because the allergen data driving the copy is the same data driving the compliance display.

For food businesses investing in SEO and content quality, there is a third benefit that is less obvious: specificity. AI-generated product descriptions that draw on actual allergen data are more specific and more factually grounded than generic AI content. A description that accurately names declared allergens and free-from credentials is more useful to a customer reading it, which is a signal that affects both conversion and organic search performance over time.

Handling Seasonal Products and Recipe Variations

Seasonal products present a particular allergen management challenge for food businesses. A Christmas pudding, a Valentine's Day brownie box, or a summer fruit tart may each appear in the catalogue for only a few weeks, but during that window the allergen information needs to be as accurate as for any permanent product. The temptation with short-run products is to treat allergen management as a lower priority — the product is not staying, so a rough approximation feels acceptable. That logic does not hold under Natasha's Law, and it does not hold when a customer with a tree nut allergy is reading the description.

Allergen Matrix handles seasonal products with the same structure as permanent ones. A record is created, allergen statuses are set, and the product page and ProductFlow descriptions draw from that record for the duration the product is active. When the product is removed from the catalogue, the record is archived. If the product returns the following year with the same recipe, the record is reactivated. If the recipe has changed — a different supplier, a reformulated ingredient — the record is updated before the product goes live, and the descriptions reflect the current formulation accurately from day one of the season.

Recipe variations within a single product line require the same discipline. A granola available in three flavours where one flavour contains nuts and two do not needs three separate Allergen Matrix records, each accurately reflecting the allergen profile of that specific variant. ProductFlow generates variant-specific descriptions reading from variant-specific records, so the nut-containing flavour's description never inherits the nut-free language from its siblings. This level of variant-level accuracy is difficult to maintain manually across a growing catalogue and straightforward to maintain when it is built into the data structure.

Keeping Records Current as Your Supplier Network Changes

Ingredient sourcing changes are one of the most common triggers for allergen record updates that businesses are not fully prepared for. A supplier change that appears administratively routine — same ingredient, different manufacturer — can alter a product's allergen profile in ways that are not immediately visible. A new flour supplier with different cross-contamination controls, a reformulated chocolate couverture that now includes a may-contain soya declaration, a shift from one stabiliser to another that introduces a new allergen — each of these requires an allergen record update before the product continues to be sold and described.

Building a supplier review trigger into procurement processes ensures that Allergen Matrix records are reviewed whenever an ingredient source changes, not just when a recipe is intentionally reformulated. The practical mechanism is straightforward: when a new supplier invoice is logged, the relevant products are flagged for allergen record review before the new ingredient enters production. That review takes a few minutes in Allergen Matrix. If the allergen profile is unchanged, the record is confirmed current. If it has changed, the record is updated and ProductFlow descriptions are refreshed immediately.

For food businesses growing their product range and supplier network simultaneously, this discipline compounds in value. A catalogue of 20 products with stable recipes is relatively manageable manually. A catalogue of 80 products with regular seasonal introductions and supplier relationships across multiple ingredient categories is not. The Allergen Matrix and ProductFlow integration scales with the catalogue rather than adding proportional administrative overhead, because the architecture does not change as the number of products grows.

Set up Allergen Matrix and ProductFlow together at saltai.app

Try Allergen Matrix free at saltai.app — no credit card required.