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
A dress house needed a catalog that could carry many evening SKUs without flattening size and color into a caption.
The constraint
High-variant fashion SKUs, a clean category split, and a storefront that still reads as a lookbook.
What we refused
Instagram shopping as the only inventory. A photography portfolio with no cart.
What we shipped
Category architecture, variant products, wishlist, and collection merchandising.
Stack, on purpose
Commerce catalog with variant SKUs. Category is a filter, not an album name.
What changed
Evening vs bridal is now a filterable catalog, not a camera roll.
What we would do next
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 us where your current operational system is breaking.