Canned and prepared fish traded under HS 1604 moved through global import channels at 3.2 million tonnes and USD 17.54 billion in 2023, according to UN Comtrade data derived with FAO. Canned tuna alone represents 43% of canned fish import volume, and canned fish accounts for 75.3% of the canned seafood market measured by Grand View Research. Volume is rarely the constraint in this trade. The constraint is documentation, and more precisely whether the documentation in the purchasing file covers the product that is actually on the water.

The failure mode is quiet rather than dramatic. A supplier file can hold a valid food safety certificate whose written scope names three fish species, and a valid halal certificate whose written scope names two product forms in two specific sauces. Both documents can be genuine, both can be inside their validity period, and a purchase order can still fall outside the scope of one or both.

This industry reference explains how importers can close that gap by writing qualification requirements into purchase terms at the level of the individual SKU, using two certificates held for the Agrogentra canned fish range as the working example.

Why supplier-level certificate filing misses SKU-level scope

Certificates are written about scope, not about a supplier as a whole. That single sentence explains most qualification disputes in canned fish procurement.

When a supplier is first approved, certificates are usually collected once and filed under the supplier name. The file records that a food safety certificate exists and that a halal certificate exists. What the file often does not record is which named products, packing media and can sizes sit inside each written scope. Because scope language is product-specific, three practical consequences follow:

• Order lines drift outside named scope. A buyer adds a new species or a new sauce variant to an existing supplier relationship, and the certificate is assumed to travel with it. Scope does not travel automatically.
• Label and listing claims outrun the evidence. Retail listings or importer declarations may reference certification that the specific SKU does not hold.
• Market-entry assumptions go unverified. Where a destination market expects halal conformity, the gap is discovered late, at customs or at the buyer's own audit, when container-level remedies are expensive.

The corrective step is procedural rather than technical: convert each certificate into a scope map of the actual SKU list, then write that map into the purchase terms so that qualification is verified per order line instead of per supplier.

The two certificates that govern canned fish qualification

Two certificates are relevant to the canned fish range discussed here, and they answer different questions. One addresses food safety management across a manufacturing scope. The other addresses halal conformity for a narrow set of product forms. Reading them as interchangeable is the origin of most scope mismatches.

BRCGS certificate 051A1312001, Issue 9

This certificate is a BRCGS certificate, Issue 9, issued by Intertek under UKAS accreditation number 014. Its scope names canned mackerel, sardine and tuna manufacturing. In practice, that means the certificate speaks to the manufacturing of those three fish categories, and it does not name other species or non-fish product lines in its written scope.

Halal certificate 8998250000 from SHC

This certificate is issued by SHC and is valid from 2025-07-01 to 2028-06-30. Its scope is limited to Canned Sardines in Oil and Canned Mackerel in Tomato Sauce, granted against Malaysia MS1500:2019 and Indonesia Halal Law Regulations. The halal certificate is therefore narrower than the food safety certificate, and narrower than the canned fish catalogue as a whole.

SKU-level scope map for the canned fish range

Once the two scopes are laid out side by side, each SKU falls into one of four positions: inside both scopes, inside the food safety scope only, outside both, or requiring clarification of the packing medium. The table below is the practical form of that mapping and is the artifact that should be attached to purchase terms.

The Agrogentra canned seafood range includes canned sardines, canned mackerel, canned tuna, canned Alaska pollock, canned squid and canned baby clam, alongside canned vegetables such as canned carrot, canned red pepper, canned sauerkraut, canned mixed mushrooms, canned sweet potato, canned potato and canned baby corn, and tomato lines including canned tomato paste and canned ketchup. Against the two scopes above, that range is not uniformly covered, and the mapping is the point.

Where private label and OEM tuna falls inside or outside each scope

Canned tuna can be produced under private label and OEM programs. That capability creates the clearest scope test in the range.

Inside the food safety scope. The BRCGS certificate scope names canned tuna manufacturing. On that reading, private label and OEM tuna production sits inside the certified manufacturing scope, because the scope is written around the manufacturing of the fish category rather than around a brand name on the label.

Outside the halal scope. The halal certificate scope is limited to Canned Sardines in Oil and Canned Mackerel in Tomato Sauce. Tuna is not named in it, and neither is any tuna packing medium. A private label or OEM tuna order therefore cannot be supported by that halal document as written; the scope would need to be extended before the certificate could be presented for that SKU.

Two drafting implications follow. First, purchase terms should require the supplier to state, for each SKU in an OEM program, which named products in which certificate scopes correspond to the branded item being produced. Second, terms should separate the two questions that buyers habitually merge: whether the manufacturing scope is certified, and whether the specific product form is halal-conformant under a named standard.

Writing scope-matching acceptance criteria into purchase terms

Acceptance criteria work best when they are written as evidence obligations rather than as general assurances. The clauses below are drafted so that they can be adapted directly into a supplier qualification annex or a purchase order schedule.

The combined effect of these clauses is that scope matching becomes a pre-order activity rather than a pre-customs discovery. They also give the buyer a written record of what the supplier represented at the moment the order was placed.

Pre-shipment evidence from the Xiamen and Qingdao QC teams

A scope clause is only as strong as the evidence that supports it at batch level. Certificates describe systems and named scopes; they do not certify individual cans. That is why pre-shipment inspection evidence belongs in the same clause set.

Agrogentra & CO.,LTD.XIAMEN was established in 2000 in Xiamen, China, and operates as an international trading company serving the United States, Europe, Latin America, Africa, the Middle East and multiple mainstream Asian markets, with export business accounting for 100% of total sales. Its operating model relies on stable factory resources, standardized production supervision and mature export procedures, supported by independent QC departments in both its Xiamen and Qingdao offices.

Those QC departments conduct full-process inspections covering factory audits, raw material testing, production monitoring, finished product inspection and pre-shipment sampling. The stated purpose of that process is to ensure each shipment complies with international food safety standards and customer requirements. For a buyer writing purchase terms, this is the mechanism that connects a certificate scope to a specific container: sampling and finished product inspection are performed prior to shipment release, and the records can be referenced to the order line.

Technical note: why product form and packing medium change the answer

Scope mismatch is rarely caused by paperwork carelessness alone. It is caused by the fact that in canned fish, a change of medium or container size produces a different product, and certificates name products rather than species families.

The canned seafood range in question is offered in can sizes of 125g, 170g (843#), 425g and 1000g, with variants packed in vegetable oil, in tomato sauce or brined, and a stated shelf life of 36 months at ambient temperature as fully sterilized, ready-to-eat product. Each combination of species, medium and can size is a distinct SKU with its own order line, artwork and destination declaration.

That is why the halal scope wording matters so literally. It names Canned Sardines in Oil and Canned Mackerel in Tomato Sauce. A sardine in tomato sauce or a mackerel in oil is a different product form from the named one, even where the fish species and the manufacturing line are the same.

The preservation process reinforces the same logic. Canned fish is preserved by sealing plus high-temperature, high-pressure sterilization rather than by preservatives; low-acid products such as most fish must be sterilized at high temperature under pressure, while high-acid products such as tomato-based packs can be processed at lower temperatures. Because a medium change alters the acidity and solid content of the pack, it also changes the sterilization parameters applied to that SKU. Form, process and scope move together, and purchase terms that treat them separately will keep producing mismatches.

Receiving discipline completes the chain. Cans showing swollen ends, leakage or severe rust should be quarantined rather than consumed, documented with batch number and arrival details, and reported to the supplier so the affected batch can be traced. Storage guidance for ambient canned product typically calls for a cool, dry environment and rotation on a first-in, first-out basis.

Where these terms matter most: buyer scenarios and destinations

Scope-matched purchasing terms are most valuable in application contexts where regulatory exposure and rework cost are high. Canned products of this type are supplied into food import, grocery wholesale, supermarket retail and catering channels, with long-distance sea transportation and ambient-temperature storage as the normal working conditions and direct consumption after opening as the normal use mode.

• Distributor and wholesale programs. Canned mackerel is supplied for wholesale and distribution markets, and canned squid is supplied to importers and wholesale buyers. Where a distributor resells across several markets, scope mapping prevents a single certificate from being applied to unrelated SKUs in a catalogue listing.
• Retail pack programs. Canned baby clam is supplied for retail pack programs, where label claims and listing documentation are highly visible and the cost of a scope correction after listing is significant.
• Food distributor supply. Canned Alaska pollock is supplied as wholesale supply to food distributors; because this species is not named in either scope described here, qualification evidence has to be established separately.
• Private label and OEM programs. Canned tuna produced under private label and OEM programs sits inside the certified manufacturing scope but outside the halal scope as written, which makes it the clearest case for a written scope-to-SKU annex.
• Halal-sensitive destinations. For orders referencing Malaysia MS1500:2019 or Indonesia Halal Law Regulations, the only forms currently named are canned sardines in oil and canned mackerel in tomato sauce.

Market signals behind the shift to SKU-level documentation

The commercial background supports tighter documentation practice rather than looser practice. The global canned seafood market was valued at USD 57.69 billion in 2025 by Fortune Business Insights, and canned fish accounts for 75.3% of that market according to Grand View Research. Canned tuna accounts for 43% of global canned fish import volume under HS 1604.

Market valuations should be read with care: research houses publishing canned seafood figures differ materially depending on whether they count hermetically sealed cans or a broader shelf-stable seafood definition, and published valuations have ranged broadly between firms covering the same category. The directional signal is more reliable than any single figure.

On the regulatory side, the direction is toward traceability. Regulation (EU) 2024/3115 became effective in January 2025 and mandates stricter plant health and traceability requirements for imported preserved foods, while the FDA requires foreign canned food processors to register under the Food Canning Establishment and file Scheduled Processes. Both push qualification evidence closer to the level of the individual product and batch, which is precisely where certificate scope should be read.

SKU-level scope matching versus traditional certificate filing

The traditional approach files certificates once per supplier and reviews them at annual audit or at supplier re-approval. It is efficient, and for many commodity relationships it is sufficient. Scope-level matching adds a per-order-line check and a written annex. The trade-off is real and worth stating plainly.

The limits of the recommended approach should be stated just as clearly as its benefits:

• A certificate covers a defined scope and period; it is not a guarantee for every individual can, which is why batch-level pre-shipment inspection remains necessary.
• As written, the halal certificate scope covers two product forms only. It cannot be extended by interpretation to tuna, Alaska pollock, squid, baby clam, vegetables or fruit.
• Fixed validity creates a scheduling boundary: a certificate valid from 2025-07-01 to 2028-06-30 must be re-verified at renewal, and purchase terms should require notification rather than assume continuity.
• Acceptance of halal documentation for a given destination ultimately rests with the receiving authority and the buyer's own regulatory advisers; a supplier's file cannot bind that decision.
• Scope matching adds administrative work per SKU, and for suppliers with very stable, narrow ranges the additional workload may exceed the risk it removes.

Future outlook

Three developments are likely to shape canned fish purchase terms over the next few years. First, documentation is moving toward product-level and lot-level traceability, following the direction set by Regulation (EU) 2024/3115 and by processor registration requirements such as FDA FCE registration and Scheduled Process filing. Second, halal scope is likely to be requested species by species rather than as a catalogue-level statement, because buyers in Malaysia MS1500:2019 and Indonesia Halal Law Regulation contexts need named product forms. Third, the practical center of supplier qualification will sit in the annex rather than the certificate itself: the value lies in a maintained mapping of SKU, standard, certificate number and validity, refreshed at each renewal.

For importers building qualification files now, the lowest-regret move is to write scope-to-SKU annexes into purchase terms before the next order cycle, and to require pre-shipment evidence that ties the SKU code, the certificate number and the batch identification together.

FAQ: matching BRCGS and halal scope to the shipped SKU

This reference describes how two specific certificates should be read against specific SKUs and does not constitute legal or regulatory advice. Importers should confirm destination requirements for Malaysia, Indonesia and other markets with their own regulatory advisers. The Agrogentra canned food product brochure is available for download: https://cdn.socialarks.com/sbsp/25119/common/2026/0805/Agrogentra%20leaflet.pdf