Every part of a bridal store, on one record

The three things that go wrong in a bridal store are all data problems

A gown arrives in a different dye lot from the sample the bride chose. A deposit is taken at the counter and nobody can say, six months later, whether it was ever applied. A bride is never called back after the appointment where she said maybe. None of these are staff failures. They happen because the appointment lives in one system, the order in a second, the deposit in a third, and the alterations on a whiteboard that gets wiped on Saturday.

The evidence for this is not rhetorical. When Cande Bridal Boutique in Kelowna, British Columbia moved off Bridal Web Solutions, three of that system's own exports gave three different answers for one order, number 872. Its Category Defaults screen reported 655 units in stock while its own inventory export reported 506. Reversals had been recorded with both a negative quantity and a negative price, so they read as positive charges: 93 lines across 59 orders, $141,807.75 wrong-signed, which made roughly 78% of an apparent $384,659.89 receivable an artefact of the data rather than money anyone owed.

RingUps is built the other way round. One record per bride, one ledger for money, one place where a deadline is calculated. The sections below map that record domain by domain, and each one says where it stops.

The proof is a migration nobody had to take on trust

One store has moved onto RingUps in full. Every figure below was verified against the production database on 4 August 2026, and the store has been trading since, so the live totals are now higher. These are migration figures, not current ones.

What the reconciliation actually found

Their exports disagreed with each other

On order 872, Bridal Web Solutions gave three different answers: one in its sales-tax export, one in its payments export, one in its own line data.

Their screens disagreed with their exports

Category Defaults reported 655 units in stock. The inventory export from the same system reported 506.

Reversals were recorded so they read as charges

93 lines across 59 orders carried both a negative quantity and a negative price, $141,807.75 wrong-signed, making roughly 78% of an apparent $384,659.89 receivable an artefact.

Tax had to be rebuilt, then corrected

The sales export carried no tax at all, so it was reconstructed on 1,391 orders and then corrected against a second report on 36 exception invoices, catching a $3,253.05 overstatement.

Ask an owner to reconcile their current system against itself.

What comes off the wall when RingUps goes in

Most bridal stores do not run one system. They run a system plus the things they built around it because the system could not hold them.

• The paper appointment book, and the second copy someone keeps on their phone.
• The spreadsheet of special-order deadlines, with its column of dates typed in by hand.
• The deposit tracker that only balances if nobody was off sick.
• The alterations whiteboard, and the four separate reports a previous system needed to stand in for a workroom.
• The separate email tool that never knew which bride had already picked up.
• The owner who keeps the rest of it in her head, and cannot take a week off.

What it does not replace, and should not

RingUps is not your accounting package. It is not your card processor, and stores keep the processor they already have. It is not a website builder, and it does not replace the designers' own ordering portals, because purchase orders print rather than transmit.

Bridal Web Solutions, for the record, is not a thin product: roughly 85 reports, 156 pages and 11 subsystems, dating to 2006. Depth you will never finish configuring is a different thing from capability. Its own screens flag 14 of Cande's 22 primary suppliers as never fully set up and 82 categories hidden.