RingUps holds a bridal store's gown catalogue and its floor inventory in the same place. The catalogue is the style: designer, style number, silhouette, neckline, colour and dye lot. The floor inventory is every physical sample you own, one record per dress, so a consultant can answer which gown a bride can try on today.
Designer, style number, silhouette, neckline, sleeve, waistline, colour and dye lot, price, supplier lead time, and the photographs. Silhouette and neckline are what a bride actually says out loud, so they are first-class fields rather than notes typed into a description box. Fabric is the one attribute nobody should take from a photograph, and RingUps flags it for a person to confirm.
Because three is never three. One sample is on a bride in room two, one went to the cleaner after a trunk show, and one has a hook missing at the back. A quantity field cannot hold any of that, so the count drifts, and once it drifts nobody trusts it again. The knowledge moves into a consultant's head and a pencil note on a rack tag.
This is measurable, and it is measurable inside the system a store already pays for. When Cande Bridal Boutique's data was reconciled during the move off Bridal Web Solutions, two screens in that same system gave two answers for the same question.
Category Defaults said 655 units in stock. The store's own inventory export, from the same system, said 506.
Reconciliation finding, Cande Bridal Boutique, verified 4 August 2026
Bridal Web Solutions is a deep system dating to 2006, and depth is not the issue. Configuration is. Its own reports flagged 14 of Cande Bridal Boutique's 22 primary suppliers as never fully set up, and 82 categories hidden. Depth you will never finish configuring is not capability. Before you compare systems, ask an owner to reconcile their current one against itself.
In most retail, stock is a number. Twelve of a shirt in a medium are interchangeable, and the twelfth is as good as the first. Bridal does not work that way. A bride tries on the sample, and the sample is a particular dress that has been zipped and unzipped for a year.
So RingUps records a unit rather than a quantity: one row per physical dress, carrying its size, its condition, any flaw worth noting, and where in the store it is right now. That is what lets a consultant say yes, we have that, in a 10, and you can try it on this afternoon. 500 of those records came across for Cande Bridal Boutique on 23 July 2026.
Nobody walks in asking for style A1359. They ask for strapless, A-line, lace at the top, nothing too sparkly. So search in RingUps runs on the attributes and on the designer and style number, and the filters are the words she used.
Gown name search is the honest exception. In the catalogue that came off Bridal Web Solutions, 610 of 730 product rows have no product name at all, because nothing ever required one. A name search over that data returns almost nothing, so RingUps does not lead with it and this page will not demonstrate it.
This is the part of a migration nobody quotes for, and it is the part that decides whether leaving is possible. A catalogue without pictures is a list of style numbers. If those pictures are served from the vendor's domain, then the catalogue you think you own is a set of links into someone else's building, and they work exactly as long as you keep paying.
When Cande Bridal Boutique moved off Bridal Web Solutions, every image was pulled down and rehosted, so the store now serves its own gown photographs from its own storage. 427 of them. The remaining 197 styles had no image in Bridal Web Solutions either, which is worth knowing before anyone claims a catalogue is complete.
The same argument applies to everything a store configures over the years and never thinks about again. Contract bodies, email template bodies, scheduled message rules, supplier lead times, size charts, booking-builder configuration and per-bride notes have no export behind them. They die with the subscription. For Cande Bridal Boutique they were captured by hand from a live session, because there was no other way to get them out.
| Measure | Count |
|---|---|
| Gown styles catalogued | 625 |
| Photographs pulled off the vendor's servers and rehosted | 427 |
| Styles with no image in Bridal Web Solutions either | 197 |
| Configuration with no export behind it | Captured by hand |
Verified against production, 4 August 2026.
Four steps. The store does the first and the last. RingUps does the two in the middle, and every row is idempotent and reversible by batch, so a bad import is undone rather than argued about.
An export from your current system, a spreadsheet, or photographs of a binder. For Cande Bridal Boutique it was the Bridal Web Solutions exports, and they disagreed with each other, which is normal and is handled rather than ignored.
624 of 625 products matched to a supplier record across 23 suppliers and 49 divisions. The one that did not match was a row called Credit, which is a bookkeeping line and not a gown.
427 gown photographs were downloaded and rehosted into the store's own storage. 500 per-unit floor inventory records were imported on 23 July 2026, one row per physical dress rather than a quantity.
Attributes that no export carried get added on the floor, a style at a time, usually as gowns are handled anyway. RingUps can draft them from the designer's photograph, and a person accepts or rejects each one.
Upload the designer's product shot and RingUps drafts the style name, silhouette, neckline, fabric, sleeve and waistline as chips a staff member accepts or rejects one at a time. Nothing is written until someone accepts it, and fabric and collection are always flagged as worth checking, because a photograph cannot honestly tell you either one.
The feature requires an Anthropic API key provisioned for your store. It is not switched on by the act of subscribing, and we would rather say that here than have you find it on a Tuesday afternoon with 300 styles to tag.
One store, one migration, verified against the production database rather than remembered. These are migration figures with a date on them.
The live catalogue is larger now, because Cande Bridal Boutique has been trading since: 735 styles and about 502 floor units today. That is a current total, not a migration figure, and the two should never be quoted as if they were the same thing.
| What was migrated | Figure |
|---|---|
| Gown styles catalogued | 625 |
| Products matched to a supplier record | 624 of 625 |
| Gown photographs rehosted | 427 |
| Styles with no image in the old system either | 197 |
| Per-unit floor inventory records imported | 500 |
| Suppliers and divisions | 23 / 49 |
A style is the gown the designer makes. A unit is one physical sample hanging in your store: a specific size, in a specific condition, in a specific place. Retail stock is a quantity. Bridal stock is a list of individual dresses, because a bride tries on the sample, not the quantity. RingUps imported 500 per-unit floor inventory records for Cande Bridal Boutique on 23 July 2026.
You do, once they are rehosted. When Cande Bridal Boutique moved off Bridal Web Solutions, 427 gown photographs were pulled off the vendor's servers and rehosted so the store owns its own images. A further 197 styles had no image in Bridal Web Solutions either. If your gown images load from a vendor's server, your catalogue stops being a catalogue on the day the subscription ends.
Yes. Upload the designer's product shot and RingUps drafts the style name, silhouette, neckline, fabric, sleeve and waistline as chips a staff member accepts or rejects one at a time. Nothing is written until someone accepts it, and fabric and collection are always flagged as worth checking, because a photograph cannot honestly tell you either one. The feature requires an Anthropic API key provisioned for your store.
A catalogue tells you what exists. Special orders is where a gown gets ordered against a wedding date, and where the dye-lot guard blocks a purchase order at placement.
See special ordersWhen a sample has done its time on the rack, list it with a condition rating, a flaw note and four photographs. Discovery and enquiry between stores. Rolling out, waitlist open.
See the marketplaceEvery figure on this page comes from one real store in Kelowna, British Columbia. The case study has the rest of it, including what the reconciliation found.
Read the case studySend your gown list ahead of the call, in whatever shape it is in, and we will have your own catalogue loaded and searchable when you arrive.