6a2f81d·feat: fashion B2B/fashion-b2b10 years, ten brands
In fashion, software
is measured in seasons.
Wholesale and retail. Two moments, one set of data.
The selling campaign opens on a date and closes on a date. Production starts from whatever was collected, the store opens when it opens. Software that is two weeks late isn't late: it missed the season. That is the constraint that makes this sector different from every other one we work in, and the reason nothing here gets improvised.
c17b3e9·feat: the season/seasontwice a year
Two moments, two different pieces of software.
In the same months, different people work on different problems. Whoever collects collection orders in a showroom does not have the needs of whoever, in a store, has to know whether that size is there. They are two pieces of software, and the only thing they must share is the data.
- 01Campaign opens
- 02Close and production
- 03Delivery
- 04Season in store
// wholesaleThe selling campaign
sales reps, KAMs, showroom, agents
Collection orders get collected against a sample range, with a client sitting there waiting. What is needed is a screen that fills in fast and writes into the ERP without a spreadsheet in between: sizes and colours in a grid, availability, the client's price list and terms already applied.
Web apps for whoever sells ↗// retailThe season in store
store managers, sales staff, warehouse
Here there is one question and it arrives with the customer standing there: is this size available? What is needed is a catalogue that tells the truth, synced with the ERP and with the other stores, and a flow that gets the request to the warehouse without a phone call.
How we sync the systems ↗ You don't start from both. You begin with the moment that costs you most right now - usually the campaign, because it has a date - and the second piece gets added once the first has survived a season.
7f3c9a2·git commit -S -mHEAD → main
A season doesn't wait. So delivery happens one piece at a time.
8e40d5c·feat: data model/modelfour objects
The things that exist only in fashion.
It isn't that the software is harder. It is that the data model has objects that exist nowhere else - and if you don't know them you discover them with the campaign already open, which is the worst possible moment.
- // grid
Sizes and colours in a grid
An item is not a row, it is a matrix. Whoever sells fills in a grid and sees the totals per row, per column and overall as they type. Outside fashion, this screen is of no use to anyone.
- // capsule
Capsules, drops, collections inside collections
The first time you hear the word capsule you don't know what it changes in the data model. The thirtieth time you know before anyone asks.
- // replenishment
Collection and replenishment are two things
One is collected months ahead against a sample range, the other arrives mid-season and has to answer the same day. Software that treats them alike makes at least one of them work badly.
- // terms
Price lists and per-client terms
Discounts, tiers, currencies, payment terms, order minimums. They are already configured in the ERP: that is the right place to apply them from, not a second table somebody keeps aligned by hand.
d5a92f7·chore: proof/case-studiesin production
Four projects, across the whole season.
Two on wholesale, one on retail, one on the data that sits under both. Different companies and different projects, but lined up they tell the season from one end to the other.
06Sportswear · Wholesale platform + ERP
Wholesale platform with pre-order and stock orders
Pre-order and stock in one interface, with catalogues and media generated on each client’s own collection.
ResultIn production shortly after the new ERP, with every client seeing only what they can buy.
Read the case study →03Fashion luxury · B2B platform + ERP
Wholesale ecosystem for collections and media
Orders, replenishments, media and catalogues in a single platform, integrated with the company ERP.
ResultEnd-to-end digitised wholesale process, catalogues generated automatically, evolving since 2019.
Read the case study →02Fashion retail · Digital catalogue + ERP
Retail catalogue synced in real time
Instant visibility on stock and catalogue for every store, with an automatic store-to-warehouse flow.
ResultZero manual catalogue updates, real support for assisted selling in store.
Read the case study →04Fashion & luxury events · Data warehouse + AI
Company DWH with middleware and MCP
ERP, HR and other application data centralised and queryable through AI - with no technical skills.
ResultA single source of data, permission-based access, interoperability across every company application.
Read the case study →2c6e8b1·chore: questions/faqfour answers
The questions we always get.
Can we start with the campaign already open?
You can, and sometimes it is the only moment you realise you need to. But what gets delivered with a campaign open is a small, safe piece, not a platform: the wrong moment to change how orders are collected is while you are collecting them. The honest thing is to tell you which weeks are at risk, and we say it up front.
Do we have to replace the ERP?
No, and it is almost always the wrong answer. The ERP runs production, accounting and the warehouse, and it does it well: what is missing is an interface for whoever sells and a channel for whoever buys. They get added alongside and they write where they should.
Do we have to choose between wholesale and retail?
Over time no, right now yes. The two moments have different users and different rhythms, so they go into production one at a time - but they sit on the same data, which is why the second costs less than the first.
Do you work with brands like ours?
Ten years in fashion B2B, ten brands and more than thirty selling campaigns, from luxury to retail. The names we can give are on the homepage; the projects, with what they solved, are in the case studies above.
Where is your season right now? Let's start from there.