One price list has to serve two worlds
A retail unit and a two-bed flat need different services at different prices, and a single list forces a compromise that suits neither.
Mixed-use developments
Shops below, homes above, one system underneath
A retail floor and a residential tower are not the same operation, and they should not share a price list. Here each part gets its own services, its own prices and its own hours — while the staff, the queue and the reporting stay shared.
- price list per part of the site
- 1price list per part of the site
- queue across the whole development
- 1queue across the whole development
- services, switched on separately
- 8services, switched on separately
- reports that add up across both
- 10reports that add up across both
Before the software
What usually goes wrong here
Nothing on this list is a failing of your team. They are all what happens when the work is real and the record of it is not.
Retail hours and residential hours collide
A shop wants cleaning after closing. A resident wants it mid-morning. One set of bookable hours cannot hold both.
Staff are shared but records are not
The same technician works both sides, and their day is split across two systems, so nobody can see their real workload.
The owner wants one set of figures
Two systems means two exports and a spreadsheet in the middle, which is where the numbers stop agreeing.
Separate where it matters
Each part of the site prices itself
Catalogs are per building and per service, so the retail side and the residential side each get their own items, prices, bookable windows and cancellation terms — published independently.
- Different items and prices for retail and residential
- Bookable hours set separately, so late cleaning is possible on one side only
- Cancellation policy set per part of the site
- Recurring discounts configured independently
- Publish one side without touching the other
app.360safeops.com/catalog
Shared where it helps
One roster, one queue, one day's work
Staff are assigned to buildings and services, not to a silo. A technician covering both sides sees one list, and their coverage shows up in the same report as everyone else's.
- Staff assigned per building, per service and per subcategory
- One queue holds retail and residential jobs together
- Coverage gaps visible across the whole development
- Escalation paths still set per building
- One audit trail, whichever side the job came from
app.360safeops.com/staff
Owner's view
Figures that add up across the whole site
Because both sides sit on one record, the reporting does not need reconciling. Ageing, staff coverage, request volumes and incident analytics all read the same underlying data.
- Ten built-in reports across the whole development
- Invoice ageing per part of the site or in total
- Request volume and response times side by side
- Repeat-incident alerts wherever the problem recurs
- Printable records for a lease, an invoice or a request
app.360safeops.com/reports
What residents can book
The services that matter at a place like this
Services are switched on per building, so the retail floor and the tower above it can offer completely different things.
Maintenance
No work starts until the resident agrees the cost.
- Staff record the diagnosis on site
- A written estimate goes to the resident
- Approve or decline in the app
Housekeeping
Cleaning on a schedule residents control.
- One-off or recurring — daily, weekly, fortnightly
- Discount applied automatically to recurring plans
- Bookable hours set per building
Guest reception
Visitors expected, verified and logged.
- Residents issue a pass before the guest arrives
- Verified at the desk, entry and exit both logged
- Walk-in policy set per building
Report an incident
Nothing gets lost between a complaint and a fix.
- Severity from low to critical
- Staff triage before assignment
- Escalation paths defined per building
Concierge
Errands and requests, tracked like any other job.
- Free-text requests with photos or files attached
- Assigned, timed and completed like every service
- Premium tiers get their own response targets
Social & events
Community programming that actually fills up.
- Eleven event types, from movie nights to festivals
- RSVP with automatic waitlist when full
- Check-in and no-show tracking
How it runs
One request, from start to paid
The same four beats every time, whichever service it was and whoever raised it.
- 01
The site is split
Retail and residential are set up as their own buildings, each with its own units and its own catalog.
Once, at setup
- 02
Each side is priced
Items, hours, discounts and cancellation terms are set separately, then published when they are right.
Independently
- 03
Staff cover both
One roster, assigned by building and service. A shared technician sees a single list, not two.
One day's work
- 04
The owner reads one number
Reporting runs across the whole development, so nothing has to be reconciled in a spreadsheet.
No exports
Questions
What operators ask about mixed-use developments
If yours is not here, the FAQ page goes further — or just ask us directly.
Can a retail tenant and a resident use the same app?
Yes — it is the same app, and what each of them sees comes from their own building's catalog. A shop is offered the retail price list, a flat the residential one.
What if the two sides are managed by different companies?
Access is scoped per building, so a manager can be given rights to one side and not the other while the owner keeps a view across both.
How many parts can one site have?
As many buildings as the site actually has — the model is per building, so a three-tower development with a retail podium is four buildings under one client.
Other kinds of property
Start here
See it running in a mixed-use development
Bring one building, its list of units and the services you already offer. We'll set the price list up with you, then you can watch a real request go all the way from a resident's tap to the invoice.
No card needed · Your data stays yours