Solutions

One van or forty locations

The platform is the same for everyone. What changes is which parts you switch on, how permissions are scoped and where the reporting rolls up. Here is what genuinely differs by operating model.

What matters mostMobile installerShopDistributorEnterprise
Primary constraintTime between jobsBay and technician capacityStock and fulfilmentConsistency across sites
Runs the day fromPhone in the vanDispatch boardWarehouse and counterRegional dashboards
InventoryOrder per jobSmall stocking plus ordersFull inventory controlVisibility across locations
UsersOne to threeFront office plus techsSales, warehouse, accountsRole-scoped, many sites
Reporting needPaid or not paidConversion and productivityMargin and fill rateExecutive roll-up and governance
Mobile installers

Run the business from the van

You are the CSR, the technician and the accounts department between stops. What matters is quoting on the spot, ordering the right glass the first time, and getting paid before you drive away.

Quote at the kerb

Decode the VIN on a phone, price the job and send it before you leave the driveway.

Order without switching apps

Check supplier stock and raise the order from the same screen as the quote.

Get paid on site

Text-to-pay closes the invoice while you are still with the customer.

Bays and technicians balanced

The dispatch board shows workload per technician per day so capacity is planned, not discovered.

Front counter to back shop

CSRs, technicians, accounting and the owner each see the same job through their own role.

Website into schedule

Hosted quote pages turn visitors into structured requests that land in the CRM ready to book.

Auto glass shops

The whole shop on one board

A shop has more moving parts than jobs: bays, technicians, walk-ins, insurance work, stock on the shelf and a phone that does not stop. The operating picture has to hold all of it at once.

Distributors

Wholesale, counter and fulfilment

Distribution is not installation with a bigger warehouse. Wholesale accounts price differently, counter sales move fast, and fill rate is the number that decides whether customers come back.

Wholesale account pricing

Per-account pricing profiles applied automatically instead of remembered per customer.

Counter and retail sales

Walk-in sales handled alongside wholesale on the same stock and the same ledger.

Fulfilment and delivery

Orders picked, fulfilled and routed with the demand data that generated them.

Cross-location visibility

Every site's jobs, stock and compliance status in one view, with drill-down to the individual record.

Standardised without slowing sites down

Shared pricing profiles, workflows and documentation standards that locations inherit rather than reinvent.

Role-scoped access

Permissions by location and function, with audit logging on the changes that matter.

API into your stack

Jobs, vehicles, inventory and invoices available programmatically for the systems you already run.

Enterprise

Consistency is the hard part

At scale the problem stops being any single job and becomes whether every location does it the same way. Enterprise deployments centre on governance, roll-up reporting and control — without forcing each site through head office to get work done.

Questions

Before you ask

Can we move between models as we grow?

Yes. A mobile operator that opens a shop keeps the same records and switches on the modules a shop needs. Nothing is migrated or rebuilt.

Do we pay for modules we do not use?

No. Licensing is à la carte — see pricing.

Can one business run both wholesale and retail?

Yes. Pricing profiles handle the two channels on the same stock and the same customer base.

Is there a limit on locations or users?

No hard limit. Enterprise deployments are scoped by location count, roles and reporting requirements.

Find the setup that fits how you work

Fifteen minutes on your actual operating model beats an hour of generic features.