SaleShade Desk · Multi-location

The shop you are not standing in

Every location's enquiries, estimates and conversions side by side. Which shop bills most is easy. Which one sells best is the question you cannot answer.

You would not hear if something were quietly wrong

The second location is doing all right.

Nobody would. Nothing that fails slowly announces itself, and a shop can lose customers for two years without a single month looking bad enough to ask about.

What you know

The billing is all right — and it arrives every month without anyone asking

What you do not

How many people walked in — and how many left without being recorded
How many took an estimate — and were never called back
Whether the man who has been there two years — is converting anything at all

One product master across every location

Products, codes and rates are the same across every location.

One master, one price list, set once and current everywhere.

That is not a restriction, it is how this trade works. A system that let each shop keep its own rates would be solving a problem you do not have and creating one you do — a customer quoted one figure at your first showroom and a different one at your second.

→Your product master →Price lists

Everything else recorded per location

Enquiries — and where each one came from
Estimates — and what they were worth
Conversions — against that location, not the group
Follow-ups done — and follow-ups missed

All of it recorded against the location it happened at, and all of it available in one view with filters — or one location at a time, if that is what you are looking at this morning.

Biggest is not the same as best

Which location bills the most is easy.

→Where the enquiries came from →Reports

Which bills the most

You have always known this. It is usually the one with the most footfall.

Which converts best

A different question, and until now there has been no way to ask it. A busy shop with poor conversion looks entirely healthy on a revenue report while turning away more customers than the small branch across town.

And below location level

Which salesman at which shop is converting what — a harder conversation to have, and a considerably more useful one.

Your team sees their shop. You see all of them.

Every user belongs to one location and sees that location's work — his customers, his estimates, his follow-ups.

Admins and super-admins belong to all of them. You switch between locations when you want to look at one properly, or open the combined view when you want to compare.

→Who can see and do what

Which also means a salesman moving to another branch is a change you make, not a database problem.

Locations are not godowns

Locations are where you sell.

→More than one godown

Adding a location adds a place to look, not a second set of administration.

See it across your own locations.

Ask for a demo

Locations

Where you sell — showrooms, counters, branches

Godowns

Where you keep things — handled separately — three showrooms and one godown, or the reverse