Age Range
OVERVIEW
The Age Range field specifies the recommended age span for which a children’s product is safe and appropriate. It is the first and most non-negotiable filter in the kids and baby product vertical. Parents search, filter, and purchase almost exclusively within an age range — and they have zero tolerance for ambiguity when safety is involved.
Age range is not just a convenience filter. It is a safety declaration. Small parts, choking hazards, developmental appropriateness, cognitive complexity, and physical durability all shift dramatically across age brackets. Populating this field accurately is both a product quality decision and a legal responsibility.
BUSINESS VALUE
Why this field matters
- Parents filter by age before any other attribute — an unpopulated age range field means invisibility
- Developmental toy recommendations, gift guides, and registry features all depend on structured age data
- Age range drives safety warnings (e.g. “Not suitable for under 3s”) that reduce product liability
- Gift buyers who do not know the child well rely entirely on age range to make purchase decisions
- AI-powered gift recommendation engines require structured age data to function effectively
- Search queries like “toys for 4 year olds” or “baby gifts 6 months” need structured data to match
ACF SETUP
How to configure this field in Accentuate Custom Fields
| Where | ACF dashboard → Templates tab → Product scope → Add new field |
|---|---|
| Label | Age Range |
| Name / Key | age_range |
| Namespace | accentuate (default) |
| Field type | Shopify >> Single-line text (List) — recommended for new fields |
| Multi-value | Yes — a product can span multiple age brackets (e.g. 3–5 and 5–7) |
| Note: Use Shopify >> List type so each age bracket is a separate, filterable array element. Leave namespace as “accentuate” — ACF sets this automatically and it is the correct value for Liquid access. |
|---|
STEP-BY-STEP IN ACF
- Open ACF, go to the Templates tab and select the Product scope
- Click “Add new field” in the top menu bar
- Set Label to “Age Range” — the Name/Key auto-fills as “age_range”
- Leave Namespace as “accentuate” (default — do not change)
- Select field type: Shopify >> Single-line text (List)
- Enable “Allow multiple selections” for products spanning age brackets
- Click Done, then Save in the right sidebar
- Open any children’s product in the ACF editor and verify the field appears ready to accept values
| Shopify admin (optional pinning): To pin in Shopify admin: Settings → Custom data → Products → Add definition. Namespace: “accentuate”, Key: “age_range”, Type: Single-line text (List). ACF will auto-detect the existing definition and show a green checkmark confirming alignment. |
|---|
| Repeatability: Shopify >> List types are repeatable by definition — no extra configuration needed in ACF for multi-bracket behavior. |
|---|
REFERENCE VALUES
Example values — adapt to your catalog
| Value | When to use |
|---|---|
| 0–6 months | Newborns; sensory products, soft toys, mobiles; no small parts |
| 6–12 months | Early explorers; teethers, stackers, soft books; still no small parts |
| 1–2 years | Toddlers; push toys, shape sorters, chunky puzzles; supervision required |
| 2–3 years | Early imaginative play; simple roleplay, large building blocks |
| 3–5 years | Pre-school; construction sets, basic board games, arts and crafts |
| 5–7 years | Early school age; strategy games, more complex construction, reading |
| 7–10 years | School age; science kits, complex puzzles, sports equipment |
| 10–12 years | Pre-teen; advanced STEM, hobby kits, social board games |
| 12+ years | Teen; adult complexity games, advanced creative kits |
| All ages | Truly universal; family games, general art supplies, open-ended toys |
BEST PRACTICES
-
Use the age range printed on the product packaging as the primary source of truth
-
Where packaging says “3+” populate as “3–5 years” AND “5–7 years” AND “7–10 years” to capture the full range
-
Never use age range to upsell: do not mark a product for a younger age than is safe
-
For gift products, add a note in the product description explaining why the age range was chosen
-
Keep brackets consistent across the full catalog — “3–5” and “3 to 5” will split filter results
COMMON MISTAKES
-
Entering free text like “3 and up” instead of structured bracket values
-
Leaving the field blank on products where the packaging clearly states an age range
-
Using marketing age ranges (“suitable from birth”) when the actual safety range is narrower
-
Applying a single bracket when the product genuinely spans multiple
-
Confusing age range with developmental stage — they are related but not the same field
IN CONTEXT
| Wooden Magnetic Fishing Game — 10 pieces |
|---|
| Age range: 3–5 years, 5–7 years |
| Developmental stage: Pre-school, Early school age |
| Material safety: FSC-certified wood, Water-based paint, BPA-free magnets |
| Educational benefit: Fine motor skills, Colour recognition, Counting |
| Safety certifications: CE, EN 71 |
Developer Implementation
| Liquid note: Shopify >> List type returns a metafield object. Use .value to get the array, then loop to render each age bracket. |
|---|
Liquid — Storefront Rendering
{% comment %} Age Range — Shopify >> Single-line text (List) Namespace: accentuate | Key: age_range Returns metafield object — access array via .value{% endcomment %}
{% assign age_range = product.metafields.accentuate.age_range.value %}
{% if age_range != blank %} <div class="age-range-badges"> {% for bracket in age_range %} <span class="badge badge--age">{{ bracket }}</span> {% endfor %} </div>{% endif %}| Pro tip: Use age_range in a Shopify collection condition to auto-build age-filtered gift guides. Create a “Gifts for 3–5 year olds” collection with condition: metafield accentuate.age_range contains “3–5 years”. Updates automatically as you add products — no manual curation. |
|---|
SEE ALSO
- Developmental stage — age range says when; developmental stage says what the child is ready for
- Safety certifications — age-based safety standards (EN 71, ASTM) are tied to age range
- Material safety — small parts hazards are defined by the age range of the intended user
| Full ACF documentation: help.accentuate.io |
|---|
| Metafield Definitions → Fields → Field data type → Shopify field types |
