INCI ingredient lists are one of the most regulated pieces of data on any skincare product. For an upload team, that sensitivity has one practical implication: the list gets entered exactly as it appears on the brand's label, without reordering, correcting, or filling gaps.
That said, skincare ingredient data for upload teams covers more than the ingredient list alone. Volume fields in two units, skin type and concern values, hero ingredient highlights, and ingredient metafields all need to land in the right Shopify field and stay consistent across the catalog. This guide covers each one, what the team needs from you, and how to structure the brief for Shopify product data entry.
Key takeaways
- INCI ingredient lists are entered as supplied by the brand, character for character, without reordering or correction
- Volume fields for skincare typically appear in two units: mL and fl oz, sometimes also g or oz
- Skin type and concern values come from the brand's own vocabulary; the team does not apply an external taxonomy
- Hero ingredient highlights and the full INCI list are two different fields and need to be briefed separately
- Structured metafields for ingredients, skin type, and concern are worth setting up before a large upload job
The INCI ingredient list
An upload team enters the ingredient list exactly as the brand supplies it. Reordering INCI names, correcting inconsistencies (for example, "Aqua (Water)" on one product and "Water (Aqua)" on another from a different supplier), or adding items that appear to be missing is not part of the upload work.
If there are inconsistencies across products, the team flags them to the merchant before entering data. Once the merchant confirms what to use, the supplied version goes in. Reviewing the ingredient list for regulatory completeness or accuracy is the brand's responsibility, not the team's.
Where the ingredient list goes in Shopify depends on how the store is set up. A plain text block in the product description is the default. For stores that display ingredients separately or query them in the storefront, a dedicated metafield is cleaner. Shopify's metafields system supports a multi_line_text_field type that works well for INCI lists, typically under a namespace like custom.ingredients or cosmetic.inci. The metafield definition needs to exist in Shopify admin before the job starts. An upload team can populate an existing definition, but creating the definition is setup work done before briefing.
Volume and size fields
Skincare products are measured in different units depending on the market. A serum listed as 30 mL on the packaging will typically also appear as 1.0 fl oz for markets using US customary units. Stores serving both regions carry both values.
The upload brief needs to state which fields to populate and in what format. Options include Shopify's built-in product weight field (for shipping purposes, single unit), a dedicated size metafield, or a formatted string in the description such as "30 mL / 1.0 fl oz." If a product ships internationally and the store displays both values, both need to be in the source data.
The weight field in Shopify is for shipping calculations and takes a single unit. Display size, whether metric or imperial, belongs in a metafield or the description. Decide the format before the job and specify it in the brief, and the team applies it consistently across every SKU.
Skin type and concern values
Skin type (dry, oily, combination, sensitive, normal) and skin concern (brightening, anti-aging, hydrating, acne-prone) are merchant-defined categories. An upload team enters the values the brand uses, not a standardized external taxonomy.
These values go into one of three places: product tags, a metafield for storefronts that filter by skin type, or the product description. If the store uses filter navigation for skin type, a metafield is the better choice because Shopify's tag-based filtering becomes harder to maintain as the catalog grows.
When building the brief, list the exact values the brand uses and specify which field each should go into. If a product suits multiple skin types, state the format: separate tags, a pipe-delimited list, or a multi-value metafield. More upload resources for beauty and cosmetics brands are available for those managing larger skincare catalogs.
Hero ingredient highlights vs the full INCI list
Most skincare brands use two formats for communicating ingredients. The first is a short marketing list of the ingredients the product is known for: "Niacinamide 10%, Zinc 1%, Hyaluronic Acid." The second is the full INCI list required on the label.
These are different fields and need to be briefed separately. The hero ingredient list is merchandising copy, usually 2 to 6 items, that goes in the product description, a feature metafield, or a comparison table. The full INCI list goes where the label data is stored.
If both are in the brief, the upload team enters both. If only the INCI list is provided, the hero list is not created or approximated. Let your team know which fields to populate and which to leave blank.
Skincare ingredient data: what to send your upload team
Before briefing a team on a skincare catalog, gather these items:
| Data | Format | Notes |
|---|---|---|
| INCI ingredient list | As it appears on the label | One per SKU if variants have different formulations |
| Volume | mL and fl oz (both) | Confirm which Shopify fields to populate |
| Skin type values | Brand's own terms | Specify tag, metafield, or description |
| Skin concern values | Brand's own terms | Same field decisions as skin type |
| Hero ingredients | Short list as written | Separate from INCI list |
| Metafield definitions | Namespace, key, type | Set up in Shopify admin before the job starts |
For gift sets with multiple components, each component may carry its own ingredient list. See Skincare Gift Sets Handover for Shopify Upload Teams for how to structure that brief. For a broader checklist of what to prepare before any upload job, see What to Send Your Upload Team Before a Shopify Job. Related articles on uploading skincare products cover adjacent topics in this category.
FAQ
Does the upload team validate whether the INCI list is correct or complete?
No. The team enters label data as supplied. Reviewing the ingredient list for regulatory completeness or accuracy is the brand's responsibility. If something looks inconsistent across products, the team flags it before entering, then enters the supplied version unless the merchant provides a correction.
Where should the ingredient list go in Shopify?
For most stores, a dedicated metafield is cleaner than placing the ingredient list in the product description. Shopify's metafield system supports multi-line text fields that work well for INCI lists. The definition needs to exist in your admin before the job starts. Your upload team can then populate it across the catalog.
What if product variants have different ingredient lists?
If variants within one product have different formulations, the brief needs a separate ingredient list for each variant. Shopify supports metafields at the variant level, so a variant-level ingredient metafield is the cleanest approach for stores where formulations change by size or region.
Can the team enter ingredient data in two languages?
That depends on the store setup. If the store uses Shopify's multiple languages feature, the team can enter translations if the merchant provides them. Translating ingredient text, including INCI names, is outside the scope of upload work.
What Shopify fields work for skin type filtering?
Stores that use filter navigation typically store skin type values in product metafields rather than tags. Both work, but metafields are easier to maintain as the catalog scales. The field type, definition namespace, and accepted values all need to be in the brief before the team starts. See the Shopify product data entry checklist for a complete pre-job field setup reference.
