Emaan Trends

The situation

Bridal and unstitched clothing moves in seasonal collections, and the client was launching several a month. Each launch meant a member of staff entering products by hand, which took days and meant a collection went live long after the moment that justified it.

What we found

The bottleneck was not the volume of products. It was the mismatch between how the supplier sends data — one spreadsheet, one row per fabric, several variants per row — and how the store expected it.

Staff were doing that translation manually every time, which is exactly the kind of work that should not be a person's job.

What we did

We modelled unstitched fabric properly as a variable product, so one listing carries its lengths and colourways instead of becoming several near-duplicate listings that split the search traffic between them.

Then we built an importer that takes the supplier spreadsheet in the shape it already arrives in. Staff map columns once; after that a new collection is a file upload and a review step.

Collections can be prepared ahead and scheduled, so a launch happens at a chosen time rather than whenever someone finishes the data entry.

How it went

New collections publish the same day they arrive rather than several days later. The work that used to take a person most of a week is now a review pass on an import.

What we would do differently

We built the importer against the supplier format that was current at the time. It changed within the year and needed remapping. A more forgiving column-matching step up front would have absorbed that without us being involved.