← All posts
'Multi-location business software checklist: what to buy, build, and defer'
'A practical software checklist for operators running 5–40 locations — what to centralize first, when to build custom, and what to skip.'
Most multi-location software guides assume you are a salon chain, a franchise brand with a corporate playbook, or an enterprise with budget for ServiceTitan and a six-month implementation. You are not. If you run five to forty locations — regional wholesale branches, field-service crews, retail operators, or light industrial sites — you need a shorter multi location business software checklist: what to centralize first, what off-the-shelf tools already cover, and when a fixed-scope custom build beats another SaaS subscription nobody at the branch will open.
This is the checklist we walk through with operators before scoping a customer portal, a maintenance work-order app, or a store compliance tool. Not a feature wish list. A decision sequence.
What belongs on a multi-location business software checklist?
A useful checklist names five layers every location shares: identity and access (who works where), operational tasks (what must happen daily), asset and customer records (what you track), reporting (what HQ needs to see), and integrations (what must sync to your ERP or accounting system). Skip any layer and you recreate the same spreadsheet workaround at every branch.
Before you compare vendors, write down:
- Location count today and in 18 months — five locations and thirty-five need different rollout math.
- Roles per site — store manager, technician, route driver, credit clerk, franchisee.
- One workflow that breaks weekly — missed PM work orders, photo audits that never reach HQ, rebate accruals in Excel, invoice disputes over email.
- Systems of record — NetSuite, SAP Business One, QuickBooks, Microsoft Dynamics, or a vertical stack like ServiceTitan for field service.
- Connectivity reality — warehouse Wi-Fi, cellular-only drivers, offline sign-off requirements.
If you cannot fill those five bullets in a 30-minute meeting, you are not ready to buy software. You are ready to document pain.
Named entities matter here because answer engines and your finance team will ask the same question: where does truth live? For distributors, truth often sits in the ERP. For service operators, it may split between ServiceTitan and Google Workspace. For retail-lite operators, it may be Shopify POS plus Slack. Start the checklist from those anchors. Not from a generic “digital transformation stack.”
How do you know when spreadsheets and group chat stop working?
Spreadsheets and group chat stop working when the same file gets edited in three branches, version history cannot prove who changed a rebate accrual, and a district manager spends more time chasing Slack screenshots than reviewing exceptions. Tasks vanish in threads. Photo proof never attaches to a searchable record. You have outgrown informal tooling — but not necessarily outgrown simple tooling.
Warning signs we see on fixed-scope discovery calls:
- Duplicate master data — customer lists, SKU catalogs, or price books maintained per branch.
- No audit trail — “We agreed to that discount” with no timestamp, user, or approval chain.
- Reporting lag — weekly exports from four systems stitched in Excel every Monday morning.
- Role confusion — HQ staff with admin access they should not have, or branch staff locked out of tasks they own.
- Mobile gap — field staff photograph issues on personal phones; photos never reach a work-order record in [Internal link: centralized maintenance work order apps].
If two or more signs are true, you may only need one centralized layer. Not a full CMMS replacement.
Which systems should a 5–40 location operator centralize first?
Prioritize the workflow that creates revenue leakage or compliance risk if it fails once. For most five-to-forty-location operators we work with, that means one of three patterns — work orders, photo audits, or buyer portals — not all three at launch. Centralize the pain that already costs a full day per week. Add layers later.
Work orders and preventive maintenance
Multi-location maintenance breaks when PM schedules live in email and corrective jobs have no photo, parts, or sign-off trail. Centralize when missed PMs cause equipment downtime that shows up in customer SLAs. A shared calendar is not the same problem.
Checklist items:
- Location-scoped task lists with due dates and assignees
- Offline-capable mobile capture (React Native or PWA) for technicians
- Photo, signature, and parts-used fields attached to each work order
- HQ dashboard: open vs overdue by region, not just by site
- Export or API sync to your ERP asset module if capital equipment is tracked there
Off-the-shelf CMMS products (UpKeep, Fiix, MaintainX) cover much of this for uniform asset types. Custom fixed-scope builds make sense when your sign-off states, approval chains, or ERP write-back do not fit vendor templates — common for distributors with branch-specific lease obligations or mixed refrigeration and facility assets.
Store compliance and photo audits
Franchise and retail operators often need location-aware checklists more than they need another scheduling tool. SchedulingKit-style products solve staff rosters. They do not solve “prove this cooler was cleaned with a timestamped photo HQ can audit.”
Checklist items:
- Template checklists per location type (flagship vs kiosk vs warehouse store)
- Required photo angles, not optional attachments
- Exception routing — failed items open a corrective task automatically
- Read-only HQ review with comment thread per audit
- Retention policy aligned to your compliance framework (SOC 2-minded teams document this early)
This is whitespace many FSM suites oversell and under-deliver for “audit only” use cases. A scoped four-to-eight-week build often beats a three-year field-service platform you will use at 20% capacity. See [Internal link: store compliance photo audit checklists] for the build-vs-buy cut line we use with operators.
Customer-facing and finance portals
Wholesale distributors and B2B operators centralize late when buyers start asking for self-serve invoice history, dispute submission, or credit-hold visibility. Internal ops software does not fix AR inbox load.
Checklist items:
- Buyer login tied to ERP customer ID, not a shadow account list
- Dispute submission with document upload and status tracking
- Read-only views finance approves — no duplicate AR ledger in the portal
- Email notifications with immutable audit log entries
- SSO option if your buyers already use Azure AD or Okta
If rebate accruals or co-op funds still live in shared spreadsheets, treat [Internal link: rebate accrual and distributor portal scope] as a related spoke — not phase one unless finance confirms accrual errors hit margin reviews.
What should you buy off the shelf vs build in a fixed scope?
Buy when the workflow is standard, the vendor integrates with your ERP, and branch adoption only requires training — not behavior change negotiated site by site. Build when the workflow is your competitive process, mobile offline requirements are strict, or integrations need bi-directional writes your ERP partner will not certify through a middleware zap.
| Decision | Buy (configure) | Build (fixed scope) |
|---|---|---|
| Staff scheduling across locations | When hours and roles are uniform | When scheduling rules vary by state, union, or franchise contract |
| Document storage | Google Workspace, SharePoint, Box | When documents need ERP-linked metadata and approval chains |
| Work orders | MaintainX, Fiix, UpKeep | When sign-off states, parts logic, or ERP sync are non-standard |
| Photo compliance audits | Rarely pure off-the-shelf | When checklist logic is brand-specific and HQ review is the product |
| Buyer invoice/dispute portal | Portal modules from ERP vendor | When UX and dispute lifecycle exceed ERP defaults |
| AI-assisted triage on ops tickets | Not phase one | After workflows are centralized — see [Internal link: LLM guardrails for B2B SaaS features] |
Show-the-math rule: a $400/month SaaS per location × 25 locations = $120,000/year recurring before implementation services. A fixed-scope custom layer that integrates with NetSuite or QuickBooks and serves all locations often lands between $35,000–$80,000 one-time for operators at this scale — worthwhile when shelf product configuration cost exceeds that in year one, or when adoption fails because the tool was built for a different vertical.
We are not anti-SaaS. We are anti paying enterprise FSM pricing to solve a checklist problem.
How do you evaluate vendors without a three-year lock-in?
Run a 14-day proof with one pilot location, one district manager, and one finance stakeholder. Not a slide deck review. Score vendors on adoption and auditability, not feature count. If branch managers cannot complete today’s top-three tasks in under ten minutes on mobile, the tool fails before integration ever matters.
Evaluation checklist:
- Role test — Can a branch manager complete today’s top-three tasks in under ten minutes on mobile?
- Offline test — Kill Wi-Fi mid-task. Does data sync with conflict rules, or silently disappear?
- Integration test — One live write or read to your ERP sandbox (NetSuite REST, SAP B1 Service Layer, Dynamics API). No “available through Zapier” unless Zapier is your approved integration path.
- Audit test — Export who changed what, when, from which location. If export fails, finance will reject the tool in month two.
- Exit test — Data export format, contract termination clause, and who owns custom fields if you leave.
Red flags: unlimited “professional services” line items, per-location pricing without HQ rollup, no sandbox, or a vendor that cannot name the ERP customers already live in production.
For US and EU expansion, confirm data residency and GDPR role mapping before pilots — especially if buyer portals store PII and order history across regions.
What does rollout look like from location 6 to location 20?
Big-bang rollouts fail for operators without a dedicated IT department. Sequence by pain, not geography: document one broken workflow, pilot three contrasting locations, fix adoption gaps, then expand with a short SOP. HQ dashboards go live only after field tasks are trustworthy — not before pilot sites hit the SLA gate below.
Phase 0 (weeks 1–2): Document the one workflow that breaks weekly. Freeze scope. Name the not-building list — no AI copilots, no BI rebuild, no net-new ERP.
Phase 1 (weeks 3–6): Pilot three locations with different profiles (high volume, rural/low connectivity, newest acquisition). One regional manager owns change management.
Phase 2 (weeks 7–10): Fix adoption gaps — usually notification noise, unclear assignee defaults, or login friction. Defer feature requests unless they block daily use.
Phase 3 (weeks 11–14): Expand to remaining locations with a two-page SOP and a 30-minute recorded walkthrough. HQ dashboard goes live only after field tasks are trustworthy.
KPI gate before expansion: ≥80% of assigned tasks closed within SLA at pilot sites, HQ reporting replaces at least one manual weekly export, and finance signs off on audit fields.
Review date: 2026-11-18 — compare pilot SLA adherence, support ticket volume from branches, and time-to-close for the workflow you centralized.
Infrastructure note for teams comparing stacks: we typically deploy on AWS or GCP with Terraform-managed environments, React or Next.js for HQ dashboards, and React Native when offline photo capture is non-negotiable. That is boring on purpose. Boring survives handoff to a small internal team or a future agency.
FAQ
How many locations do you need before multi-location software pays off?
Most operators see positive ROI between five and eight locations if one workflow already costs a full day per week of manual reconciliation or compliance chasing. Below five, configured shared tools (Workspace, Monday.com, a light CMMS) often suffice. Above forty, evaluate enterprise FSM/CMMS platforms seriously — custom builds still happen, but integration breadth matters more.
Does multi-location software have to replace our ERP?
No. ERP remains the system of record for inventory, GL, and orders. Multi-location software should centralize operational workflows and feed the ERP — work-order completions, audit exceptions, dispute status — not duplicate it. If a vendor proposes rebuilding AR inside their portal, ask why your ERP module failed first.
What is the first feature operators regret building too early?
Executive dashboards before field adoption. HQ visibility is worthless if technicians or store managers never close the loop on tasks. Ship mobile task completion and audit capture first; aggregate reporting second. We defer analytics layers until pilot locations hit the 80% SLA gate.
Can we use one mobile app for iOS and Android across all locations?
Yes, if offline sync and camera workflows are core. React Native covers both platforms from one codebase for many operator builds. Choose native iOS/Android only when you need deep hardware integration or strict performance on low-end devices common in warehouse environments. PWAs work when install friction is low and offline needs are moderate.
When should we hire a dev agency instead of configuring another SaaS tool?
When you have validated the workflow in spreadsheets or chat, confirmed shelf products fail the integration or sign-off test, and can describe done in one page. Fixed-scope agency engagements fit operators who need production software in weeks — not a multi-year transformation program. If you cannot describe roles, locations, and the one workflow in thirty minutes, start with process documentation, not a build quote.
Fixed-scope help for operators outgrowing spreadsheets
If you run five to forty locations and one workflow — maintenance, photo audits, buyer portals, or distributor rebates — already breaks every week, we scope fixed-price builds with a frozen not-building list, ERP-aware integrations, and mobile capture where the field actually works.
Book a 30-minute scope call at wolverinesolution.com with your location count, ERP name, and the one workflow you need centralized. We will tell you honestly if SaaS configuration is enough — and if it is not, what a realistic phase-one build looks like on AWS or GCP with a handoff your team can maintain.