Prom Module

No Two Girls From the Same School in the Same Dress

It is the promise every prom shop makes at the till. BridalOp is what makes it true — registered against the school, checked before the sale, and provable six months later.

The Promise You Already Make

Most shops keep it in somebody’s head, or a binder by the till. That works until the girl who bought in November comes back in March, or the one consultant who remembered is off that day. Then two girls arrive at the same prom in the same dress — and neither of them forgets it.

BridalOp keeps the book. Your team is told before the sale, not after.

Prom 2027

Prom Registry

Every dress spoken for this season, by school. Last year’s book stays browsable behind the season selector.

128

Dresses registered

across 14 schools

On hold, not yet paid

Holds ending this week

1 override this season

Sold over an existing registration at Springfield High — reason given: “different prom, transferred in January.” Recorded with the name of whoever approved it.

Season: Prom 2027
Matched on: Style and colour — never size
Exclusive to: The school, across every location

Recent activity

Emerald mermaid, style 4471 — registered to Springfield High just now

Hold on ruby A-line lapses in 2 days — Maya R. this morning

Navy two-piece released — returned, back on the rail at Central High yesterday

The Prom Registry, once the module is switched on.

How It Works

Three things to set up, and then it keeps itself.

Switch It On

Settings → Modules. Nothing appears anywhere in BridalOp until you do — bridal-only shops never see it.

Tick the Dresses

Choose which product types are prom stock. The counter beside each one tells you how many products it covers.

Add Your Schools

Once each, under Operations. District and city are there to tell two Central Highs apart.

Sell

Every prom dress sold to a girl with a school on her record registers itself. There is no list to keep.

Caught Long Before the Till

A warning at the register is the last line of defence, and the worst place to find out. The point is that your team already knows.

Where	What your team sees
On the appointment	Her school, and how many dresses are unavailable to her — so the rail is pulled before she walks in.
On the product page	How many schools this gown is spoken for at, expanding to the list with colour and date.
In the POS grid	With her attached, dresses she cannot have are badged. No clicking through to find out.
At the till	Warn, block, or record silently — your setting, and every override logged.

You choose who may override, and whether they have to give a reason.

What It Tracks, and What It Won’t

It keeps itself

Dresses register themselves the moment they sell
A full refund gives the dress back automatically
Holds expire on their own, so a forgotten one cannot block a school
Last season stops blocking this one when you roll the season over
Released dresses keep their record — who had it, and why it went back

It stays out of the way

Sizes never clash — matching is on style and colour
A partial refund does not release the dress; that is usually an alteration
Rebooking cannot move a girl to another school behind your back
Staff see a first name and last initial — enough to have the conversation
The public checker never returns anybody’s name

A Page She Can Check Herself

Put the link on your own website and a girl picks her school, searches a dress, and gets an answer. When it is taken, the page can suggest what is still free at her school — which turns a disappointment into a second appointment.

It never says who has a dress. Only whether it is free at that school.

The page stays hidden until the module is on, the checker is enabled, and your catalogue actually covers something — a checker that answers “free!” about stock it does not track would be worse than not being there.

When Somebody Overrides It

Software cannot decide whether a clash is really a clash. Two sisters, a girl who transferred in January, a school whose prom is a different night — most overrides are perfectly good, and a system that refused them all would just be switched off.

So BridalOp records them instead. Every override carries a reason and a name, and they sit together in one place. One override is a judgement call. A run of thin reasons is something you want to know about, and this is where you would see it.

What You Need

Prom stock in your catalogue

The module is keyed to a product’s type, and you tick which types count. A counter tells you how many products each one matches, so you cannot switch it on against nothing.

Your schools, entered once each

Name, plus district, city or state when two schools share a name. Entering one twice would split its own exclusivity, so the list is worth keeping tidy.

A BridalOp account

Included on every plan at no extra cost. Bridal-only boutiques leave the module off and never see any of it.