Fashion is the hardest kind of shop to design well. We built two live stores on the same theme code to show how Claude handles it: a multi-department store built for range, and a single-label Cotswolds boutique built for the brand.
The product changes every season, the photography carries the brand, and the same catalogue has to work for someone who knows exactly what they want and someone who is just browsing. Most templates pick one of those and fail the other. These two stores run on the same theme code; everything that differs between them is brand, copy and preset. The design system does the heavy lifting, and the shop that sits on top can be as big or as small as the business.
Both are on the examples page, with a live catalogue, bag and checkout you can walk through.
MarbleArc is the department-store preset. It is designed for the businesses where the catalogue is the brand: department stores, fast fashion, multi-brand retailers, anyone with Women, Men, Kids and Accessories running side by side and hundreds or thousands of lines underneath.
The branding is deliberately impersonal. There is no founder story on the home page and no “our values” section; the wordmark is clean, the palette is neutral, and the photography does the talking. That is a choice, not an omission. When you sell twelve brands across four departments, the store’s own personality has to get out of the way so each product can have its own.
What it does instead is impact and throughput:
For a fast-fashion operation the useful property is that the design never needs touching when the range changes. New drop, new department, new sale: it is all catalogue work, and the theme re-lays itself.
Honeystone is the same theme switched to the boutique preset. It is a country-clothing label from Cheltenham, with one department, around twenty-five pieces, and a shop you can collect from.
Here the branding is everything. The home page opens on one landscape image with a card over it, then a single edit of pieces the brand has chosen, then the story with two photographs, then the lookbook and the journal. The about page has the shop’s address, the collection note and the posting note, because for a shop this size those are the trust signals.
The differences from MarbleArc, in practice:
The theme code is shared. Fix a bug in the product page or improve the checkout and both stores get it. For an agency running several fashion clients, or a group with a flagship and a diffusion line, that is the model: one theme, many installs, each with its own catalogue, keys and brand.
Each store is a folder of short stubs that point at the shared theme, plus one brand file that sets:
department or boutique),Product photography comes in through the image queue. Brief the shoot once, the queue generates the frames, and the theme places them into named slots: hero, category tiles, lookbook background, journal covers. Swap the image set and you have a different brand on the same bones.
Design gets the customer in; the back of house keeps the manager sane. These are the parts of the Claude ecommerce stack that matter most when the product is clothing.
If the first thing a customer should see is range, start from MarbleArc. If it is the label, start from Honeystone. Either way the theme underneath is the same, so the decision is not permanent: a boutique that grows into departments flips the preset rather than starting again.
Both stores are live on the examples page. Open one, add something to the bag, go through to checkout. Then tell Claude what you would change.
Want the bigger picture first? The ecommerce website builder page shows what a full store build looks like, and the setup guide walks from an empty site to a working store.