Bridal and evening catalog
Gown inventory was photos in a gallery. We rebuilt bridal, evening, and simple dresses as variant-aware products with SAR pricing.
The situation & problem
A dress house needed a catalog that could carry many evening SKUs without flattening size and color into a caption.
The operational constraints
High-variant fashion SKUs, a clean category split, and a storefront that still reads as a lookbook.
Architectural tradeoffs & what was refused
Instagram shopping as the only inventory. A photography portfolio with no cart.
What I built & shipped
Category architecture, variant products, wishlist, and collection merchandising.
Architecture & stack
Commerce catalog with variant SKUs. Category is a filter, not an album name.
Result & measurable impact
Evening vs bridal is now a filterable catalog, not a camera roll.
Next iterations & roadmap
Fitting appointments attached to the same SKU the customer saved.
System surfaces & interface captures
Hover and click any record to open the full-resolution pixel inspector with zoom lens and 1:1 precision.
Have a similar constraint?
Tell me where your current operational system or product is breaking.