Resources
The questions bridal retail actually turns on, answered
This is the reference section of the RingUps site. RingUps is a retail operating system for bridal boutiques, and this page answers twelve questions about how a bridal store really works, from what a dye lot is to how a deposit becomes revenue, each in a few sentences, each linking to the page that covers it in full.
12 questions answered here, 8 bridal terms defined, and every figure on this site traced to one production database queried on 4 August 2026.
01
The gown and its deadline
2 questions
- What is a dye lot, and why does it matter in a bridal store?
- A dye lot is one run of fabric dyed at a single time. Two runs of the same fabric in the same named colour come out fractionally different, which is invisible on a hanger and obvious when five bridesmaids stand in a row. RingUps blocks a purchase order that would split a wedding party across two dye lots of the same fabric, and a staff member has to tick an override to place it anyway. The dye-lot guard, and what the override costs you →
- How does a bridal system work out when a gown has to arrive?
- It counts backward from the wedding rather than forward from the order. RingUps takes the bride's wedding date, subtracts the store's alterations buffer, which is 28 days by default at Cande Bridal Boutique, and produces a must-arrive-by date that the designer's lead time is measured against. If the lead time already overshoots that date, the order is flagged at risk on the day it is sold, while there is still a conversation to have. How the deadline engine classifies an order →
02
The money
1 question
A deposit taken in March is not revenue in March.
The rule the payments ledger is built around
- How does deferred revenue work for a bridal deposit?
- A deposit is money the store owes as a gown, not money it has earned. RingUps posts every payment to an append-only double-entry ledger and recognizes the revenue at delivery rather than on the day the card clears, so a deposit taken in March is not March revenue. The deposit ledger, leg by leg →
03
The bride, the catalogue and the workroom
4 questions
- Why can a general CRM not model a bride?
- A CRM models a contact and a deal that closes. A bride is one transaction that stays open for roughly a year: an appointment, a gown ordered against a wedding date, deposits taken in stages, a party of bridesmaids attached to her, fittings, and a pickup. RingUps holds that as one record rather than as a contact with notes stapled to it. What sits on a bride record →
- What is a division, and why does one designer have several?
- A division is a separate label a designer sells under, with its own styles, its own price band and often its own ordering rules. One supplier can therefore appear in a store's catalogue as several divisions. The migration of Cande Bridal Boutique carried 23 suppliers across 49 divisions, which is why a boutique's ordering rules rarely sit neatly at the supplier level. Designers, divisions and lead times →
- What is the difference between a sample, a floor unit and a special order?
- A sample is the gown a bride tries on in the shop, owned by the store and worn hundreds of times. A floor unit is one physical piece of stock with its own size, colour and condition, and the Cande Bridal Boutique migration imported 500 of them. A special order is a new gown bought from the designer for one named bride against her wedding date, and it is the transaction that general retail software gets wrong. The catalogue and the floor as one record →
- Where do alterations live in a bridal system?
- In RingUps they live in one workroom screen holding the jobs, the fittings and the per-item work. In Bridal Web Solutions the same work is scattered across appointments, per-supplier charge records and four separate reports, with no workroom screen at all. Inside the alterations workroom →
04
Leaving a system, and who can read yours
3 questions
Ask an owner to reconcile their current system against itself.
The question the migration work kept answering
- How does a bridal store move off BridalLive or Bridal Web Solutions?
- Three routes, in this order: the vendor's own exports first, an authenticated read of the records held on the vendor's servers second, and configuration transcribed by hand third. Configuration is the part that no export covers, so contract bodies, message template bodies, scheduled message rules, supplier lead times, size charts and per-bride notes are captured from a live session before the subscription lapses. Every row RingUps imports is idempotent on its source reference and reversible by batch id. The migration path, week by week →
- What does it mean for one store's records to be isolated from another's?
- There are two ways to do it. Application-level filtering means the code has to remember to add a store filter to every query, and one forgotten filter is a breach. Database-level isolation means the database itself refuses the read: RingUps uses row-level security across 53 tables, every policy written against one shared rule, and the isolation is proven by a script that signs in as another store and fails to read a single row. Isolation, backups, and what RingUps does not hold →
- What did RingUps find when it reconciled a store's old data?
- Bridal Web Solutions disagreed with itself. On order 872 its sales-tax export, its payments export and its own line data gave three different answers, and its Category Defaults screen said 655 units in stock while its own inventory export said 506. RingUps found 93 wrong-signed reversal lines across 59 orders worth $141,807.75, roughly 78% of an apparent $384,659.89 receivable that was an artefact, and skipped 228 orders rather than invent a bride to attach them to. The whole reconciliation, with the numbers →
We found it, we refused to guess at it, and we told the owner not to collect on it.
The $141,807.75 of wrong-signed lines, 2026
Glossary
Eight bridal retail terms, defined for someone who does not work in bridal
Every one of these is a word a boutique uses several times a day and a word most retail software has no field for. If you are evaluating systems, or writing about the category, these are the eight that change what a system has to be able to do.
- Dye lot
- One run of fabric dyed at a single time. Two runs of the same colour name differ slightly, so a bridal store tries to keep a whole wedding party inside one lot.
- Division
- A separate label a designer sells under, with its own styles, price band and ordering rules. Twenty-three suppliers became 49 divisions in the Cande Bridal Boutique catalogue.
- Special order
- A gown bought from a designer for one named bride after she has chosen it, rather than sold off the rack. It is ordered in her size and colour, paid in stages, and arrives weeks or months later.
- Must-arrive-by date
- The date a special-order gown has to be in the shop. It is the wedding date minus the store's alterations buffer, so it is a deadline the store sets rather than one the designer quotes.
- Deferred revenue
- Money taken from a bride before the gown is delivered. It is a liability on the books until delivery, at which point it is recognized as revenue.
- Sample
- The gown kept in the shop for brides to try on. A sample belongs to the store, is worn hundreds of times, and is eventually sold off at a discount.
- Floor unit
- One physical piece of stock, tracked individually with its own size, colour and condition, rather than as a quantity sitting against a style.
- Fitting
- An appointment in the workroom where a gown is pinned, measured or checked against the bride. It is a different thing from the sales appointment at which she chose the gown.
One RingUps limit that follows from the last term: a fitting created in the alterations workroom and an Alterations-department appointment on the calendar are two records that do not synchronise, and a fitting appears on neither the calendar nor the iCal feed. Read the workroom page.
This page in full
Every page behind these answers is free to read, right now
Twelve answers, eight terms, and a link to the full page behind each one - no form, no call, no waiting on a guide that has not been written yet. Read at your own pace, then bring the checklist below to a demo.
Who builds RingUps, and why →The evaluation checklist
Five questions to ask every vendor, RingUps included
Take these to every demo you sit through. The answers are more revealing than the feature lists.
- 01What will my bill be in twelve months with everything I actually use switched on?
- 02If I leave, exactly which records can I take, including open orders and alterations?
- 03Does the system compute my deadlines from wedding dates, or do I still track that myself?
- 04Where do alterations live: a real workroom queue, or a note field on an order?
- 05Can you show me your own numbers reconciling against themselves, on screen, right now?
05
About these pages
2 questions
- Where do the figures on the RingUps site come from?
- From the production database of the first store running RingUps, Cande Bridal Boutique in Kelowna, British Columbia, queried on 4 August 2026. Migration figures and current totals are different numbers and are labelled as such, because the store has kept trading since. One of the two RingUps founders owns that store, and that is disclosed on every page that uses its figures. The store the figures come from →
- Do I have to book a call to get a straight answer about RingUps?
- No. Every price is published on the pricing page, and a fifteen-minute demo runs on your own data if you want one - nothing here is held back until you take it. The full FAQ →
Where owners go next
Three pages that answer the rest of it
The long version of this page
The FAQ takes the same approach and goes further, answering the questions a bridal store actually asks before booking a demo.
Every price, published
Go here if the question you actually came with was what this costs. Every module is in every plan, and staff logins are unlimited on all of them.
The whole platform in one place
If you would rather see the modules than read the concepts, the platform overview walks appointments through to reporting in order.
Bring the checklist to a call and we will answer all five
Fifteen minutes, on your own data, walking through the workflow end to end.