Example configuration
Run many locations from one platform without flattening each one
A multi-location operator needs the whole picture and the detail of each site. This example configuration shows parent-and-store structure, location-level service work, equipment orders and campaigns across channels.
New location
Setup
Active
Service open
Where the work gets stuck
Common friction in retail and multi-location
Location-level detail lost in a flat customer list.
Orders and repairs requested location by location, by e-mail.
Promotions that differ in every market.
What you can run on Mako
Use cases for this example configuration
Parent company and store structure
A parent with child locations and permissions that limit each store or region to its own records.
Location service and repairs
A repair becomes a quote ticket, a work order and an invoice on that location's account.
Equipment and fixture orders
Orders move through a processing queue with a price list and history per account.
Customer campaigns
E-mail, text and social campaigns that share one brand profile.
Workflow examples
How the modules work together here
Each step uses a capability the platform has. Steps marked as configured to your business are set up with you.
Store service request to completed work order
A request from a single location.
- A quote ticket is raised on the store's account.Quotes and invoices
- A technician is found and a work order is issued.Work orders, technicians and requests for quotation
- The visit is scheduled and completed.Installations and scheduled work
- The invoice is issued to the same account.Quotes and invoices
Seasonal campaign across channels
One campaign, many touchpoints.
- The Records Explorer tags the segment to reach.Records Explorer
- Brand Intelligence keeps drafts consistent.Brand Intelligence
- Posts are approved and published to connected pages.Social publishing
- The e-mail goes out through Mailchimp and its analytics are reviewed.Email marketing with Mailchimp
Featured modules
The capabilities that matter most for this configuration
Multi-location and partner structures
Parents, children and partners, not a flat list.
DetailsGranular permissions
Each menu, list and tab is a permission.
DetailsEquipment orders
From order form to processing queue to history.
DetailsWork orders, technicians and requests for quotation
Field work assigned, accepted and tracked.
DetailsBulk management
Change owner and next action across large sets.
DetailsDashboard
The numbers a manager opens first.
DetailsRelated example configurations
Example configuration This page shows how Mako's modules can be arranged for Retail & Multi-Location. It uses sample data, is illustrative only and does not describe an existing customer or deployment. Anything described as configured to your business is set up with you.
Discuss a configuration for your locations
Show us how your stores, regions and service work are organised and we will map it to the platform with you.