TL;DR — Quick Summary
- Multi-location merchants are the highest-value segment in an ISO’s portfolio but require a fundamentally different onboarding approach: the onboarding sequence for a 10-location restaurant chain is not 10 times harder than a single location — it is 10 times harder plus the coordination complexity of a centralized decision-maker, distributed frontline staff, inconsistent local infrastructure, and location-specific variance in menu, workflow, and compliance requirements.
- The multi-location onboarding playbook has six phases beyond the single-location playbook covered in AD14: location-tiering (which locations go first, second, and third), centralized configuration before rollout, phased deployment with location-level checks, centralized reporting setup, staff training at scale (train-the-trainer model), and the 90-day governance checklist that monitors whether the account is stabilizing across all locations or concentrating risk in a few underperforming ones.
- The biggest mistake ISOs make with multi-location onboarding is treating it as 10 single-location onboardings: the ISO that deploys the AD14 playbook at 10 locations sequentially without a central coordination layer will spend three times the effort for two-thirds the result — and will create a support burden that follows the location with the most problems, not the merchant decision-maker who needs reassurance that the portfolio is under control.
Onboarding Playbook
Sequencing Strategy
Checklist Horizon
Why Multi-Location Is a Different Business Problem
A single-location merchant onboarding is a 1:1 relationship: one ISO, one merchant contact, one location, one training session, one go-live event. The ISO knows who the decision-maker is, who the frontline user is, and where the friction points are. The AD14 playbook covers this well. But a multi-location merchant — a franchise group with 8 locations, a regional restaurant chain with 20 sites, a hospitality group with 5 hotels — is not 10 single-location onboardings. It is a project management challenge with a distributed team, a centralized decision-maker who is not the daily user, and a risk profile that scales with the number of locations rather than the volume of a single store.
The ISO’s value proposition shifts from “I will set up your POS” to “I will run your rollout across your portfolio.” The ISO that can demonstrate a repeatable multi-location playbook — with location-tiering, phased deployment, centralized reporting, and a governance checklist — commands higher margins and lower churn than the ISO that treats multi-location as an afterthought of the single-location playbook. This article gives you the playbook.
go first and why
templates from HQ
local managers
health checklist
Phase 1 — Location-Tiering Before Signing
Before signing the multi-location agreement, the ISO needs to know which locations go first. Not all locations are equal: some are high-volume flagships that define the merchant’s brand, some are low-volume sites with high support burden, and some are in geographies with unreliable internet or compliance complexity (alcohol licensing, late-night operations, card-present vs card-not-present variance). The ISO that does not tier locations before signing is building a deployment plan on sand.
Tier A — Flagship Locations (2 to 3 locations): Highest volume, most visible to the merchant’s leadership, best local infrastructure (reliable internet, trained staff, stable management). Tier A locations go first because they are the proof of concept that justifies the rollout to the rest of the portfolio. If the ISO can show a Tier A location performing at 95 percent uptime with full staff adoption in 14 days, the merchant’s decision-maker has the confidence to commit to the full rollout.
Tier B — Standard Locations (5 to 10 locations): Average volume, standard infrastructure, no unusual compliance complexity. Tier B locations go second — after Tier A proves the concept and the ISO has refined the deployment checklist based on Tier A learnings. The ISO should build a Tier A lessons-learned document before touching Tier B.
Tier C — Challenged Locations (remaining locations): Lower volume, infrastructure gaps (spotty internet, high staff turnover, older hardware), compliance complexity, or geographic distance from the ISO’s support reach. Tier C locations go last — after the ISO has a refined playbook and the merchant’s HQ staff have been trained to support Tier C locally.
Phase 2 — Centralized Configuration Before Rollout
The most common multi-location onboarding failure is configuring each location individually — 10 locations means 10 separate configuration sessions, 10 sets of menu items, 10 printer configurations, and 10 times the risk of inconsistency. The correct approach is to configure once at HQ, push the configuration to all locations from a central template, and validate at each location before go-live.
Menu template (central): The ISO works with the merchant’s HQ to build a master menu template — categories, items, modifiers, pricing, tax rates, and comp keys — that applies across all locations. Local variance (location-specific items, regional pricing, state tax rates) is handled as exceptions layered on top of the central template, not as separate configurations. This means that when HQ updates the menu (seasonal item, promotional pricing), it propagates to all locations simultaneously.
Staff template (central): Role definitions, permission levels, and PIN management are configured centrally — manager vs cashier vs kitchen display permissions are consistent across locations, which makes multi-location reporting meaningful and reduces the support burden from role confusion.
Reporting hierarchy (central): Before any location goes live, the ISO sets up the reporting hierarchy: which HQ user sees which location, which reports are aggregated by region or district, and which alerts go to the ISO’s support team vs the merchant’s HQ vs the location manager. Multi-location merchants buy reporting as much as they buy a POS — the ISO that delivers a reporting hierarchy from day one wins the trust of the HQ decision-maker.
Phase 3 — Phased Deployment with Location-Level Validation
The ISO does not deploy all locations simultaneously. The phased approach: Tier A locations (weeks 1 to 3), Tier B locations (weeks 4 to 8), Tier C locations (weeks 9 to 14). Each location goes through the AD14 single-location playbook — pre-launch checklist, go-live day, 7-day stabilization, 30-day success criteria — but the ISO is managing multiple simultaneous locations at each phase, and the HQ decision-maker is receiving a portfolio-level status update, not individual location reports.
Location validation checklist (per location, at go-live): Internet speed test (minimum 10 Mbps upload), terminal pairing confirmed (all terminals communicating with the hub), menu sync verified (all items from central template present and accurate), printer mapping confirmed (kitchen display and receipt printer at correct stations), staff PINs loaded (all users from central staff template active), payment test transaction completed (card-present and card-not-present), and alert routing confirmed (location-level alerts going to the right local manager).
Phase 4 — Staff Training at Scale: The Train-the-Trainer Model
Training 50 staff members at 10 locations is not the ISO’s job for the full rollout. The ISO trains the merchant’s HQ staff — a training coordinator, a IT manager, and a operations manager — who then train the local managers at each location, who then train the frontline staff. This train-the-trainer model scales without multiplying the ISO’s time cost proportionally.
HQ Training (ISO-led, 1 day): The ISO trains the merchant’s HQ team on: the central configuration system, the reporting dashboard, the escalation path for multi-location issues, the process for requesting new menu items or pricing changes across the portfolio, and the escalation criteria for when a location needs the ISO’s direct support vs when the HQ team can resolve it locally. The HQ team leaves the training with a training playbook they own — not the ISO’s playbook that lives in the ISO’s head.
Local Manager Training (HQ-led, half-day per location): The HQ team trains local managers using the playbook they received from the ISO. Local manager training covers: daily opening and closing procedures, shift change reconciliation, how to run an end-of-day report, how to escalate a hardware or connectivity issue, and how to request a menu change through HQ (not directly to the ISO). The ISO attends the first two local manager training sessions as a quality check, then observes from a distance as the HQ team takes ownership.
Phase 5 — Centralized Reporting Setup
The HQ decision-maker needs a single dashboard that shows portfolio health at a glance: total processing volume across all locations, average ticket size, refund rate, chargeback rate, uptime by location, and staff activity by location. This is not a nice-to-have — it is the HQ decision-maker’s reason to stay with the ISO. The ISO that delivers a working multi-location dashboard at the 30-day mark has answered the question the merchant’s leadership was asking when they signed: “How do I know this is working across all my locations?”
Dashboard components (30-day milestone): Portfolio volume trend (daily, weekly, monthly), location-level volume comparison (which locations are above or below portfolio average), average ticket by location (flagging locations that are significantly above or below average), refund and chargeback rate by location (flagging locations that exceed portfolio average by 50 percent or more), uptime and error report (terminal downtime, payment decline rates), and staff activity report (active users per location, transaction count per user — useful for identifying understaffed or overstaffed locations).
Phase 6 — 90-Day Multi-Location Governance Checklist
The 90-day governance check is the most important milestone in a multi-location onboarding — it determines whether the account is stabilizing across all locations or concentrating risk in a few underperformers. The ISO schedules a formal 90-day business review (QBR) with the merchant’s HQ decision-maker, using the checklist below to structure the conversation.
| Checklist Item | Target | Action if Below Target |
|---|---|---|
| Portfolio processing volume vs forecast | ≥90% | Root cause analysis; location-level volume deep dive |
| Location count fully deployed | Per rollout plan | Negotiate revised timeline; offer deployment acceleration support |
| Portfolio refund rate | ≤2.5% | Flag high-refund locations; staff retraining at those sites |
| Portfolio chargeback rate | ≤0.3% | Location-level review; tighten authorization rules at flagged locations |
| Average uptime per location | ≥99.5% | Internet upgrade; terminal replacement; SLA escalation to vendor |
| HQ staff trained and independent | 100% | Additional ISO-led training session; extend support coverage |
| Menu change request volume | Decreasing | Review initial configuration completeness; update central template |
| Merchant NPS or satisfaction score | ≥7 / 10 | Location-level follow-up; dedicated support for below-target locations |
| ISO QBR delivered to HQ | Yes | Schedule immediately; bring data, not just updates |
How OrderPin Supports Multi-Location Onboarding
OrderPin is a white-label POS platform built for ISO and MSP partners — including those serving multi-location merchants. On the multi-location playbook: OrderPin’s platform supports centralized menu management, role-based permissions across locations, multi-location reporting dashboards, and white-label configuration that lets the ISO deliver the HQ dashboard under their own brand. The ISO can use OrderPin’s API to integrate the multi-location dashboard with the merchant’s existing back-office tools. Use this playbook to structure the onboarding sequence, and use OrderPin’s white-label configuration capabilities to deliver the brand experience the HQ decision-maker expects from day one.
Frequently Asked Questions
How do I handle locations in different states with different tax rules?
Tax configuration is handled as a location-level exception to the central menu template. The ISO configures the base menu template with a default tax rate, then layers state-specific tax rates on top of the locations that require them. OrderPin’s platform supports per-location tax rate configuration — the ISO should confirm this with the vendor during the AD13 configuration review and include it in the Pass/Fail checklist. Tax compliance across state lines is the merchant’s responsibility; the POS platform’s job is to enforce the tax rate the merchant’s accountant configures.
What if the merchant’s HQ decision-maker is not involved in the onboarding?
This is a red flag — and the ISO should address it before committing resources. A multi-location onboarding without HQ engagement is a collection of single-location onboardings with no central coordination, no portfolio-level reporting, and no train-the-trainer model. The ISO should insist on a named HQ sponsor (the person who approves the rollout plan, attends the 90-day QBR, and serves as the escalation path for multi-location issues) as a contract condition before signing. Without a HQ sponsor, the ISO is managing a relationship with a location manager who does not have authority to make decisions that affect the whole portfolio.
How does franchise royalty structure affect POS configuration?
Franchise merchants typically have a royalty structure that flows through the POS: franchise fee percentage, marketing fund contribution, and sometimes loyalty or gift card program fees. The ISO should understand the merchant’s royalty calculation method (percentage of gross sales, net sales, or transaction count) and confirm that the POS platform can generate the reports the franchise HQ needs to calculate royalties accurately. This is a configuration item that should be in the central template — not a per-location decision. Misconfigured royalty reporting is a franchise compliance issue, not just a POS configuration issue.
Should I charge differently for multi-location vs single-location onboarding?
Yes — and the multi-location onboarding fee should be separate from the per-merchant platform fee. The ISO should charge a project fee for the multi-location onboarding engagement: site survey, location-tiering analysis, central configuration, phased deployment management, HQ training, and the 90-day QBR. This project fee covers the ISO’s upfront time investment before the portfolio generates recurring revenue. The per-location monthly platform fee and processing margin revenue stream begins once each location is live. Use the TCO model from AD15 to ensure the onboarding project fee covers the ISO’s actual time investment — a 10-location rollout typically requires 40 to 80 hours of ISO time, not 10 hours.
How do I manage Tier C locations with poor internet connectivity?
Internet reliability at each location should be in the pre-signing site survey. Locations with unreliable internet should be flagged as Tier C and configured for offline-capable mode if the POS platform supports it — terminal stores transactions locally when connectivity is lost, syncs automatically when connection is restored, and flags transactions that require manual reconciliation. If the platform does not support offline mode, the ISO should recommend an internet upgrade as a condition of going live — and include the upgrade cost in the onboarding project scope. Locations with persistent connectivity issues should not go live until the issue is resolved; a failed go-live at a Tier C location creates disproportionate churn risk.
How does multi-location onboarding tie to AD14 and AD15?
AD14 covers the single-location onboarding playbook — Phase 1 of this article (pre-launch, go-live, 7-day stabilization, 30-day success criteria) is the AD14 playbook applied per location in a multi-location context. AD15 covers the ISO’s business-level TCO — the multi-location onboarding project fee should be calculated using the AD15 TCO framework to ensure the ISO recovers the 40 to 80 hours of upfront time investment. The 90-day QBR in Phase 6 is also the foundation for the customer success engagement that prevents churn — the ISO that delivers a data-driven 90-day QBR to the HQ decision-maker is demonstrating the strategic advisor role that justifies the merchant’s long-term loyalty.
Multi-location merchants are the highest-value segment in an ISO’s portfolio — and they require a fundamentally different onboarding approach than single-location merchants. The playbook in this article gives the ISO a six-phase framework: location-tiering before signing, centralized configuration before rollout, phased deployment with per-location validation, train-the-trainer training at scale, a centralized reporting dashboard for the HQ decision-maker, and the 90-day governance checklist that determines whether the account is stabilizing or concentrating risk. The ISO that executes this playbook consistently will win multi-location deals that ISOs without a playbook lose — and will retain those accounts at the 90-day QBR because the HQ decision-maker has the visibility they need to justify the investment to their own leadership. OrderPin, a white-label POS platform built for ISO and MSP partners, supports every phase of this playbook — from centralized configuration to multi-location reporting dashboards — under the ISO’s own brand.
About OrderPin
OrderPin is a white-label POS platform built for ISO and MSP partners. We offer full data ownership, flexible pricing, and seamless API integrations to help you build a recurring revenue business under your own brand. Learn more about OrderPin’s white-label solution
