Beauty catalogs that meet INCI + regulatory + customer trust.

Catalogue Hub stores the canonical INCI ingredient list against the product record. Markets-native locales format the list per market — US FDA format (descending order by weight, allergens highlighted), EU Cosmetics Regulation format (INCI + CMR substances explicit), UK + JP variants. You update the ingredient list once at the canonical record; the locale-formatted versions propagate via Store Sync to every connected store. Quality Guard's beauty rules enforce INCI completeness as a publish-gate requirement.

Apimio AI drafts regulatory-phrased copy per market — pulling from your canonical product claims + locale-specific regulatory templates. The output is a draft for human compliance review (we don't auto-publish regulatory text without human approval). The 5–10× speed gain shifts the compliance team's work from "rewrite this per market" to "review + approve." For high-stakes regulatory phrasing (FDA structure-function claims, EU SCCS safety claims), the reviewer-in-the-loop is non-negotiable — and Apimio is built that way.

Beauty category rules in Quality Guard require sensitivity flag attribution (paraben-free, sulfate-free, fragrance-free, vegan, cruelty-free) — each as structured fields with type validation. The publish gate blocks listings missing required disclosures per category (e.g., allergen lists for fragranced products). The audit log captures every flag change with actor + timestamp, so compliance reviews + recalls become traceable.

Yes. Salons typically carry a curated professional subset (back-bar products, treatment-room kits) at salon-pro pricing tier with smaller MOQs. Retail beauty partners (multi-brand beauty retailers) carry your full retail line at wholesale tier with larger MOQs. Each gets its own portal with scope + pricing tier independently. Spa partner programs and aesthetician networks are common variations supported on the same model.

Shade-matching tools (quizzes, AR shade-matchers, virtual try-on) integrate at the Shopify storefront layer — reading product + variant data from Shopify's API. Catalogue Hub writes canonical records to Shopify; the matching tool reads from there. Extended shade attributes (undertone, finish, coverage level) live in Catalogue Hub's extensible attribute schema. Apimio coexists with these tools, not replaces them.

Subscription billing apps (Recharge, Bold Subscriptions, Shopify Subscriptions) integrate at the storefront layer reading from Shopify product data. Apimio holds the canonical product + per-store override (so subscription-tier pricing is captured via overrides). The subscription app handles the recurring billing; Apimio handles the catalog data feeding it.

For brands already on Shopify, no migration — Apimio reads existing Shopify catalogs on first sync. Typical beauty catalog (200–5,000 SKUs across markets) completes import in 10–20 minutes. INCI + regulatory backfill via Apimio AI + reviewer approval typically takes 2–4 weeks to clear. Wholesale channel rollout to existing partners is another 1–2 weeks.

Yes — Markets-native locales support every Shopify-supported language including CJK scripts. Apimio AI translation handles formal/casual register per locale, and regulatory phrasing per market. For high-stakes markets (Japan PMDA, China NMPA for cosmetics), the reviewer-in-the-loop is required — AI drafts, in-market compliance reviewer approves.

Yes. Catalogue Hub stores per-locale INCI ingredient lists with regional compliance flags. The FDA list, EU CosIng list, UK MHRA list, and JP MHLW list can differ for the same product — Apimio holds all four. Quality Guard's compliance gate ensures regional-specific INCI is complete before publish to that locale's store.

Variant Manager up to 2,048 combinations handles shade matrices easily. A foundation with 60 shades × 3 finishes × 2 sizes = 360 variants — well within scope. Each shade gets its own image, alt text, INCI, and price.