Does a small amount of cheese or meat in a sauce need a CHED-P at the GB border?

Does a small amount of cheese or meat in a sauce need a CHED-P at the GB border?

A pasta sauce with 4% cooked beef and a tablespoon of parmesan can need a CHED-P. A tomato-only one doesn't.

That single contrast is the thing most importers get wrong, and it's the thing that lands a held consignment on someone's desk at 4pm on a Friday. The instinct is volume: "it's only a trace of cheese, surely that's too little to matter." But the composite-product rules at the GB border don't read your spec sheet the way you do. They turn on what the product contains (products of animal origin — POAO), how that POAO was treated, whether the product is shelf-stable, and whether it sits on the GB exemption list. The amount is rarely the deciding factor.

This is a customs and sanitary-and-phytosanitary (SPS) question, so it sits across two systems you'll meet on every food import: IPAFFS (Import of Products, Animals, Food and Feed System — where you pre-notify) and the CHED (Common Health Entry Document — the document that pre-notification generates). For composite and plant products the relevant type is the CHED-P. The rules are set by Defra and published on GOV.UK, and they sit inside the Border Target Operating Model (BTOM), which risk-categorises goods. Below is how the call actually gets made — and how to make it before the lorry reaches the border control post (BCP), not after.

A note before we start: this is practical guidance, not regulated advice, and the rules for composite products have changed more than once. Always check the current GOV.UK position for your specific commodity and route, or ask us. Don't treat a classification you set two years ago as still correct.

What is a composite product, and why does it have its own rules?

A composite product is a defined SPS category, not a marketing term: it's a food intended for human consumption that contains both processed products of animal origin (POAO — meat, dairy, egg, fishery products) and products of plant origin. A jar of pasta sauce, a ready meal, a filled biscuit, a stock cube — these are composites. Because they're part-animal, part-plant, they get their own controls.

The reason composites have a distinct regime is that the animal-health risk lives in the POAO content, but a finished composite is usually processed, often shelf-stable, and sometimes a very long way from the raw ingredient that carried the risk. So the rules try to scale the control to the actual risk: a fully cooked, ambient-stable sauce with a little processed cheese is treated very differently from a chilled product carrying raw or lightly-treated meat. The category sounds like bureaucratic hair-splitting. In practice it's the difference between a consignment that moves freely and one that needs a CHED-P, an EHC-backed attestation, and a BCP check.

Define the term once and it stops being slippery: if your product is made from both animal and plant ingredients and isn't simply a cut of meat or a wheel of cheese, it's a composite — and the composite rules decide its border treatment.

Does a small amount of dairy automatically exempt a composite product?

No. A small amount of dairy does not automatically exempt a composite product. GOV.UK publishes guidance on which composite products are exempt from SPS controls and which need pre-notification, and the line is drawn by treatment and shelf-stability — not by the percentage of dairy on your specification sheet. A trace of cheese can still pull a product into controls.

This is the single most expensive assumption in composite imports. The volume instinct feels right because food law elsewhere is full of thresholds and percentages. But the composite exemption logic asks different questions of the dairy: was the milk-based ingredient fully heat-treated? Is the finished product shelf-stable at ambient temperature? Does the product as a whole appear on the relevant exemption list, or meet the conditions to be treated as exempt?

For many shelf-stable composites containing only processed dairy — think a long-life sauce where the dairy is a fully heat-treated, minor processed ingredient — the product can fall outside SPS pre-notification entirely. But that exemption is a function of the conditions being met, not of the dairy being "small." Change one fact — the dairy isn't fully treated, the product needs chilling, the meat content appears — and the same jar can need a CHED-P. The treatment of that dairy matters more than the amount of it.

How are meat and dairy treated differently in a composite?

Meat and dairy are treated differently because they carry different animal-health risk. As a general rule, the bar for meat (and meat products) in a composite is far lower than for dairy: a composite containing meat is much more likely to require a CHED-P and full SPS attestation, even at low inclusion rates, whereas a shelf-stable composite carrying only processed dairy can more readily qualify for exemption.

That's why the pasta-sauce contrast at the top holds. Take a sauce out and add 4% cooked beef, and you've introduced meat — the higher-risk POAO. A tomato-and-herb sauce has no POAO at all and isn't a composite in the controlled sense. A sauce with only a heat-treated dairy ingredient may sit in the exempt space if it's shelf-stable and the conditions are met. The same recipe, three different border outcomes — driven by which POAO is present and how it's been processed.

So "how much meat is in it?" is the wrong opening question. The right sequence is: Is there any POAO? Which type — meat, dairy, egg, fishery? How was it treated? Is the finished product shelf-stable? Does it meet the exemption conditions? Get the POAO type wrong and you've started the whole assessment from the wrong rule.

How do you actually decide if your sauce needs a CHED-P? A worked example.

You decide by running the product through the composite logic in order: identify the POAO, identify its treatment, check shelf-stability, then check the product against the current exemption position on GOV.UK. The CHED-P requirement is the output of that check — and it's a check you do at the desk, before the consignment ships, not at the BCP.

Let's run a real-shaped example through it. Say you import an ambient pasta sauce from the EU. Spec sheet: tomato base, herbs, olive oil, 4% cooked beef, and a small amount of processed hard cheese.

Step 1 — Is there POAO? Yes. Two animal-origin ingredients: cooked beef (meat) and processed cheese (dairy).

Step 2 — Which POAO governs? Meat is present, so the higher-risk rule applies. Even at 4%, the beef is the deciding ingredient. The cheese question barely matters now — the meat has already set the bar.

Step 3 — Treatment and shelf-stability. The product is ambient-stable and the meat is fully cooked. That's relevant to which controls apply and to the supporting attestation, but for a meat-containing composite it does not, by itself, deliver an exemption.

Step 4 — Check the current GOV.UK position. Because meat is present, you check the composite-product guidance and the exemption list for this exact product type and route. In the great majority of cases, a meat-containing composite from the EU will need pre-notification in IPAFFS and a CHED-P, supported by the appropriate health attestation.

Outcome: this sauce needs a CHED-P, raised in IPAFFS before arrival, and the consignment routes through a BCP capable of handling composites.

Now change one fact. Drop the beef; keep only the heat-treated processed cheese; keep it ambient-stable. Re-run the steps and you may land on exempt — no CHED-P — provided the product meets the current exemption conditions. Same shelf, same packaging line, completely different border treatment. That's why the classification is a per-recipe decision, not a per-supplier one.

What does the IPAFFS pre-notification and CHED-P actually require?

For a controlled composite, you pre-notify the consignment in IPAFFS before it arrives, which generates the CHED-P; the consignment must be accompanied by the correct supporting documentation — typically a health attestation or, for higher-risk POAO content, an Export Health Certificate (EHC) — and arrive at an appropriate BCP, where it may be subject to documentary, identity, and physical checks.

In practice that means several pieces have to line up, and they're easy to get out of step:

• The commodity code. You classify the finished product with the correct commodity code on your customs declaration (lodged in CDS, the Customs Declaration Service). The code and the SPS treatment have to tell the same story — a composite classified as if it were a plain plant product will not match its CHED-P.
• The IPAFFS entry. Raised by the importer or their representative, before arrival, describing the product honestly — including the POAO content. What this entry says about the dairy or meat is the decision. A vague or wrong entry is where holds are born.
• The supporting attestation / EHC. The right document depends on the POAO type and treatment. This is sourced in the exporting country and must travel with the goods.
• The BCP routing. The consignment has to enter through a BCP designated for that category of goods.

Miss the pre-notification window, and the consignment can be held on arrival. For perishable goods, that cost compounds by the hour — but even for an ambient sauce, a hold means storage, demurrage, and a scramble for the document you should have had in hand.

Who owns the composite classification in your import workflow?

The composite classification should be owned by someone who can see both the product specification and the customs/SPS requirements — usually the importer's compliance or operations lead, not the freight forwarder guessing from a product name. The decision happens at the point you classify the product, long before the lorry reaches the BCP, and that's exactly where it's most often missed.

This is the process gap behind most composite holds. The forwarder sees "pasta sauce" and books it as ambient grocery. The supplier's spec sheet lists ingredients but doesn't tell you the border treatment. Nobody runs the four-step check, because nobody owns it. Then the consignment hits the BCP, the documentary check flags the POAO, and the hold lands on the importer's desk — not the forwarder's.

The fix is unglamorous and cheap: decide the composite status when you onboard the product, write it down, attach it to the SKU, and re-check it whenever the recipe, the supplier, or the rules change. Reviewing your composite classifications is a before-the-next-load job, not an after-the-hold one.

Has BTOM changed how composite products are treated?

Yes. The Border Target Operating Model (BTOM) introduced a risk-categorisation approach for SPS goods, and composite products are assessed against risk categories rather than a single blanket rule. A classification you set before BTOM, or before the most recent guidance update, may now produce a different answer — which is why a periodic re-check matters.

The practical takeaway isn't to memorise the categories — they can move, and the detail differs by commodity and origin. It's to treat a past, "settled" classification as a hypothesis rather than a fact. If you last decided whether your sauce needed a CHED-P a couple of recipe iterations or a guidance update ago, that answer is overdue a recheck against the live GOV.UK position. The rules have already moved more than once for composites; assume they can again.

How does this connect to commodity codes and labelling?

The composite decision doesn't sit on its own. Two adjacent mechanisms travel with it.

First, the commodity code. The code you classify the finished product under drives the duty, the controls, and whether the customs declaration in CDS aligns with the SPS treatment. Composite products are notoriously easy to misclassify — and a code that doesn't reflect the POAO content is both a compliance risk and, sometimes, the reason duty is over- or under-paid. Get the classification and the SPS call done together, from the same view of the product.

Second, labelling. If you're importing to sell in GB, the product still has to meet GB food information rules (the retained FIC framework) — ingredient lists, allergen emphasis, mandatory particulars. And if any of that product flows on to Northern Ireland or back into the EU, separate labelling expectations apply. The composite question is "can it cross the border?"; the labelling question is "can it legally sit on the shelf once it has?" Both need answering before you commit a launch.

You don't need to become an expert in all of this. You need one person, or one adviser, holding the whole picture so the commodity code, the CHED-P decision, and the label all tell the same story.

The short version

A small amount of cheese or meat in a sauce does not automatically escape a CHED-P. Whether your composite needs one turns on the POAO type, its treatment, the product's shelf-stability, and the current GOV.UK exemption position — not the percentage on the spec sheet. Meat sets a far lower bar than dairy. Decide the classification at the desk, before the consignment ships, and re-check it whenever the recipe, the route, or the rules change.

Borders are complicated. We aren't. We live in the detail so you don't.

Got a consignment moving soon, or something already held? The Falsum Helpdesk triages live customs and SPS issues, including composite-product classification calls. Talk to the Helpdesk. Or for a product you're planning to import: tell us the goods and the route — we'll tell you exactly what you need.

FAQ