Pet Food Documentation: Country of Origin, Allergen Statements and COA Essentials

The five documents buyers usually need to start qualification

In most pet food organizations, initial qualification for a fruit or vegetable ingredient can begin with five core documents: (1) a product specification or technical data sheet, (2) a current COA example (or typical analysis), (3) an allergen statement and cross-contact disclosure, (4) country of origin and traceability information, and (5) packaging and shelf-life information. Additional documents may be required depending on your customer channel and market (organic certificates, kosher letters, etc.), but these five form the foundation. If any of these are missing, approvals stall. If they are inconsistent (different origin statements on different documents), approvals also stall. Consistency across documents matters as much as the documents themselves.

COA essentials: what QA teams actually check

A COA is only useful if it reflects the attributes that affect production performance and finished product safety. For fruit and vegetable ingredients, the most common COA checkpoints include: solids/°Brix or dry matter (yield and consistency), acidity and pH (stability and preservative effectiveness), sensory notes or color (when relevant), and a defined micro posture. QA teams often look for clear lot identification, date codes, and test methods or references. A COA that lists “pass” without context can be insufficient in stricter organizations. In pet food, COA review is frequently integrated into receiving release procedures—so missing values can delay unloading and production.

For a full COA walkthrough, see Topic 093. For micro-spec guidance across fruit ingredients, see Topic 094.

Country of origin: why it matters beyond marketing

Country of origin matters in pet food for three main reasons: regulatory and customer requirements, traceability during investigations, and risk management. Some customers require origin disclosure; some markets treat origin as a compliance requirement. During a complaint or a recall investigation, origin and lot traceability become critical. And from a risk standpoint, origin influences supplier qualification, logistics planning, and consistency expectations. Origin statements should be consistent across documents (spec sheet, COA, invoice), and they should reflect how the ingredient is defined (single-origin vs blend). If your ingredient can be produced from mixed-origin inputs depending on season, disclose that clearly and manage it through change control.

For a dedicated traceability and lot coding guide, see Topic 099.

Traceability: what “lot coding” should accomplish

Traceability is not simply having a lot number on a drum. It is the ability to connect a finished product lot back to the ingredient lots used, and then back to supplier production and raw material records. In practice, buyers want to see that: each shipping unit is labeled with a unique lot code, the COA references that same lot code, and the supplier can provide supporting trace records quickly if needed. If your ingredient is repacked or converted (for example, a puree repacked into a different packaging format), you must know whether the lot code changes and how the chain of custody is recorded.

Allergen statements and cross-contact: why “fruit has no allergens” is not enough

Fruit and vegetable ingredients are often inherently low allergen risk, but allergen documentation is still required. Buyers are not only concerned with the ingredient itself—they are concerned with cross-contact in shared facilities, shared equipment, and shared packing lines. A complete allergen statement should address: whether the ingredient contains any major allergens, whether allergens are present in the facility, and whether controls exist to prevent cross-contact. This is especially important when pet food brands serve multiple channels, including sensitive animals and owner households with allergy concerns.

For a broader allergen and cross-contact checklist, see Topic 098.

Micro posture: how pet food plants think about risk

Pet food plants may handle fruit and vegetable ingredients in wet mixing areas where contamination can cause batch spoilage or microbial failures. Even when the ingredient is aseptic, plants want clear micro expectations and handling instructions. For aseptic purees, micro posture is often expressed through process validation plus verification tests. For non-aseptic or post-open handling, plants may require defined time-in-use and storage rules. The documentation should align with the real handling workflow: how the ingredient is received, stored, connected, used, and cleaned.

For plant-handling and storage controls in pet food facilities, see Topic 084.

Packaging specs: why fitments, liners, and shipping units matter

Packaging is often treated as a logistics detail, but in pet food plants it is a processing variable. If the puree is delivered in bag-in-box or totes, fitment type affects how it connects to pumps and dosing systems. Liner integrity affects contamination risk. Drum and tote dimensions affect storage and handling. For consistent production, define packaging expectations: drum/tote size, liner type, fitment, pallet pattern, and whether the packaging is food-grade and suitable for your plant’s receiving standards.

For a packaging overview across fruit/veg ingredients, see Topic 096.

Certifications and special requirements (organic, kosher, etc.)

Certifications are common in premium pet food lines. If your brand claims organic, ensure certificates are current and match the specific product and facility scope. If kosher letters or other third-party confirmations are requested, confirm availability early. The operational rule is simple: certifications should be treated as controlled documents with expiration dates, and changes must be managed through supplier change control. Availability varies by item and supplier—so build flexibility into your sourcing plan.

Supplier change control: the most overlooked “document”

One of the biggest reasons pet food approvals break after launch is unannounced change: a new origin, a new processing method, a new packaging fitment, or a different solids range. Change control is what prevents those surprises. Buyers often request a supplier statement describing which changes will be communicated, how far in advance, and what documentation will be provided. If your brand depends on consistent kibble texture or wet gravy viscosity, change control is not optional. It protects production schedules and protects product identity.

Practical qualification checklist (use this before your first PO)

Before issuing the first purchase order, confirm you have: a signed specification sheet, a current COA example, an allergen statement with facility cross-contact disclosure, an origin/traceability statement, packaging specifications with fitments, shelf-life and storage guidance, and (when applicable) certifications. Also confirm how lots will be labeled and how quickly trace records can be produced. If you are using co-manufacturers, confirm they accept the documentation set and packaging format. This saves weeks of back-and-forth once the first shipment is on the dock.

Next steps

If you share your pet food application (kibble, wet, topper, treat), destination market, packaging preference (drum/tote/bag-in-box), and your organization’s documentation requirements, PFVN can recommend fruit and vegetable ingredient formats and provide procurement-ready documentation sets where available. Use Request a Quote or visit Contact. You can also browse Products and Bulk Juice Concentrates.

Continue reading: Topic 082 — Fermented Fruit Ingredients in Animal Nutrition • Back to Academy index

Previous article: Topic 080 — Fruit Inclusions in Pet Kibble
Academy index: All 100 industrial application guides
Next article: Topic 082 — Fermented Fruit Ingredients in Animal Nutrition