How to track alterations without promising the same week twice
6 min read
Fittings are booked months ahead but alterations are agreed in a corridor conversation. Writing down four things at that moment is what keeps the seamstress's week from being sold twice.
The job is agreed in the worst possible place
A sale gets an order form. A fitting gets a calendar slot. Alterations get agreed standing next to a mirror, with a bride in a gown and pins in someone's hand, and the whole record is a sentence: we'll take the hem up and add a bustle, ready in two weeks.
Everything that goes wrong later is already contained in that sentence. Nobody wrote down which gown, who agreed the price, or what two weeks means as a date. The seamstress finds out on the day she opens her list, and by then three other brides have been told the same fortnight.
You do not need a form with twenty fields. You need four things captured before the bride has her coat on: which dress, what work, what it costs, and the date you promised.
Keep the status list short enough to be true
Four working states cover nearly every alteration: requested, on the table, ready for pickup, delivered. Add cancelled for the jobs that evaporate and stop there.
The temptation is to add more — awaiting fabric, first fitting done, second fitting booked, pressed. Every extra state is a state somebody will forget to move a job out of, and a job parked in a stage nobody updates looks handled while it rots. Short lists get filled in; long lists get abandoned, and an abandoned list is more dangerous than no list because people trust it.
Make the transitions one-directional in practice. A job that is ready can be delivered or cancelled; it does not quietly slide back to requested because someone changed their mind about the hem. If the bride asks for more work, that is a new job on the same dress, with its own price and its own promised date. That is not bureaucracy — it is the only way the second piece of work gets paid for.
One promised date, and read the overdue list first
Every job carries exactly one promised date: the date you told the bride. Not the date the seamstress hopes for, not the wedding date. Those are useful but they are not the promise, and the promise is what you will be judged on.
Then sort the open work by that date and read the overdue ones before anything else each morning. This is the entire discipline. A shop that looks at its late jobs daily is calling brides before they call in; a shop that looks weekly is apologising.
Delivered and cancelled jobs should drop off that list entirely. A working list that shows finished work is a list people stop reading, and the day they stop reading it is the day a dress misses a wedding.
Charge on delivery, not on agreement
The cleanest money rule for alterations is that the fee is earned when the gown is handed back, not when the work is agreed and not when it comes off the table.
It matches what the bride believes — she is paying for a finished dress — and it keeps your books honest about work in progress. Charging on agreement books income for a hem that has not been sewn; charging when the work is finished books income for a dress still hanging in your back room. Delivery is the one moment both sides agree the job is done.
Whatever rule you pick, apply it once per job. The most common bookkeeping mess in a bridal shop is not a missing charge, it is the same alteration charged twice because two people both tried to be helpful on the same afternoon. Tie the charge to the job moving into delivered, and the second attempt has nothing left to do.
Bridal Stack puts this into practice: every gown has one status, every order has one total, and every count records the difference instead of hiding it.
Start free →