Women’s fashion
LaceMade
LaceMade uses strong styling and collection stories to create desire, but conversion depends on clear sizing, fit, occasion and inclusive range guidance.
Visit the live project
Core implementation review
Three storefront journeys from model choice to purchase
LaceMade can hold attention with princess-core styling and corset silhouettes. A sale still waits on a bust, waist and hem the shopper trusts. Occasion collections should land her in the right garment range; the product page should fold photography, size variants and fit notes into one submitable choice, instead of letting the campaign film and the buy controls disagree.
Project context
Define how customers choose before defining the storefront
Customers enter through New Dream, corsets, dresses, cottagecore, prom or Curve & Plus, then choose by occasion, silhouette, colour, size and price. Model data, size guides, details, reviews, styling and returns confirm fit.
Shopify fashion frontend, range and occasion navigation, product cards, language and currency, and mobile UX.
Narrow the wardrobe by occasion before a single dress opens
When someone arrives with prom, a date or a cottagecore look in mind, New Dream, corsets, dresses, Cottagecore, Prom or Curve & Plus should catch her first—not a flat wall of every garment.
- 01Enter through an occasion or collection
- 02Narrow by silhouette, colour and size
- 03Open the matching garment page
- 04Sell standard and curve as separate products
Implementation
- New Dream, corsets, Dresses, Cottagecore, Prom and Curve & Plus own occasion discovery; collections do not own sellable sizes.
- Colour and size live on product variants. Fabric, model notes and care stay as content, outside the variant matrix.
- Curve and standard fits share a visual language but remain distinct SKUs, so a fit difference is never stored as a colour.
- Predictive Search returns garment and collection suggestions while she types, sending the query back into the right range.
Deployment and acceptance
- New drops update collection pages and filter dimensions first; garment templates reuse the same variant structure.
- Editors work in collections, fit notes and policy modules rather than packing occasion copy into size options.
- Collection photography can be shared across markets; bust units, delivery and returns update by destination.
- By the time a garment page opens, occasion is already resolved; the remaining work is fit.
- A new release can enter discovery by following the collection-plus-variant pattern, without a new taxonomy for every drop.
View script and Shopify API evidence
Predictive Search APIProve bust, waist and hem with the body, not the mood crop
A corset page has to show how the garment sits on a body. Size controls, the size guide and returns copy must survive the campaign photography—especially on a phone, where a full-bleed hero can hide them.
- 01Read multi-angle body and hem
- 02Open the size guide and model notes
- 03See which colours and sizes can still sell
- 04Keep returns visible beside the buy box
Implementation
- The gallery leads with body photographs that show bust-waist structure and hem length; mood crops support the story, they do not replace fit evidence.
- Colour chips, size buttons and add-to-cart keep high-contrast states, and unavailable sizes are visible before submit.
- pagefly-product-media.js and pagefly-product.js extend garment media and the purchase layout, while theme.js, custom.js and vendor.js remain the theme interaction base.
- The size-guide overlay can be dismissed and must not cover returns copy while open.
Deployment and acceptance
- Desktop pairs a long editorial gallery with the buy box. Mobile crops campaign frames and keeps size controls reachable beyond the first-screen details.
- Corset templates split gallery, sizing and purchase so fabric and care can change without touching variants.
- Fit guidance stays in an app extension and does not rewrite the theme’s size variants.
- The same page can sell the look and still let her check the cut.
- Seasonal photography can be swapped without rebuilding the size block or the buy box.
View script and Shopify API evidence
pagefly-product-media.jspagefly-product.jstheme.jscustom.jsvendor.jsThe size on screen has to be the variant that enters the cart
Once Love Flower Notes or Crash Landing On You is the dress, colour, size and add-to-cart must point at one variant. Fit help and related styling may assist; they must not replace the garment.
- 01Choose colour and an available size
- 02Check fit in the sizing overlay
- 03Submit the product form to the cart
- 04See related pieces in the same garment context
Implementation
- The product form submits the selected size and colour variant; media and price follow that choice instead of calculating a second answer.
- SizingPlugin.prod.js supplies fit guidance as an overlay, outside the theme variant.
- Add, quantity change and cart update travel through Cart Ajax, not a full-page reload or a section rerender.
- Product recommendations offer related styling from the current garment, with delivery and returns kept beside the purchase action.
Deployment and acceptance
- blocker.js handles regional access at the storefront edge, not inside the garment form, so access rules never become size options.
- No dedicated cart-drawer file is exposed; add-to-cart feedback stays inside the theme bundle and Pagefly product scripts.
- Recommendations can extend the basket; price, variants and the buy button do not depend on that request.
- The size she is looking at is the variant that enters the cart.
- Fit help, regional access and related styling can sit beside the dress without rewriting what can be sold.
View script and Shopify API evidence
Product form behaviorVariant behaviorSizingPlugin.prod.jsCart Ajax: addCart Ajax: changeCart Ajax: updateProduct Recommendations APIblocker.jsOperational handoff
The operating team can continue after launch
- The live catalog treats corset silhouettes, occasion dresses and vintage-inspired gowns as the sellable garments, with New Dream, corsets, Dresses, Cottagecore, Prom and Curve & Plus as occasion routes.
- Size and colour belong in variants. Fabric, model notes and care remain content, outside the variant matrix.
- Curve and standard fits share a design language as separate SKUs, and new garments reuse the split between gallery, sizing and purchase.
- Checkout preloads use locale=en-US, so the default transaction context is English and USD.
- Some extension requests include a lacemadeuk shop parameter, which means access and size notation may diverge by market; blocker.js gates that access at the storefront edge.
- Size charts, bust units, delivery and returns stay destination-specific, while collection visuals can be shared and the core purchase path does not need to be rebuilt for a drop.
Research notesPublic sources and verification boundary
Public research sources
Content verification
Industry, product and observable feature notes are verified against the brand site. Apps, admin configuration and commercial data that cannot be confirmed from the storefront are not inferred. WESWOO scope is stated only from project records and client authorization.
Public information last reviewed: 2026-08-12