RingUps holds the asset underneath a bridal store's marketing: the gown photographs themselves, served from your own storage rather than a supplier's, with structured attributes attached to every style. Upload a designer's product shot and RingUps drafts the silhouette, neckline, fabric and sleeve for a person to accept or reject - the groundwork for every post, listing and consultation that photograph goes on to power.
Everything on this page is running in production today, verified against a real bridal store's catalogue.
Photographs. Not a posting schedule, not a strategy document. A bridal store's marketing is made of gowns on real people, shot by real photographers, and the store either has those files or it does not. Everything else is a distribution problem that a person with a phone can solve in ten minutes.
Which is why RingUps works on the files rather than on the posting. The photographs below belong to Cande Bridal Boutique in Kelowna, British Columbia, and they are the reason this page exists at all.
This is the question nobody asks until the month they are leaving. If your gown images are served from your software vendor's domain, then what you think of as your catalogue is a set of links into someone else's building, and they work exactly as long as you keep paying. The same images are usually the ones your staff pull from when they post.
A catalogue without photographs is a list of style numbers.
When Cande Bridal Boutique moved off Bridal Web Solutions, every image was pulled down and rehosted, so the store serves its own gown photographs from its own storage. 427 of them. The remaining 197 of 625 styles had no image in Bridal Web Solutions either, which is worth knowing before anyone calls a catalogue complete.
The photographs are the visible half of this. The other half is everything a store writes once and never thinks about again. Contract bodies, email and message 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.
Attributes, not prose. 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 to the style record until someone accepts it, and fabric and collection are always flagged as worth checking, because a photograph cannot honestly tell you either one.
That is the useful half of a content tool for a store with 625 styles and no time. Once a gown has silhouette, neckline and sleeve on it, the person writing a post has something to write from, and so does the consultant answering the message that post produced.
The condition is worth stating twice. This feature requires an Anthropic API key provisioned for your store. Subscribing does not switch it on, and we would rather say so here than have you find it on a Tuesday with 300 styles to tag.
Two things, and it is worth being specific about both. The first is the catalogue: the image sits on the style record next to the designer, style number, silhouette, neckline, price and lead time, so a consultant on the floor is looking at the gown and the facts about it in one place.
The second is a marketplace listing. When a sample has finished its time on the rack, a listing takes four photographs, a condition rating on a five-tier scale and a flaw note before another store can find it and enquire. The four-photograph gate is the interesting part: it is the one place in RingUps where content is a requirement rather than a nicety, because a store buying a used sample sight unseen deserves to see the hem.
The marketplace is discovery and enquiry. There is no checkout, no payment and no escrow in it, and it is rolling out with a waitlist rather than operating as a populated network.
After a migration they are served from your own storage rather than a supplier's. When Cande Bridal Boutique moved off Bridal Web Solutions, 427 gown photographs were pulled off the vendor's servers and rehosted. A further 197 of the 625 styles had no image in Bridal Web Solutions either. If your gown images load from a supplier's server, your catalogue stops being a catalogue on the day the subscription ends.
On the gown style record in the catalogue, and on a marketplace listing. A listing takes four photographs, a condition rating on a five-tier scale and a flaw note before another store can find it and enquire. That is discovery and enquiry only: there is no checkout, no payment and no escrow. The marketplace is rolling out and the waitlist is open.
Where the 427 rehosted photographs actually live, alongside the style attributes, the size charts and the per-unit floor inventory.
See the catalogueThe one screen where photographs are mandatory: four of them, a condition rating and a flaw note. Discovery and enquiry, rolling out with a waitlist.
See the marketplaceWhat RingUps does send, which is email, and the suppression log that answers why a particular bride never received a particular message.
See communicationsBuy RingUps for the deadlines, the workroom, the deposits and the catalogue. Read this page as a reason to believe the rest of the site, not as a reason to sign.