For multi-location groups

Two stores shouldn't mean two systems and two answers

Most bridal software treats a second location as a second subscription with a wall between them. RingUps was built with organization-level data separation from the first line of code, so a group is one business with many rooms — not many businesses you reconcile by hand.

$349
a month, up to 3 locations
+$99
per additional store
1
login for an owner across all of them
Group overview
3 stores · week to date
All locations
$41.2k
recognized
23
appointments
2
orders at risk
Kelowna$18.4k9 appts
Kamloops$14.1k8 appts
Vernon$8.7k6 appts
Vernon has both at-risk orders and the lowest conversion this week. One click into the store shows whether it's staffing, stock or a designer.
Transfers

The gown she wants is at your other store, in her size

In a group with separate systems, that sentence ends with "let me phone them and call you back." With shared inventory, the consultant sees the unit, its condition and its dye lot, requests the transfer, and tells the bride it will be here Thursday — while she's still in the room.

Every physical unit visible across the group, with its real status
Transfers tracked as movements, so nobody loses a sample between stores
The sale stays with the store that made it, however the stock moved
Group stock · Cascade A-line #A-2291
Kelowna · size 10, IV-4Floor sample
Kamloops · size 8, IV-4Transfer requested
Vernon · size 14, IV-4At the cleaner
Requested 14:22 · arriving Kelowna Thursday · bride notified automatically · sale credited to Kelowna.
Permissions

Managers see their store. You see all of it.

Role-based access per location, so a store manager gets their own numbers and their own staff without seeing the group's margins — and an owner never logs in three times.

Ownerall stores, all reports
Store managerone store, full
Consultantone store, no margins
Seamstressworkroom only
Group reporting

Compare your own stores like for like

Conversion, party attachment, alterations margin and sell-through, side by side per location — so a difference between two of your stores becomes a conversation rather than a hunch.

Kelowna conversion52%
Kamloops conversion47%
Vernon conversion31%
One catalogue

Buy once, carry it everywhere

One designer catalogue, one price list, one set of contract terms across the group — with per-store overrides where a location genuinely differs, rather than three copies drifting apart.

How the catalogue works →
Worth knowing before you commit
The architecture supports multi-location properly — organization-level data isolation was part of the design from the start, not bolted on. But it isn't proven in a live multi-store rollout yet: our production customer, Cande Bridal, is single-location. We'd rather tell you that directly than borrow a group customer story that doesn't exist. If you're a two-to-five store group, talk to us about being the first, and about what that's worth in price and priority.
Read what we can prove → Talk about being first →

Bring your rollout plan, not just your questions

Tell us how many stores, on what systems, in what order — and we'll tell you honestly what a sensible sequence looks like.

Book a demo Migration paths