Overview
RepeatMD supports multi-location practices in two configurations: one app with multiple locations (recommended for most groups) or one app per location. The choice affects patient accounts, payments, reporting, branding, and how updates roll out across locations.
This article is for practice owners and onboarding leads deciding how to structure a multi-location deployment. Final setup is configured with your Customer Experience Manager (CEM) during onboarding — you cannot switch models freely after launch.
Before You Start
This decision is made at launch. Changing models later is limited (see How It Works).
Consult your CEM before committing if you are unsure.
Know whether patients cross between locations frequently and whether branding is uniform or location-specific.
Confirm how each location handles bank accounts and payouts — especially if locations have separate ownership.
Why It Matters
The multi-location model you choose affects daily operations for years:
Patient experience — one sign-up vs. separate accounts per location.
Payment routing — centralized vs. per-app Stripe Connect accounts.
Reporting — unified filters vs. isolated data per app.
Admin workload — bulk updates across locations vs. logging into each portal separately.
Choosing the wrong model creates costly migration work and patient confusion.
How It Works
One app with multiple locations (recommended)
Best for practices with little to no patient crossover between locations and uniform branding across the group.
Area | Behavior |
Admin management | Manage all locations in one Admin Panel. Apply updates to one, several, or all locations at once. |
Reporting | Unified reporting with filters by location. |
Payments | In-app purchases route to the patient’s home location by default. Patients can select a purchasing location at checkout when enabled. |
Redemption | Patients can redeem purchases at any location, regardless of where they bought. Reconciliation reporting supports cross-location redemption. |
Patient accounts | Patients sign up once and use one app across all locations they visit. |
Branding | Branding settings are shared across locations. |
One app per location
Best for practices where patients frequently visit multiple locations, or locations have distinct branding or separate ownership.
Area | Behavior |
Admin management | Each location’s app is managed separately. Updates cannot apply to multiple locations at once. |
Admin access | Staff log into each location’s Admin Panel individually. |
Reporting | No unified reporting across locations. |
Payments | In-app purchases pay out to the bank account linked to each app. |
Redemption | Patients redeem treatments only at the location where they purchased. |
Patient accounts | Patients create a separate account for each location they visit. |
Branding | Each app can have unique branding and marketing materials. |
Switching after launch
Separate apps → one app: Possible, but the consolidation is complex and disruptive for your business and patients. Plan carefully with your CEM.
One app → separate apps: Not supported. This setup cannot be reversed later.
Step-by-Step Instructions
Evaluate which model fits your practice
List your locations and note whether patients typically visit more than one.
Confirm whether branding is shared or location-specific.
Confirm whether bank accounts and legal entities are shared or separate per location.
Review the comparison tables in How It Works with your leadership team.
Schedule time with your CEM before launch to confirm the model and configure locations.
Document the decision for your internal team so admins know whether to expect one portal or multiple.
Best Practices and Pro Tips
Default to one app with multiple locations unless you have a clear reason for separate apps (heavy crossover, distinct brands, or separate ownership).
Decide before go-live. Reversing a one-app setup is not possible; consolidating separate apps is painful.
Align Stripe setup with your model. One platform typically uses one Stripe Connect account by default; separate apps may need separate Connect accounts. See Set up your Stripe account (Admin Panel).
Train staff on redemption rules so front desk knows whether cross-location redemption applies.
Use location filters in reports when running a unified app so each site can review its own metrics.
Common Mistakes and FAQs
Q: Can I switch from one app to separate apps later?
A: No. If you launch with one app for all locations, you cannot split into separate apps later.
Q: Can I consolidate separate apps into one app later?
A: Yes, but the transition is complex and disruptive. Consult your CEM before launch to avoid migration.
Q: Do patients need separate accounts if they visit two locations?
A: One app model: No — one account across locations. Separate apps model: Yes — a new account per location.
Q: Where do in-app purchase payouts go in a multi-location app?
A: Typically to the patient’s home location’s connected payout account, with checkout location selection affecting routing when enabled. Confirm details with your CEM for your account structure.
Q: Can patients redeem a treatment bought at Location A at Location B?
A: One app model: Yes, at any location (with reconciliation reporting). Separate apps model: No — redemption stays at the purchase location.
Q: Who configures locations in the Admin Panel?
A: Locations are reviewed during onboarding Setup (Confirm Location Information) and managed with your CEM. See Complete your RepeatMD onboarding (Admin Panel).
Next Steps and Support
Complete your RepeatMD onboarding (Admin Panel) — location confirmation during Setup
Location selection at checkout — patient checkout behavior
Need help? Email support@repeatmd.com