The short answer
- Track close dates on one board, not delivery dates — closes create the work
- Standardise the process so every store runs the same way
- Count pieces closing per week, not number of stores
- Offer close dates rather than accepting them, and space them deliberately
- Batch production across stores sharing a garment or ink
One store is a job. Six overlapping stores is a different discipline, and the shops that struggle are usually running each one as a separate project with its own arrangements.
What makes multiple stores manageable is that they are all the same process, run in parallel, with deliberately different dates.
Where it breaks down
| Failure | Cause |
|---|---|
| Two large stores close the same week | Close dates accepted rather than offered |
| Nobody knows which stores are open | No single view |
| Every store works slightly differently | Arrangements negotiated per customer |
| A close date passes unnoticed | Nothing prompts the consolidation |
| Sorting collides across stores | Sorting time not scheduled |
| Stock committed twice | Same garment in two open stores |
The last one is specific to multiple stores and easy to miss. Two stores offering the same style are both quietly relying on the same supplier stock, and neither knows about the other until the second order is placed.
Delivery dates are what customers see. Close dates are what fill your week.
One board
Every open store on one view, with the dates that matter. The instinct is to track delivery dates; the useful field is the close date, because that is when the work lands.
What the board should show
- Store name and customer
- Open date and close date
- Delivery date
- Orders and pieces so far
- Which garments and colours it uses
- Who the organiser is
- Whether promotion has gone out, and when the next reminder is due
The garments column is what prevents the double-commitment problem. Seeing at a glance that three open stores all use the same navy hoodie tells you to check stock depth before all three close.
The reminder column is the one that improves revenue. Organisers need prompting on the day each message is due, and a board that shows which prompt is next turns that from something you remember into something you do.
Standardise the process
Every store should run the same way, with only the catalogue and dates differing. Bespoke arrangements are what make six stores feel like six businesses.
The same for every store
- The one-page agreement, with dates filled in
- Six to eight items, two colourways on one ink set
- The promotion pack of three messages, an image and a QR code
- The same launch checklist
- The same exchange policy
- The same post-close review
Standardising is what makes stores delegable. A process that lives in one person's head cannot be handed over; one that is six repeatable steps can be run by whoever is available, which is the difference between a shop that can take on more stores and one that cannot.
Stagger the closes
Offer close dates rather than asking for them. Most organisers have no strong preference between the 12th and the 16th, and choosing spaces your production at no cost to them.
| Rule | Why |
|---|---|
| No two large stores within three days | Consolidation and sorting collide |
| Count pieces, not stores | Three small closes is fine; two large is not |
| Leave a buffer before peak delivery weeks | Absorbs a late supplier |
| Avoid closing on a Friday | Nothing can be ordered until Monday |
The Friday point is small and saves a weekend. Blanks cannot be ordered until the store closes and the breakdown is known, so a Friday close loses two days before anything can be bought.
Batching production
Where stores share a garment or an ink colour, run them together even if their delivery dates differ.
Two stores using the same navy hoodie and the same white print are one setup and two runs rather than two separate jobs. That is the same sequencing logic as any other week, applied across customers.
Batch across stores by
- Ink colour, to avoid re-mixing
- Garment colour, so darks run together
- Screens, where a design is shared
- Supplier, so blanks arrive in one shipment and reach the free-freight threshold
Do not batch the sorting. Named orders must be sorted per store and kept physically separate, because a mixed sort is the most reliable way to put the wrong garment in the wrong bag.
Scaling further
Past roughly six or eight concurrent stores, two things need to change.
Somebody owns stores. Not as a task among others — one person accountable for the board, the prompts, the closes and the reviews. Below that number it can be shared; above it, shared ownership means nobody is watching the dates.
The board stops being a spreadsheet. Stores that are set up, tracked and closed inside the same system that holds the orders remove the reconciliation step entirely, which is what running them as a product rather than as a series of arrangements is for.
Then keep the per-store record. Which items sold, which sizes ran short, how long sorting took — across several stores those become patterns rather than anecdotes, and they are what make the following season straightforward. The rest of the stores archive assumes you are offering close dates rather than accepting them.
The weekly review
Fifteen minutes, same time each week, looking at the board rather than at individual stores.
What to check
- Which stores close in the next fortnight, and total pieces
- Which prompts are due, and to whom
- Any store performing badly enough to intervene
- Stock on any garment used by more than one open store
- Sorting time booked for the closes coming
The fourth line prevents the double-commitment problem before it happens rather than after. Two stores relying on the same style are fine until one of them closes and takes the stock.
Intervening early on a weak store is the other value of a weekly look. A store that is quiet in week one can usually be rescued with another send from the organiser; the same store discovered at close cannot.



