RingUps gives every person in a bridal store their own account rather than one shared counter login, at no extra cost on any plan, so a Saturday part-timer, a seamstress and a bookkeeper are separate people in the system instead of the same password. Bring your staff list to a demo and we will set up exactly what each of those accounts can reach, in front of you.
A store like Cande Bridal Boutique in Kelowna, British Columbia has an owner, one or two full-time stylists, a couple of weekend part-timers and a seamstress who may not be an employee at all. Each of them touches a different part of the week. The stylist lives in appointments and orders. The seamstress lives in the workroom. The part-timer is there on Saturday, sells a gown, takes a deposit and goes home. The owner is the only one who needs to know what the month came to.
A weekend part-timer does not need the revenue report. That is not suspicion, it is tidiness: a person given four screens to do their job does it faster than a person given forty, and a number they cannot explain is a number they will be asked about by a bride.
The right answer for a store this size is personal logins by default and a short, explainable set of differences on top, decided once with a person who knows the product - not a permission scheme with dozens of switches that nobody has time to maintain.
The left of this table is the store, not the software: it is the shape of a five-person bridal team and what each person reaches for in a week. The right-hand column is the part we are willing to put in writing about RingUps today. Where it says the setup is walked through on a demo, that is because we would rather show you the screen on your own staff list than publish a grid you have not seen working.
| Person | A typical week | Reaches for | Has no reason to open | Where RingUps stands today |
|---|---|---|---|---|
| Owner | In three or four days a week, and carries everything nobody else carries. | Revenue, deposits held, what is owed, supplier orders, the whole reporting hub. | Nothing. | The owner account is the one the store is set up around. The one thing we will state without a demo is that it is not the only account that can move data: the import screen has no role gate, so any signed-in user can run or roll back an import. |
| Full-time stylist | Appointments most days, writes the orders, keeps the brides. | The appointment book, a bride's record, orders, deposits, the special-order deadlines. | Month-end reporting, supplier cost prices, payroll-shaped numbers. | Her sales and her appointments are what employee attribution is built on, and imported history barely carries it: 3 of 1,403 orders carry a selling staff id. Ask to see sales-by-employee on your own data before you rely on it. |
| Weekend part-timer | Saturdays. Sells a gown, takes a deposit, books the next fitting, goes home. | Today's appointments, the bride in front of her, checkout. | The revenue report, cost prices, another person's numbers, the import screen. | This is the setup question owners ask first and the one we answer on a demo rather than in a diagram. Bring the staff list and we will open the screens a Saturday hire would see, in front of you. |
| Seamstress | In the workroom, often a contractor rather than staff. | The alterations workroom: which gowns are in the room, whose they are, what is due when. | Payments, the sales floor, anything to do with revenue. | The workroom is one screen in RingUps, which Bridal Web Solutions does not have at all. It holds zero rows in production today, and it records no seamstress pay, no cost and no margin, so it cannot tell you what the room earned. |
| Bookkeeper | External. In at month end and at year end. | Reports and exports. | The appointment book, bride contact details, the sales floor. | There are 28 standalone report pages plus a hub, and 30 export keys. Reports are pull-only: nothing is scheduled and nothing is emailed, so somebody signs in and pulls them. |
Four steps. Each one says what the manager does and what RingUps does in response.
The manager adds the new hire by name. RingUps creates a staff record for them, which is the thing appointments, orders and training attach to later. Adding a person does not change your invoice: staff logins are unlimited on every plan, which is the whole reason personal accounts are realistic in a store this size.
The invite is a link tied to that staff record. It is what turns a name on your list into an account with a password only that person knows, so the shared counter login stops being how anyone signs in.
The manager copies the link out of RingUps and forwards it by hand, in whatever the store already uses to message people - text, email, whatever is fastest. Ten seconds, and the invite comes from someone the new hire actually knows instead of an automated email sitting in a junk folder.
The new person sets up their own sign-in. From that point their work is recorded against their own staff record rather than a counter login everybody shares, which is what makes a selling staff id on an order or a stylist id on an appointment worth anything at all. Onboarding them is a separate thing again, and the training portal is where courses, progress and certificates live.
An illustration with sample names. RingUps has an owner account and staff accounts. The finer detail of what each person can reach is walked through on a demo rather than printed here, so this panel shows the part we can describe without qualification: the list, and the invite you have to send yourself.
RingUps does not send this. Copy it and forward it to her yourself.
Illustration with sample names in a built screen. Job descriptions here are how a store would label its own people; the permission detail behind each account is walked through on a demo.
A permission scheme nobody maintains is a shared password with extra steps.
Photographed on the sales floor at Cande Bridal Boutique, Kelowna, British Columbia.
Because employee attribution is nearly absent in imported history, and this is the first thing an owner does once her team is set up: she looks up her team's numbers. Sales-by-employee reads a selling staff id on the order. Closing rate reads a stylist staff id on the appointment. In the history that migrated across, 3 of 1,403 orders carry the first and 8 of 3,851 appointments carry the second.
Both reports are real reports. They are simply running on near-empty data for a store that has just switched, and we do not screenshot them as populated. The figures that will be worth reading are the ones your team records in RingUps from the switch onward, which means a useful sales-by-employee report is a season away rather than a day away. Anyone who tells you otherwise has not looked at what their own import carried.
This is worth knowing before you set up your team rather than after, because it changes what you do first. Personal logins from day one are what make the attribution accumulate at all. The reporting page covers the rest of what the reports do and do not carry, including the categorisation gap.
Verified against production on 4 August 2026. RingUps has no commission-per-employee calculation and no debit-machine reconciliation.
Because a system that charges per seat makes proper accounts an expense, and a shop with four people and a Saturday hire will not pay a monthly fee for someone who works six days a month. So one login gets set up at the counter, the password goes on a note taped inside the till drawer, and everybody uses it. That is not carelessness. It is the rational response to being charged for the thing you are being told to do.
The costs show up later and they are not dramatic. Nobody can tell who wrote the order. The person who left in March still knows the password. Every report that reads a staff id reads nothing, because there was only ever one staff id and it belonged to the counter. Permissions become theatre, because there is only one account to apply them to.
RingUps prices staff logins at nothing on every plan for that one reason. It removes the argument for sharing before any of the rest of this page can matter. Making a login free is a smaller decision than a permission engine and it does considerably more, in a store with five people in it.
Three pages that carry the parts of the team story this one hands off to.
Adding a person to the staff list is not the same as teaching them the job. The training portal is where courses, assignment and progress live for a new hire, and neither BridalLive nor Bridal Web Solutions has an equivalent.
Training new staff →Where sales-by-employee and closing rate live, what the 28 report pages cover, and the rest of what a freshly migrated store should expect its first month of reporting to look like.
The reports →Who can see your data from outside the store, and how RingUps handles access and data security.
Security and trust →You add the person to your staff list and RingUps generates an invite link for them. RingUps does not send that link. Staff invite emails are not sent from inside RingUps, so a manager copies the link and forwards it by hand, using whatever the store already sends messages with. The person opens the link and sets up their own account.
Bring that question to a demo with your own staff list, because it is a setup decision and we would rather show it to you than print a matrix. What we will state flatly is the part that is already verified: every person gets their own login at no extra cost, and the import screen has no role gate at all, so import is not owner only. Ask us to open the screens a weekend part timer would see and judge it there.
Bring your staff list, including the weekend people. We will set the team up in front of you and open the screens each of them would see, so the answer to what your Saturday hire can reach is something you watched rather than something you read.