Packing is the strictest test a wardrobe gets, and it turned out to be a useful test for a catalogue too. At home, a piece can survive on one good pairing and a forgiving mirror. In a suitcase, every item has to work with several others, come out of the bag presentable, and suit more than one kind of day. Building Soclasica around classic pieces meant asking whether the catalogue itself passed that test — or whether it was quietly full of single-purpose items that only looked versatile on a product page.
What worked
Counting pairings instead of describing occasions. Early product copy described where a piece might be worn: dinner, work, a weekend. That told a shopper almost nothing testable. What worked better was thinking in pairings: a knit that works over a dress one evening and with trousers the next morning, shoes that suit both, a tote that carries the day and still looks right at dinner. Versatility stopped being an adjective and became a count — how many other pieces in a small set does this one actually combine with?
Simple lines and colours that sit together. The pieces that passed the packing test shared unglamorous qualities: simple lines, colours that sit comfortably together, and fabrics that do not demand special handling the moment they are unpacked. None of that photographs as dramatically as a trend piece, but it is what makes a small travel set repeat without looking repeated — and what makes the same pieces wear well at home, because they were chosen for repeat use rather than one occasion.
Treating packing as editing, not shopping. The clearest framing that emerged was that a wardrobe that travels well is usually a wardrobe that was built calmly in the first place. Travel does not require a separate wardrobe, only a selection from the existing one. For the catalogue, that meant favouring depth in the classic end of the rail — dresses, knits, totes, boots and beauty staples selected for repeat wear — over breadth in one-season items.
Soclasica is where that selection lives, with tracked delivery in 7–15 business days; US shipping starts at $4.99 and the actual rate is calculated in the cart once items are added.
What broke
Trend pieces failed the count. Items bought for one look, one event, or one photograph combined with almost nothing else in the set. On a product page they looked like range; in a suitcase they were dead weight, and at home they were the pieces left unworn after their moment passed. The catalogue lesson was uncomfortable: breadth measured in SKUs is not the same as breadth measured in outfits.
Fabric handling was invisible in the data. A piece could pair beautifully on paper and still fail in practice because it creased, needed special care, or could not be worn twice between washes. Early product data had no field for any of that, so the versatility count overstated real usefulness. Handling has to be part of the product record, not a surprise discovered in a hotel room.
Combinations multiplied faster than they could be shown. A small set of versatile pieces produces more combinations than a product page can sensibly display. Showing a handful of honest pairings worked; trying to show every combination turned pages into noise and shoppers stopped reading. Curation beat completeness, the same lesson the suitcase teaches.
Lessons worth keeping
A versatility test is stricter and more honest than a style description: count the pairings, check the handling, and see whether a piece earns its place twice — once at home and once in the bag. Catalogues, like wardrobes, get better by editing toward repeat use, not by adding single-purpose range.
How do you test whether something in your catalogue — or your codebase — is genuinely versatile, rather than just described that way?
