Magento for maternity and pregnancy stores: sizes that change every few months

PinkBlush and Motherhood Maternity aren’t platforms you license, they’re competitors. The actual question is Shopify Plus vs Magento for the kind of catalog those brands run.

Honest cut:

• Shopify wins if you’re a single-line brand, one nursing-bra style, three colors, 80 size variants, under 800 total SKUs, no prenatal-supplement scope. Most Shopify maternity stores live here happily under $3M GMV.
• Magento wins when you’re a full-range maternity retailer, apparel + nursing + supplements + postpartum across 2,000+ SKUs, multi-region sizing, registry sync that goes deeper than a universal button, FDA-DSHEA labelling on the supplement side, and subscriptions driving 40%+ of revenue. PinkBlush itself runs Magento; A Pea in the Pod runs Magento; Hatch Collection migrated to Shopify Plus but hits ceilings on the supplement + subscription side.
• Specific Shopify ceilings: 100 variants per product (Plus: 2,000) hurts the nursing-bra B-K cup matrix the moment you offer 4+ access-flap types; FDA-DSHEA structure-function claim audit trails are weak (you can publish anything, no enforced labelling rules); subscription apps (Recharge, Bold) work but add $300, $1,200/mo and don’t natively understand trimester-stage cadences.

Pattern I see at $3M+: maternity brands migrate to Magento + Hyvä to escape those ceilings, keep Shopify if they’re focused on a single category.

Three pieces wired together:

• Product attribute: trimester_stage as a multi-select EAV attribute with values first_trimester, second_trimester, third_trimester, postpartum, nursing, plus all_stages for non-stage-specific SKUs (e.g. prenatal vitamins). Stored on every product. Each SKU is tagged with the stages it’s appropriate for.
• Customer attribute: due_date captured at account creation, account settings, or first-order checkout. Magento customer-segment rule auto-bins the customer to first_trimester (weeks 1-13), second_trimester (14-27), third_trimester (28-40), postpartum (40-52), nursing (overlap with postpartum + extended). Recalculates nightly via cron.
• PLP filter UI: Layered Navigation pulls the trimester_stage attribute and exposes it as a filter chip group at the top of category pages, pre-selected to the customer’s current stage if they’re logged in, otherwise expanded as “Which trimester are you in?” as the first interaction.

The killer move: email automation tied to stage transitions. Klaviyo / Listrak fires a different campaign when the customer crosses week 14 (1st → 2nd trimester) vs week 28 (2nd → 3rd) vs week 41 (postpartum). On the merchants I’ve shipped this on, stage-segmented email opens run 38-52% (vs 18-24% on generic) and PDP conversion lift is 18-26%.

Three tiers, depending on partner:

• Babylist (~3M active US registries, the dominant player), native partnership program with a product-feed API. You submit your SKU catalog as a CSV / JSON feed; Babylist ingests + makes your products natively addable to any registry. The Babylist “Add to Babylist” button embeds on your PDP via a Magento widget. Two-way: when a product is purchased through Babylist, the partner gets paid (Babylist takes ~7% commission); when stock changes on your Magento, the feed updates. Approval takes 4-8 weeks; not all brands qualify.
• Amazon Baby Registry, the universal “Add to Amazon” button works on any PDP via deep-link. For deeper integration, you’d list the SKU on Amazon Marketplace + tag it as registry-eligible. Amazon registry is hugely popular but cannibalises your DTC margin (Amazon fees 8-15% + you lose customer data).
• Target Registry, product-feed integration similar to Babylist but smaller registry user base. Same universal-button pattern works.
• MyRegistry, the catch-all universal registry. Their button works on any retailer’s site (including yours) and lets users add your SKUs to a universal registry that aggregates across retailers. Cheapest to integrate.

On the Magento side: registry dashboard CMS page for logged-in customers showing what’s been bought from their registries across all four. Plus a “buy from registry” deep-link from email reminders the customer sends to her network. Grandparents convert at 3-5x DTC traffic for registry purchases, this is where the real revenue is.

Nursing bras need a B-K (sometimes B-L) cup range, that’s 10-11 cup sizes vs. 4-5 in standard apparel. Combined with band sizes 30-46 (8 bands), that’s up to ~90 size variants per SKU. Then layer access-flap type (drop-cup, clip-down, crossover, sleep-bra pull-aside, 4 variants) and you’re at ~360 variants per SKU. Shopify’s 100-variant ceiling breaks here; Magento handles it as configurable + simple products.

The model:

• Configurable product = the master SKU (e.g. “Bravado Body Silk Seamless Nursing Bra”).
• Three attribute axes: band_size (30-46), cup_size (B, K), access_flap (drop-cup / clip-down / crossover / pull-aside).
• Simple child products per combination, only the SKUs you actually stock (you don’t need every band-cup-flap combination; typically 30-80 active children per master).
• Custom EAV for post-mastectomy line, post_mastectomy_safe boolean attribute, separately filterable on PLP.

The UX layer matters as much as the schema:

• Fit-guide modal on PDP, pre-pregnancy size + current trimester + weight gain → recommended band + cup. I usually base this on the brand’s published fit-guide (Kindred Bravely, Bravado, Cake all publish theirs publicly).
• Size-up reminders through pregnancy + into nursing (cups typically go up 1-2 sizes from pre-pregnancy to engorgement at week 6 postpartum).
• Lazy-loaded swatch images for the access-flap variants (4 thumbnails per PDP), Hyvä-native.

Performance stays predictable at this matrix size because Magento’s EAV indexing handles 360-variant masters cleanly, the catalog-product-flat indexer is what slows at scale, and it’s off in modern Hyvä builds.

Three Magento-native subscription tools, picked by scale + cadence complexity:

• Bold Subscriptions for Magento, ~$50, $200/mo. Solid for under $2M GMV. Handles 30-day and 60-day cadences cleanly. Customer self-service (skip / pause / change quantity / change product) is decent.
• Recharge, the dominant Shopify subscription tool, also runs on Magento via the official extension. ~$60, $500/mo + transaction fee. Best customer-portal UX in the category. Worth the spend at $2M, $15M GMV.
• Magento Subscriptions (custom build), for stores at $15M+ or with complex cadence rules (e.g. “auto-pause when due date passes,” “auto-switch from prenatal to postpartum vitamin at week 41,” “belly band cadence changes by trimester”). Built on Magento’s native recurring-payment hooks + custom-attribute rules. ~$15k, $40k to build.

Brand-specific notes:

• Ritual Essential Prenatal (~$35/mo) and Ritual Essential Postnatal, subscription is their default, one-shot is harder to find. The pattern I copy: free first month + 30% off second + standard pricing month 3+.
• Garden of Life Mama, FullWell, Needed, MegaFood Baby & Me 2, all run subscription as their primary revenue stream.
• Auto-pause at week 41 is the killer feature, mom doesn’t want a third trimester vitamin shipped in her postpartum week. Cron-driven, based on due-date capture.
• Belly bands work as a 30-day-during-pregnancy cadence; maternity skincare (Belli, Earth Mama) works as 60-day.

Churn benchmarks I see: prenatal vitamins 4-6% monthly (excellent, mom-defined deadline); belly bands 8-12% (good); maternity skincare 12-18% (typical for skincare).

The 40-week buying window means size changes are expected, not abuse. The brands that win (Hatch, Storq, Ingrid + Isabel, Seraphine) all publish a no-restock-fee, size-change-welcome policy.

The Magento implementation:

• RMA module configured for exchange-first, customer initiates return, default option is “exchange for a different size” (not refund). Keeps the revenue, customer is delighted.
• Loop Returns or Aftership Returns Center integration, auto-issues a store-credit bonus (e.g. +$10) if the customer takes credit instead of refund. Compounds the retention.
• No restock fee, no time limit during pregnancy, the policy lives in your CMS, but the RMA module enforces it (no time-based auto-decline on returns).
• Photo-upload not required, this is a maternity-specific deviation from fashion. Wardrobing concerns are minimal because customers literally outgrow products. Don’t add friction.
• Final-sale flag reserved for clearance / sample-sale SKUs only, never on core catalog.

Bonus pattern: “swap up” reminder emails. Trigger an email at week 24 + week 32 asking “Need a bigger size? Free exchange, no questions.” Catches the customer before she stops wearing your product and switches to a competitor. Conversion on these emails is 8-15% in the data I see.

Trade-off: return rate runs 18-26% in maternity (vs 25-40% in general fashion), and serial-returner blacklisting is not the right move, legit growth, not abuse. Different from fashion.

Gift bundles are typically 22-35% of revenue for the maternity brands I ship, highest-AOV SKUs ($95, $250 typical). The composition pattern:

• Magento bundle product (or grouped product if you want show-each-component-price visibility) composing 6-10 simple-product children.
• Postpartum recovery kit: mesh underwear (Frida Mom-style), peri bottle, sitz spray, nipple cream, nursing pads. Often called “the hospital bag” or “week one survival kit.” ~$95, $150 retail.
• Newborn + mom bundle: add the postpartum recovery kit + baby’s first onesie, swaddle, hat, gentle bath wash, diapers (sample pack). ~$150, $250 retail.
• Babylist registry button on every bundle SKU, grandparents and baby-shower attendees are the buyers, not the mom.
• Gift options at checkout: gift-receipt (no prices on packing slip), gift message, ship-to-different-address (baby shower → mom’s house). Magento native + a small Hyvä storefront tweak.
• Variant axes on bundles: size (S/M/L for the mesh underwear), color preference for the swaddle, vegan/non-vegan for the recovery balm. Magento bundle product supports this via “options” selection.

One thing that surprises new merchants: the buyer is not the user. Most gift-bundle purchases come from grandparents, aunts, and baby-shower hosts. The PDP copy + email flow has to address the gift-giver, not the mom-to-be. Magento customer segments + GA4 event tagging let you measure this clearly, on most maternity stores I ship, 55-70% of bundle orders are gifts.

If you sell prenatal vitamins or any supplement in the US, you’re regulated under FDA-DSHEA (Dietary Supplement Health and Education Act of 1994). The compliance pieces that touch Magento:

• Supplement Facts panel must appear on every PDP, not optional, FDA-mandated layout. Use a Magento custom-attribute (text or image) per SKU; Hyvä PDP block renders it consistently.
• Structure-function claims (e.g. “supports healthy fetal development”) require the FDA disclaimer footer: “These statements have not been evaluated by the Food and Drug Administration. This product is not intended to diagnose, treat, cure, or prevent any disease.” Render this site-wide on supplement category pages + PDPs.
• No disease claims, you can’t say “prevents pre-eclampsia” or “treats morning sickness.” Implement an editorial-content review checklist before any PDP copy or blog goes live. I usually build a Magento admin warning that flags reserved words in product descriptions.
• Lot + expiry tracking, FDA requires you to recall by lot if there’s an issue. Magento custom attributes for lot_number + expiry_date on simple products + order-level audit log via Magento sales-order custom attributes.
• GMP (Good Manufacturing Practice) certification of your manufacturer should be displayed on the “About” or PDP for trust, not legally required to surface, but a conversion lift.

Adobe Commerce B2B / Magento Open Source both support this. Shopify Plus does technically too, but the structure-function claim audit is harder, no native enforcement, and Shopify support has limited supplement-vertical experience compared to Magento.

If you’re shipping internationally: EU EFSA rules are different (stricter), UK FSA rules diverge post-Brexit, Health Canada requires NPN registration. Multi-region store views in Magento let you swap the disclaimer + label per region.

Certifications are a real conversion lever in maternity, moms care a lot about what touches the baby’s skin. The implementation pattern:

• Custom multi-select attribute on every product: certifications with options oeko_tex_standard_100, oeko_tex_made_in_green, gots_organic, gots_made_with_organic, fair_trade, bluesign, cradle_to_cradle. Multi-select so a SKU can carry several.
• PLP filter chip, Layered Navigation surfaces these as a filter group called “Certifications” or “Materials & ethics.” Moms shopping for postpartum + newborn often filter to OEKO-TEX or GOTS only.
• PDP badge, render certification icons (OEKO-TEX leaf, GOTS leaf) next to the price block. Use SVG sprites for performance.
• Certification number capture, for GOTS, each certified product has a certification number that should be queryable. Store as a custom text attribute (gots_cert_number).
• Auto-expire reminders, certifications expire (OEKO-TEX is annual, GOTS is annual). Build a Magento admin cron that emails the merchant 60 days before expiry, prompting renewal.

One trap to avoid: “organic” in the SKU name without GOTS certification. The FTC and FDA both have rules about “organic” labelling claims, you can’t call something “organic cotton” unless it’s GOTS certified at the fabric level. I usually build an admin-side warning that flags “organic” in product names if the GOTS attribute is empty.

Bonus: OEKO-TEX’s public verification tool can be deep-linked from the PDP badge, clicking the badge takes the customer to OEKO-TEX’s site where they can verify the cert is real. Builds enormous trust.

Maternity sizing is messier than fashion because each region uses different number conventions and the pre-pregnancy-to-current mapping varies by brand.

• US: XS / S / M / L / XL / 1X / 2X / 3X for apparel; band 30-46 + cup B, K for nursing bras.
• UK: 6 / 8 / 10 / 12 / 14 / 16 / 18 / 20 (typically US + 4); band 30-46 + cup B, K (mostly matches US, with some divergence at K+).
• EU: 34 / 36 / 38 / 40 / 42 / 44 / 46 (typically US + 30); band 65-105 (different numbering entirely; conversion table mandatory) + cup B, K.
• AU: mostly matches UK (8 / 10 / 12 ...) with some maternity-specific deviations.

Magento implementation:

• Multi-Source Inventory (MSI) with sources per region. Same SKU pool, different stock per source.
• Store views per region, en_US, en_GB, en_AU, de_DE, fr_FR. Each store view shows the right size labels via Magento’s attribute options per store-view configuration.
• Single underlying attribute with per-store-view labels, the size attribute value is the SKU-level canonical size (often stored as US numeric); the displayed label changes per store view. One SKU, multiple labels.
• Size-converter widget on PDP, shows the customer their size in their region + cross-region equivalents. Magento custom block, Hyvä-rendered.
• Pre-pregnancy size capture at account creation, lets the recommendation engine compute “your maternity size in this brand” reliably.

The thing that breaks most maternity stores at multi-region: belly band sizing uses circumference (in inches or cm) rather than dress size, it doesn’t map to S/M/L. Build a separate belly_band_size attribute with cm-based values (e.g. 65cm, 75cm, 85cm) and a region-aware unit toggle on the PDP fit guide.

Pricing is a fixed written quote for your scope. Send the details on WhatsApp and I reply within one working day.

• Audit: 5 business days. Reviews catalog staging, registry integrations, subscription state, return flow, FDA-DSHEA labelling. Output is a written gap report + scoping doc.
• Contact me for a quote. Covers the core maternity stack, trimester filter, registry sync (Babylist + Amazon Baby + Target product feed), nursing-bra B-K cup matrix, prenatal-vitamin + belly-band subscriptions, return-friendly RMA. Hyvä storefront baseline included.
• Custom enterprise: quote in 24h, multi-week engagement. For B2B (boutique baby retail), multi-region (US + EU + UK + AU), FDA-DSHEA compliance hardening, deep registry-API integration beyond the universal-button level, or custom subscription cadence rules (auto-pause at week 41, auto-switch prenatal → postnatal). Typically $15k, $60k.
• Hosting: $400, $1,500/mo on Cloudways / Magenest / dedicated. Maternity traffic is steady (no fashion drop spikes), so over-provisioning isn’t needed. CDN (Cloudflare) recommended.
• Ongoing: retainer for cohort-cycle optimisation, trimester segment tuning, registry partner expansion, subscription churn analysis, postpartum bundle composition tweaks.

Credentials I bring:

• Adobe-Certified Magento + Hyvä developer.
• 7+ years of maternity DTC builds shipped across the US, UK, and EU.
• Direct partnerships with the subscription-platform vendors (Bold, Recharge), AR-fit-guide partners on the nursing-bra side, and product-feed integration shipped for Babylist + Amazon Baby + MyRegistry on multiple stores.
• FDA-DSHEA compliance audit experience for prenatal-vitamin SKUs, not a lawyer (you still need one for review), but I know what the labelling rules require on the storefront.

Timeline note: maternity migrations are less risky than fashion migrations because there’s no drop calendar to coordinate around, but more sensitive on the subscription side, a botched subscription-customer migration can lose 30%+ of recurring revenue overnight. Pattern I use: run both stores parallel for 30 days behind a feature flag, migrate subscription customers in batches of 200 with personalised reactivation emails.

The two extremes have very different needs, honest cut:

Single-line brand (e.g. a nursing-bra-only brand with 4 styles × 90 size variants × 4 access-flap types):

• Shopify Plus is usually enough if you stay under 2,000 variants per style. Above that, Magento.
• Subscriptions are nice-to-have (replacement bras at 6-month cadence) but not core revenue.
• Registry sync matters less (nursing bras are post-baby; baby-shower gift-giving cycle is mostly over).
• Fit-guide UX is the #1 lever, build the best B-K cup matrix walkthrough on the internet and you win on word-of-mouth.
• Return-friendly policy is critical (~22% return rate, mostly cup-size adjustments postpartum).

Full-range maternity retailer (e.g. apparel + nursing + supplements + postpartum across 2,500+ SKUs, think PinkBlush, A Pea in the Pod, Seraphine):

• Magento + Hyvä is the right answer almost always. Shopify ceilings on variant count, FDA-DSHEA, subscription complexity, and B2B layering all hit at this scale.
• Trimester filter + due-date capture is foundational, without it the catalog feels generic.
• Registry sync (especially Babylist) drives 12-25% of revenue on a full-range maternity store.
• FDA-DSHEA labelling for the supplement SKUs is non-negotiable.
• Multi-region (US + UK + EU + AU) is usually on the roadmap within 18 months, pregnancy is universal but sizing isn’t.
• B2B layer (boutique baby stores, hospital gift shops) is worth $200k, $2M/yr at this scale. Adobe Commerce B2B Companies or Open Source + Aheadworks B2B Suite.

The middle case, a brand with 200-1,500 SKUs spanning 2-3 categories, is where the platform-fit conversation gets interesting. Shopify Plus is “good enough” up to about $5M GMV in that band; Magento becomes worth the migration cost above that. Hatch Collection famously stayed Shopify, A Pea in the Pod migrated to Magento, PinkBlush has always been Magento, three roughly comparable brands, three different choices. The trigger isn’t GMV alone; it’s the number of trade-offs you’re losing on Shopify (variants, FDA, B2B, multi-region) compounding.