Loading WardrobeIt

Developer documentation

WardrobeIt technical overview for merchants and integrators.

Architecture, Shopify setup, merchant portal controls, storefront widget embed, shopper journeys, and the public plugin API — compiled from the shipping product (August 2026).

  • AudienceMerchants, agencies, evaluators
  • PlatformShopify now · WooCommerce planned
  • SurfacesWidget · Portal · Plugin API

Overview

What WardrobeIt is — and what shoppers experience

A B2B AI stylist embedded on the merchant’s Shopify storefront. Shoppers stay on the brand site; catalog, checkout, and customer relationships stay with the merchant.

Three product jobs

Stylist chat

Natural-language discovery against this catalog only — occasion, budget, style, or size.

Catalog search

Fast structured search over synced inventory. No cross-store mash-ups or invented SKUs.

Virtual try-on

Eligible Growth+ previews with guided capture — QR on desktop, camera on mobile. Not a fit guarantee.

Typical shopper journeys

  1. 01
    Discover

    Describe a need; assistant may clarify, then shows in-catalog products.

  2. 02
    This product

    On a PDP, sizing and try-on refer to the garment on the page.

  3. 03
    Try on

    Capture → confirm → preview → note, cart, or alternatives.

  4. 04
    Complete the look

    Multi-product cards from the same store when a hero item is in focus.

  5. 05
    Buy

    Add to cart and checkout remain on Shopify. WardrobeIt does not process cards.

Architecture

Three components, one tenant per Shopify store

The shopper browser talks to WardrobeIt’s plugin API with a storefront key, and to Shopify cart endpoints on the store origin — never directly to Shopify Admin.

LayerRoleUser
Storefront widgetReact in Shadow DOM · wardrobeit-widget.jsShoppers
Merchant portalConnect, sync, appearance, try-on, analytics, billingBrand / ops
API gatewayAuth, search, try-on jobs, keys, metering, StripeWidget + portal
Catalog storePostgreSQL per store · Redis for jobs/sessionsAPI only
ShopifyOAuth, Admin API, webhooks, /cart/add.jsMerchant + shopper

Capabilities

Live in production vs portal preview

Do not sell coming-soon portal screens as shipped capabilities. Plan limits and prices are API-backed — see Pricing.

Live Production today

  • Overview, store health, usage meters
  • Revenue & attribution (with approved order webhooks)
  • Assistant control — color, logo, launcher, Classic / Studio skin
  • Message manager — per-page greetings and starter chips
  • Virtual try-on — SKU enablement, consent, retention copy
  • Connections & catalog — OAuth, sync, plugin keys, merchant brief
  • Multi-store, session analytics, billing & usage

Coming soon Portal preview only

  • Executive reports, recommendation rules, offers & coupons
  • Leads & audiences, support handoff, multichannel marketing
  • Product intelligence, ops AI recommendations
  • Team permissions, agency white-label
  • WooCommerce connector stub

Setup & embed

Install on Shopify and embed the widget

Preferred path: OAuth from the merchant portal, then enable the theme app embed. Liquid snippet is the documented fallback.

OAuth path (recommended)

  1. Portal → Connections & Catalog → Install on Shopify.
  2. Enter brand.myshopify.com and approve the app.
  3. Copy widget key ss_live_… when shown (once).
  4. Theme Editor → App embeds → enable WardrobeIt stylist.
  5. Paste API key, base URL, script URL. Test message + product card on storefront.

Custom app token fallback: Admin token with read_products + read_content.

Embed attributes

data-api-keyRequired · ss_live_…
data-api-baseRequired · …/api/v1
data-page-typehome · product · collection · cart
data-product-idCatalog UUID on PDP

Portal & catalog

Merchant portal surfaces and catalog sync

The portal is the control plane for widget behavior, VTO policy, and Shopify catalog ingestion. API keys and OAuth tokens stay server-side.

Portal modules (live)

  • Overview — health, sync status, quick actions
  • Assistant — branding, launcher, Classic / Studio
  • Messages — page-type greetings and chips
  • Try-on — SKU toggles, consent, retention
  • Connections — Shopify OAuth, plugin keys
  • Catalog — sync jobs, metafield mapping

Catalog pipeline

  1. OAuth or custom app token registers the store.
  2. Background sync pulls products, variants, images, tags.
  3. Metafield wardrobeit.id maps Shopify → catalog UUID.
  4. Widget passes data-product-id on PDP for context.
  5. Re-sync on demand from Connections & Catalog.

VTO eligibility is per-SKU in portal — not every product is try-on ready on day one.

API & FAQ

REST surface, auth, and common questions

Public widget traffic uses store-scoped keys. Server integrations use merchant API keys with tighter scopes — rotate from the portal.

Auth model

Key typePrefixUsed by
Widget (public)ss_live_Storefront script embed
Merchant APIsk_live_Server-side integrations

Representative endpoints

MethodPathPurpose
POST/sessionsStart shopper session
POST/messagesAssistant chat turn
GET/products/{id}Catalog context for PDP
POST/try-onInitiate VTO capture
POST/webhooks/ordersAttribution (merchant setup)

Full OpenAPI reference ships with merchant onboarding. Do not expose sk_live_ keys in theme Liquid.

Frequently asked

Can I run the widget without Shopify OAuth?

Yes — custom app token + manual catalog sync is supported, but OAuth is the supported merchant path.

Where do product UUIDs come from?

Catalog sync writes wardrobeit.id metafields. Reference them in Liquid for data-product-id.

Is try-on available on every SKU?

No — merchants enable eligible SKUs in the portal. The widget hides try-on when a SKU is not enabled.

How do I test before go-live?

Use a development store, enable the theme embed, and verify assistant + product cards on PDP and collection pages.

Ready to integrate?

Book a technical walkthrough or start a trial — we will validate OAuth, embed, and catalog mapping with your theme.