chaochudby JRYWedding-shop software that works like a dress ledger, where bookings never clash
Wedding shops have run on dress ledgers for years: one page per dress, with each bride's name and event date listed down the page. ChaoChud keeps that way of thinking, but makes it impossible for two bookings to collide, even when several sales staff are serving customers at once.
The demo is a fictional shop with fictional data. Every button works and nothing is saved for real.
| Event date | Customer | Status |
|---|---|---|
| Sat 17 Oct | Pim · Chiang Mai | Confirmed, deposit paid |
| Sun 1 Nov | Kaew · Bangkok | Held until 20 Oct |
| Sat 14 Nov | May · Khon Kaen | Swapped from LN-004 |
Back-office-only mode, for shops that close the sale in store
Most wedding-dress customers need to try a dress on first, so the shop does not need a page where customers book by themselves. In this mode the sales team uses only the back office, on a phone or a tablet in the shop.
Open one dress and see its full customer queue by event date, with photo, code and price group. Search by event date to see every dress that is free that day.
A customer who asks you to hold a dress before paying the deposit looks different from a confirmed booking, and the hold has an expiry date. The sales team always knows which bookings need chasing.
The customer tries another dress and wants it instead. The system checks the new dress is free on the event date, moves the booking in one step, calculates the price difference and releases the old dress straight away. Changing the event date works the same way.
Every bill is tied to the sales person who opened it. See each person's totals for any period, with no counting from the ledger.
Bookings, swaps, discounts and cancellations are all logged: who did it, when, and what changed from what to what.
Add extras to the bill, and the system blocks the cleaning days after each event automatically. A dress's next booking can only start once the dress is genuinely ready.
How to get started
- We agree your shop rules: price groups, deposits, cleaning days and each staff member's permissions
- You send your dress list and photos. We enter the data for you, including upcoming bookings from your existing ledger
- Your sales team starts using it in the shop. Keep the old ledger alongside until you are confident
Frequently asked questions
Can customers book on a website themselves?
That is optional. Many wedding shops want customers to talk and try dresses on first, so they use the back office only. If you want an online storefront where customers check free dates themselves, it can be added.
Can we move our existing bookings from the notebook?
Yes. Before you start, we enter the upcoming bookings for you, and you can check them against the notebook dress by dress.
What can each sales person see?
Permissions are set per person. For example, someone can create bookings but cannot give discounts or edit prices, and every change is logged with who made it.
Does the back-office demo use real data?
No. The demo is a fictional shop. Its data stays in your own browser, and you can press every button without touching any real system.
Talk to June about your shop
Tell us roughly how many dresses you have, how many sales staff, and how you track bookings today. We will look together at whether the system fits, and if it does not, we will say so.