Fashion Ecommerce Where A Size Is A Real Thing.

Almost every apparel problem is a variant problem. Size and color hold their own stock and their own price here, so a medium selling out stops the medium rather than the shirt, and the back-in-stock note goes to the people who wanted that size.

Start Building How Variants Work

What Apparel Needs From A Catalog

Six things, and the first one causes most of what the others fix.

Variants

Size And Color Hold Stock

Not options bolted onto one product with one number behind it. A medium in navy is its own count, its own price and its own photograph.

Restock

Back In Stock, Per Size

The alert fires on the variant that returned, so somebody waiting on a medium is not emailed because a small came back.

Drops

Content As Pages

Lookbooks and campaign pages are structured content with their own images and SEO fields, edited without a deploy, which is what a drop cadence actually requires.

Bundles

Sets And Outfits

A bundle is a real object rather than a discount code pretending to be one, so what leaves stock when a set sells is the items in it.

Photography

Handled On Upload

Images become WebP with a placeholder as they are uploaded and the build emits the responsive sources. Apparel is image-heavy and this is where its speed usually goes.

Returns

Refunds On The Record

A refunded order is a status on the order rather than a spreadsheet, and returns are the defining operational fact of selling clothes.

Why The Variant Decision Is Everything.

Stock on the product instead of the variant looks fine on launch day. It stops being fine the first time a medium sells out and the store keeps taking orders for it, and by then the fix means re-entering the catalog while trading.

Every downstream apparel feature depends on getting this right: restock alerts, size-level reporting, honest availability on the product page.

Drops Are A Content Problem.

A brand shipping a collection every six weeks does not want a deploy for each one. Lookbooks, campaign pages and category stories are content records with named image slots and their own SEO fields.

Which means the person writing the drop can publish it, and the developer is not the bottleneck between a photoshoot and a live page.

It Reads From The Same Records

Stock

Variants And Bundles

counts on the size that sold

Mail

Back In Stock

triggered by the variant returning

Storefront

The Site Itself

built for the brand, not themed

Questions People Ask

How are sizes and colors handled?

As real variants. Each combination holds its own stock, price and images, which is what makes availability honest on the product page and what makes size-level reporting possible at all.

Can customers be told when their size is back?

Yes, and on the variant rather than the product. Stock restored is a real event on the exact size that returned, so the mail goes to the people who wanted it and nobody else.

How do we publish a lookbook or a drop?

As content. Pages carry named image slots, their own SEO fields and draft and published states, so a collection page is written and published without a deploy.

Do you handle bundles and sets?

Bundles are real objects, so selling a set decrements the items inside it. That matters more in apparel than most categories, because a set that does not decrement its parts oversells all of them at once.

What about returns?

Refunds are a status on the order with the money handled through the same rail that took it. The order history stays intact, which is what you need when a customer returns one item from an order of four.

Put One Style In And Look.

Start Building All Industries