↳ HEAD points to your-idea on main

Start a project
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.

  1. 01Campaign opens
  2. 02Close and production
  3. 03Delivery
  4. 04Season in store
// wholesale

The 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
// retail

The 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.

A season doesn't wait. So delivery happens one piece at a time.

Signed-off-by: Merge <merge@beecreative.it>
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.

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.

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.

merge@beecreative.it copied to clipboard