A web-based portal that gives store teams a clear, one-page guide to how each flagged garment is meant to fit. The goal is to reduce avoidable returns and exchanges.
A meaningful share of returns happen not because a garment is wrong, but because the intended fit is misunderstood — a low waist reads as “too loose,” a sharp shoulder feels “wrong,” a client sizes up or down against the design. When the floor can explain design intent confidently, fewer of those returns happen, and more convert to exchanges rather than refunds.
Sales associates
Browse and search guides on the floor, pull up a style during a fitting, log quick feedback after a sale or return, and send a client-safe version to a customer.
Store managers
See how the guides are performing — return rates, how often guides are viewed, and the feedback associates are logging.
Design / technical design
Author the guides, set the fit language, and decide which styles get flagged as likely to be misread.
Administrators
Manage the full library, run the approval process, and publish guides.
The Hub
A clean, visual library of every published guide. Filter by season, delivery, and category, or search by style or SKU, and switch between a visual grid and a sortable list. Styles likely to be misread carry a risk badge so the floor spots them immediately.
The Detail page
For each flagged style: photos from five angles, a short fit headline and the key fit points, “may feel counterintuitive” callouts that pre-empt the common misunderstanding, brand-voice copy, and the model’s size and measurements for reference.
Client-safe links
Associates generate a clean link to send a customer. The client view shows only customer-appropriate content — none of the internal notes.
Seconds, not minutes
After a sale or return, associates log the reason, the outcome (return / exchange / kept), how useful the guide was, and an optional note. This separates real fit problems from misunderstanding problems.
Pilot performance
Return rate by style versus baseline, how the exchange-vs-refund mix is shifting, how much the guides are used, and a searchable log of all associate feedback.
One source of truth
The team creates and edits guides in a familiar rich-text editor, uploads the five photos, and routes each through a simple approve → publish flow. Previous versions are archived so nothing is lost.
- It’s a standard web application — nothing to install. Staff open a link in a browser. Designed mobile-first for store iPads and phones.
- Login uses the organization’s existing single sign-on, with role-based access so each person sees only what’s relevant. A simpler role-selector login is available for pilots and demos.
- The look and feel follow a defined brand guideline so the portal feels native to the brand: restrained, editorial, quiet luxury.
- It runs on a standard database today and can move to the company’s cloud database later with no rebuild — a configuration change, not a new project.
Lower returns
A lower return rate on flagged styles compared with the baseline.
Revenue retained
More returns converting to exchanges rather than refunds.
Floor confidence
Associates report higher confidence explaining fit.
Defensible data
Clear separation between genuine fit/spec issues and simple misunderstandings, so corrections are targeted.
One store
~25–40 high-risk styles in a single delivery window.
~8 weeks
Enough to capture selling and return behavior.
Weekly snapshot
Then an end-of-pilot readout with learnings and a recommendation on whether and how to scale.
- Which styles to flag — for each delivery — the merchandising / design call.
- Single sign-on details — which identity system to connect to. The one item with timing uncertainty; worth scoping early with IT.
- Brand assets — final fonts and any garment photography to use in the guides.
- Content ownership — the points of contact in design / merchandising who author guides and act on the feedback loop.
- One current, authoritative version of every guide, with older versions archived.
- A feedback loop designed for periodic review of recurring confusion themes, so the guides — and the template — improve over time.
- Fast, lightweight approvals so guides don’t sit in limbo and miss the selling window.