Selling kids' clothing online in Australia carries a compliance load that adult fashion simply doesn't. Children's nightwear in sizes 00 to 14 has to be tested and labelled against a fire hazard category. Care and composition labelling sits under an information standard. Anything with a button battery, a detachable bead or a toy sewn to the front picks up its own mandatory standard. On Shopify, all of that is a data problem before it's a legal one: if the fire hazard category, the warning text, the test report and the size table live in structured metafields instead of a paragraph someone pasted into the description box, every product page renders the right warning automatically and you can audit two hundred SKUs in a morning.
Most of the stores we pick up have the labels right on the garment and nothing at all on the website. That's the gap worth closing first.
The ACCC list you need before a single product goes live
Mandatory standards under the Australian Consumer Law apply to the supplier, which includes you as an online retailer. Importing directly from a mill in Tiruppur or Guangzhou makes you the supplier, and "the factory said it was compliant" is not a defence. The ones that actually bite in childrenswear:
- Children's nightwear and limited daywear β fire hazard categorisation, testing and labelling, covering sizes 00 to 14, plus certain infant all-in-ones and paper patterns.
- Button and coin batteries β secure battery compartments and warning requirements, which catch light-up shoes, flashing badges and musical plush trims.
- Toys for children under three β small parts testing, which applies to a rattle stitched onto a bootie just as much as to a toy in a box.
- Care labelling β the information standard referencing AS/NZS 1957, so permanent care instructions and fibre content.
Drawstrings and cords around the neck and hood aren't covered by a mandatory standard the way nightwear is, but they are one of the more common reasons childrenswear gets recalled here. Design them out. A recall on a 600-unit drop costs more than the margin on the drop.
Keep the supplier's test reports. Not in someone's inbox: in a file metafield attached to the product, with the report date and the lab name. When a regulator or a marketplace asks, you want to answer in ten minutes.
Children's nightwear fire danger label requirements, and what goes on the product page
The standard sorts nightwear into four fire hazard categories based on how the fabric burns and how the garment is styled. Categories 1 and 2 carry a low fire danger label. Categories 3 and 4 carry a high fire danger warning telling the wearer to keep away from fire or heat. Close-fitting cotton pyjamas usually land low; a loose flannelette nightie or a dress-up gown with a flowing sleeve usually doesn't. Limited daywear β think an infant's cotton all-in-one that could plausibly be slept in β gets pulled into the same scheme.
We get the category wrong on the first pass more often than you'd expect, because the tech pack says one thing and the lab report says another. Always go with the report, and re-test when the fabric supplier changes, not when the style changes.
Online, the legal obligation attaches to the garment's label. But the ACCC's position on misleading conduct means that a product page showing a loose, flowing nightie with no mention of a high fire danger warning is a problem waiting to happen, and a parent who finds the warning only when the parcel arrives is a parent who returns it. Put it on the page. We render the warning as a bordered block directly under the add-to-cart button on nightwear templates, with the category stated plainly, and repeat it in the order confirmation email for category 3 and 4 items.
Product metafields for safety warnings in Shopify
Don't scatter this across the description field. Build a metaobject called something like Compliance record and reference it from the product, so a style that comes in six colourways carries one record instead of six copies that drift apart.
Fields we use on an Australian childrenswear build:
- fire_hazard_category β a single-select list: 1, 2, 3, 4, or Not applicable. Validation on, so nobody types "cat 2?".
- fire_danger_statement β the exact label wording for that category, held once centrally so a wording change updates every product.
- age_grading β e.g. not suitable for children under 36 months, where small parts apply.
- contains_button_battery β boolean, which triggers the battery warning block and a packaging rule in the warehouse.
- fibre_composition and care_instructions β structured, not freeform, so you can filter by "100% cotton".
- country_of_origin β needed for provenance claims and for customs paperwork on returns.
- test_report β file reference, admin-only access, never exposed to the storefront.
Set storefront access deliberately. The test report and the supplier reference should stay in the admin; the warning text and composition should be readable by Liquid and by the Storefront API if you ever head to headless. Metafield access control is per-definition, and the default is rarely what you want.
One practical note: do the definitions before you bulk-import the catalogue. Retro-fitting compliance metafields onto 400 live SKUs via CSV is a two-day job and a source of silent errors. If you need a hand standing the structure up properly the first time, this is the sort of work a Shopify developer on a short engagement finishes faster than a founder learning metaobjects at 11pm.
A Shopify product template for childrenswear that earns its keep
Online Store 2.0 lets you run more than one product template. Create product.nightwear alongside the default and assign it to the sleepwear collection. The nightwear template carries the fire danger section; the default doesn't render an empty box.
Order the page for a parent on a phone, because that's who is buying. Image, price with the Afterpay instalment amount, variant picker, size guide inline under the picker rather than behind a modal, add to cart, then the safety block, then care and composition, then shipping. Collapsed accordions below the fold are where size information goes to die, and size confusion is the single biggest driver of returns in this category.
Build the safety block as its own section with a conditional on the metaobject reference, so merchandisers can reorder it without touching Liquid. Then add a blocked-publish rule in your process: no nightwear product goes live without a fire hazard category set. Shopify won't enforce that for you, so it has to be a checklist item or a small private app.
Shopify size charts for kids by age and height
Australian kids' sizing runs 0000, 000, 00, 0, then 1 through 16, and the numbers are nominally ages. They're not ages. A tall three-year-old wears a 4. Parents know this, which is why the first question in every support inbox is some version of "my daughter is 104 cm, which size?"
So lead with height in centimetres and treat age as the secondary cue. Build the chart as a metaobject with one entry per size containing: size code, height range in cm, age guide, chest, waist, and inside leg. Reference the chart from the product so a 0000β2 babywear style shows the baby rows only, and a 8β16 range shows its own. One global size chart image is the lazy version and it costs you in returns.
Two things that measurably reduce swaps: put the model's height and the size worn under the hero image, and state whether the garment has growth allowance at the hem or cuff. If you sell across a wide range, add height as a filterable facet on collection pages so a parent can browse everything that fits 110β116 cm β FilterPro handles that kind of metafield-driven filtering without a theme rebuild.
Returns and exchange policy for kids' clothing in Australia
Consumer guarantees aren't optional and you can't contract out of them. If a garment has a major failure β the fire danger label is missing, a seam fails on first wash β the customer chooses between refund, replacement or compensation, and "sale items are final" doesn't apply. Write the policy so it separates consumer guarantee returns from change of mind returns, because the second one is entirely yours to design.
For change of mind in kidswear, exchange-first beats free returns. Offer a free size swap, charge for a refund return, and exclude worn underwear and swimwear on hygiene grounds with the exclusion stated before checkout, not after. Give yourself a sensible window β 30 days is standard, and a longer window over Click Frenzy and December is worth the goodwill because half those parcels are gifts bought six weeks early.
Australia Post, Sendle and what shipping lightweight kidswear really costs
Kidswear is light and small, which is the one structural advantage you have. A 500 g prepaid satchel takes two or three garments comfortably. Australia Post prepaid satchels in 500 g, 3 kg and 5 kg are the sane default because the price is flat nationally β Perth costs what Parramatta costs. Sendle is usually cheaper on metro-to-metro and picks up from your door, but it won't deliver to PO boxes or parcel lockers, and a meaningful share of regional customers use exactly those. Run both: Sendle where the address allows it, Australia Post everywhere else.
The arithmetic on a typical order, so you can plug in your own numbers. Two pairs of leggings and a pyjama set at $89 including GST. GST out at 89 Γ· 11 = $8.09, leaving $80.91. COGS $29. A 500 g satchel at $10.95. Afterpay at roughly 5% plus 30c = $4.75. Pick, pack and mailer $1.80. Gross profit: $80.91 β $29 β $10.95 β $4.75 β $1.80 = $34.41, or 42.5% of ex-GST revenue.
Now send one free size exchange on that order. A return satchel plus a second outbound is $21.90, which is 64% of the gross profit on the sale. That's the whole argument for spending a week on size charts instead of a week on ads. In a market this size, the second and third order from the same parent are where the business is, and kids grow out of everything in four months, so the repeat cycle is handed to you for free if the first fit was right.
Free shipping thresholds: set yours above your average order value, not at it. If your AOV is $72, a $99 threshold pulls a second item in. Ten-dollar flat rate below it.
Selling baby products online in Australia: a different compliance list
The moment you extend from clothing into nursery, you inherit a separate set of mandatory standards β cots and portable cots, prams and strollers with their brake and tether requirements, baby walkers, dummies, and toys for under-threes. Each has its own testing and labelling obligations, and some require specific warning text displayed with the product. Sleeping bags and swaddles aren't under a mandatory standard but attract close scrutiny around TOG ratings and hood design, and any claim about safe sleep is a claim the ACCC can test.
The same metaobject structure handles it. Add a mandatory_standard field naming the instrument the product is certified against and a required_warnings rich text field, then render it in a dedicated section on a nursery product template.
Claims, seasons and GST
Organic, ethically made, carbon neutral, Australian made β Australian shoppers respond to these and the ACCC has been actively pursuing vague environmental claims. "Eco-friendly" with nothing behind it is a liability. "GOTS-certified organic cotton, certificate number on request, sewn in Melbourne" is a selling point. Store the certification reference as a metafield and show it; specificity converts better than the adjective anyway.
On tax: GST registration is required once turnover hits $75,000, and the 10% applies to your domestic sales. If you're importing stock yourself, low-value imported goods rules mean overseas suppliers selling direct to Australian consumers charge GST on consignments at or under $1,000, while anything above gets assessed at the border. Set your Shopify tax settings to tax-inclusive pricing. Australian parents expect the shelf price to be the price.
Plan the calendar backwards from a summer Christmas. Flannelette and fleece peak from Easter through July. Back-to-school and summer basics run late December into January, which collides awkwardly with your December gift peak. Click Frenzy in November and EOFY in June are the two discount events worth building stock for.
If you're mid-build or sitting on a catalogue where the safety information lives in free text, the useful next step is small: export your products, add a column for fire hazard category, and find out how many nightwear SKUs you can't fill in. That number tells you the size of the job. We're happy to look at the structure with you β our free store audit covers metafield architecture and template logic, and the Australian market page has more on how we work with brands shipping from here.