Most product categories give you a title, a description, and a price. Pet food gives you a nutrient analysis panel, an AAFCO nutritional adequacy statement, an ingredient list ordered by regulatory requirement, and feeding guidelines by animal weight. Getting the right pet food data for upload teams to process accurately, in the right format, is what separates a clean catalog from one that stalls mid-job.
Key takeaways
- Pet food has regulated label elements (AAFCO nutritional adequacy statements, nutrient analysis panels, ingredient lists) that your upload team enters word for word from the supplier's label; they do not rewrite or correct this copy.
- Life stage, species, and protein source are the three variant axes most pet food ranges use; not every range needs all three as Shopify options, but you need to decide upfront.
- Feeding guidelines and pack weights belong in the product description and in dedicated custom fields; send metric and imperial values to your team.
- "Senior" is a marketing term, not an AAFCO-defined life stage. Senior products usually carry an Adult Maintenance AAFCO statement, so the team enters what is on the label, not what the product name implies.
- A pet food upload brief that flags the regulated fields in advance saves significant back-and-forth during the job.
What makes pet food data different
Pet food is one of the few e-commerce product categories where label copy is partly set by regulation, not by the merchant's preference. In most countries, pet food manufacturers must include a nutritional adequacy statement (in the US and many markets, this follows AAFCO guidelines), a nutrient analysis panel, a complete ingredient list in descending order by weight, feeding directions, and species designation. This text must appear on the product, often in a specific format.
For your upload team, this creates a different working situation than apparel or homewares. With most products, they can clean up a messy supplier spreadsheet, standardize descriptions, and fill in gaps. With regulated pet food label data, they enter what is on the label exactly. They flag inconsistencies, but they do not correct or reorder ingredient lists, rephrase a nutrient analysis, or rewrite a nutritional adequacy statement. That distinction matters when you write your upload brief.
Core product fields for every pet food listing
Before the regulated label data, your team needs the standard product fields filled in your brief:
| Field | What to send | Notes |
|---|---|---|
| Product title | Brand + species + protein/flavor + life stage + pack size | Set your naming convention once and apply it across the range |
| SKU | Your internal SKU per variant (per size, flavor, or life stage) | One SKU per variant row: never share a SKU across variants |
| Barcode (GTIN) | Product-level EAN or UPC from the label | Outer carton barcodes are different; confirm which code you want in Shopify |
| Vendor | Brand name exactly as the manufacturer spells it | Used for filtering and collections in Shopify |
| Product type | Your category (e.g., Dry Dog Food, Wet Cat Food, Dog Treats) | Set a consistent list before the upload starts |
| Weight (product) | Net weight of each variant, metric and imperial | Example: 3 kg (6.6 lb). Both units prevent customer confusion |
| Shipping weight | Packed weight per unit for calculated shipping rates | Different from product net weight; include both |
| Tags | Species, life stage, protein, and dietary type (grain-free, etc.) | Agree on your tag vocabulary before the job; changes later mean bulk edits |
Label copy your upload team enters as supplied
These four label elements are regulated in most markets. Your upload team copies them from the source and does not paraphrase or correct them. Send the exact label text for each product in your brief.
Nutritional adequacy statement. In the US, this follows AAFCO guidelines and appears in a specific format: either formulation-based ("formulated to meet the nutritional levels established by the AAFCO Dog Food Nutrient Profiles") or feeding-trial-based ("Animal feeding tests using AAFCO procedures substantiate..."). The statement names the life stage and, in some cases, the specific breed life stage. Copy it verbatim from the label; do not shorten or paraphrase.
Nutrient analysis panel. The required minimums (crude protein, crude fat) and maximums (crude fiber, moisture) must appear as printed. Some brands add additional rows (ash, omega fatty acids, taurine). Include all rows in the order they appear on the label.
Ingredient list. Ingredients are listed in descending order by weight before processing. This order is set by the manufacturer and is not something your team rearranges. Supplier files sometimes list ingredients in a different order for internal reasons; flag the discrepancy to the brand rather than correcting it yourself.
Feeding guidelines. These are by animal weight and sometimes by age bracket. They are not regulated in the same way as the above three, but they should still be entered as supplied, since the quantities have safety implications. Most feeding guides use metric weights (kg) and may also include cups or cans; include all units in your brief.
One practical note on the nutritional adequacy statement: "senior" is a marketing life stage, not one defined by AAFCO for nutritional profiles. A product labeled "for senior dogs" typically carries an Adult Maintenance AAFCO statement (since AAFCO defines Growth, Adult Maintenance, All Life Stages, and Gestation/Lactation, not Senior). If your brief says "enter the AAFCO statement for each product," your team knows to enter what is on the label, which may say Adult Maintenance, not what the product name implies. This prevents a common upload error on senior ranges.
For more on US labeling requirements, the FDA's pet food guidance and the AAFCO website are the primary references, as of November 2026.
Life stage, species, and flavor variants
Pet food ranges often have three natural variant axes: species (dog, cat), life stage (puppy, adult, senior), and flavor or protein source (chicken, salmon, beef). The challenge is that Shopify allows up to 3 options per product (as of November 2026, per the Shopify product details help page), so you can structure variants to cover all three, but only if every combination exists as a real SKU.
If your range has 2 dog life stages x 4 flavors = 8 variants, that is manageable as one product with two options (Life Stage and Flavor). If you also stock cat versions with different SKUs, those are typically separate products. Decide your variant structure before the upload starts, because restructuring mid-job means rebuilding products from scratch.
What to send your team for variants:
- A clear list of every option name and value, spelled consistently ("Puppy", not "Puppy/Junior" on some rows)
- The exact SKU for every combination
- Whether any combination is out of stock or discontinued
- Whether flavor names match the label exactly (supplier files sometimes use shorthand, such as "Chkn" instead of "Chicken")
For ranges with a senior product line: decide whether "Senior" is an option value (a variant) or a separate product. If it is a variant, its SKU should differ from Adult products. Your team will flag this, but deciding upfront avoids a mid-job pause.
Preparing pet food data for your upload team
The job runs faster when your brief addresses the regulated fields explicitly. A general upload brief that says "include all product details" leaves gaps that require the team to stop and ask. A pet food brief that names the four label fields, confirms who copies them, and flags where the supplier data might not match the label saves multiple rounds of back-and-forth.
Shopify product data entry for pet food covers the full job: from structuring the variant tree to entering the nutrient analysis for every SKU. The quality of the output depends on the quality of the brief you send.
For context on what a complete upload brief contains beyond the pet food specifics, see What to Send Your Upload Team Before a Shopify Job. That article covers the general structure; the template below adapts it for pet food's regulated fields.
For ongoing catalog work across a full pet food range, the Shopify Product Data Entry Checklist covers the field-by-field preparation steps that apply to every upload.
Pet food upload brief template
Use this structure when briefing your upload team on a pet food catalog. Adapt the fields to your range.
| Brief section | What to include |
|---|---|
| Range overview | Brand name, species (dog / cat / other), product types (dry / wet / treats / supplements), total SKU count |
| Variant structure | Options used (Life Stage, Flavor, Size), all valid combinations, discontinued or out-of-stock SKUs flagged |
| Title convention | Your naming format, e.g., "[Brand] [Species] [Protein] [Life Stage] [Pack Size]" |
| Regulated label fields | Confirm: enter AAFCO statement, nutrient analysis, and ingredient list exactly as printed on the label. Flag any discrepancy between supplier file and label. |
| Feeding guidelines | Enter as supplied. Include metric and imperial values. Note the animal weight range and any age/size bracket. |
| Product weights | Net weight per variant (metric + imperial). Packed/shipping weight per variant. |
| Barcodes | Product-level EAN/UPC per variant. Confirm: not outer carton barcodes unless specified. |
| Tags to apply | Agreed vocabulary for species, life stage, protein, dietary type (grain-free, raw, etc.). One tag list for the whole range. |
| Collections | Which Shopify collections each product belongs to (e.g., Dog Food, Puppy Range, Grain-Free). Pre-built or to be created? |
| Source files | Supplier spreadsheet, label scans or PDFs (for regulated copy), image files with naming convention |
For a pet supplies product upload service overview, the industry page sets out what our team handles for the category.
Not sure yet? Send us a sample of your product data and we will show you what we would do with it.
Frequently asked questions
Does my upload team correct ingredient list errors?
No. Ingredient lists for pet food are regulated and must reflect what the manufacturer submitted for approval. Your upload team enters the ingredient list exactly as it appears on the label and flags any discrepancy between the supplier file and the label copy, but they do not correct or reorder it. Resolution goes back to the brand.
How should I handle a product range that has both dog and cat versions?
Structure them as separate products, not as an option within one product. Species affects the AAFCO statement, the feeding guidelines, weights, and ingredient profiles, and shoppers filter by species. Two products with a shared brand and naming convention are easier to manage than one product with a species option.
What is the difference between a product barcode and an outer carton barcode?
The product barcode (EAN or UPC) is printed on the individual retail unit (the bag, can, or box a customer buys). The outer carton barcode identifies the trade case (typically 6 or 12 units) used in warehousing. Shopify's barcode field is for the product-level code. Unless you sell by the case, specify the product-level EAN or UPC in your brief and confirm this with your team upfront to avoid carton codes being entered by mistake.
Does every pet food product need a custom field for feeding guidelines?
Not necessarily. Short feeding guidelines fit in the product description. Longer or tabular guidelines, where the serving varies by animal weight across multiple bands, work better in a metafield so they can be displayed in a consistent layout. Decide how you want feeding guidelines to appear on the product page before the upload, and tell your team which field to use.
How do I handle a supplier file where flavor names are abbreviated or inconsistent?
Standardize the flavor names in your brief before sending it to the upload team. List every variant name as you want it to appear in Shopify, for example "Chicken" not "Chkn", "Salmon and Potato" not "Slmn/Pto". Include the mapping from supplier shorthand to your published name. This is a decision that only you can make, because it affects your store's customer-facing labels, not internal data.
