ReturnMate logoReturnMate
Multi-store

Run multi-store returns from a single dashboard.

One admin, many stores. A master warehouse and its retail spokes share RMAs, transfers, staff, and reports — without data leaking between tenants and without pretending every store is the same.

app.returnmate.io
RMA list with location and assignment columns
§ 01

Hub-and-spoke with proper isolation

Nominate a master hub (typically the central warehouse) and link retail stores to it. Each store keeps its own Shopify connection, branding, and customer portal — but RMAs, transfers, and reporting flow centrally.

  • Master hub receives all return labels by default
  • Retail stores can accept drop-off with automatic transfer to master
  • Separate Shopify install per store — compliant with Shopify multi-location
  • Location-specific branding for the customer portal on each store
§ 02

Eight transfer reasons, full audit

Inter-store transfers aren't a special case — they're a first-class record with 8 built-in reasons (parts unavailable, specialist repair, supplier return, DG handling, no local stock, customer dispute, complex diagnosis, customer pickup). Every transfer shows on the originating and receiving RMA timelines with the reason code logged.

  • Generate transfer labels with the same carrier integrations as customer returns
  • Tracking events flow to the transfer record, not just the parent RMA
  • Receiving a transferred parcel auto-resolves the source transfer
  • Transfer reports by reason, by store, by month
§ 03

Staff access scoped to location

A warehouse receiver in store A can't accidentally approve an RMA from store B. Managers and admins can be given cross-store access explicitly. Role-based access control operates at the individual user level with per-location grants.

  • Roles: Admin, Manager, Ops, Support + custom
  • Per-user, per-location access grants
  • Audit trail shows which location a staff member acted from
  • Support users can see only the queue for their assigned location
§ 04

Centralised reporting without losing location detail

All the dashboards that work for a single-store operator work across stores too — with a location dimension to slice on. Compare stores side-by-side, roll up by region, or drill into a single retail floor.

  • Group-by location on every analytics view
  • Compare stores on SLA, cost-per-return, write-off rate
  • Cross-store customer pickup with transfer auto-generation
  • One invoice across your group (via Shopify enterprise billing)
FAQ

Questions about multi-store operations.

Do I need separate ReturnMate subscriptions per store?

Enterprise customers get multi-brand consolidation under one subscription. Ops and Scale plans are per-store; Scale supports up to 10 locations and Ops supports 2.

Can customers drop returns at any retail location?

Yes. Configure any retail store as a drop-off location. Customers pick one at portal submission; the parcel is received there and automatically transferred to the master hub (or specialist repair location) based on the RMA's workflow.

Does location access control apply to analytics?

Yes. A support user scoped to store A sees only store A's analytics. A cross-store manager sees the roll-up. Data isolation is enforced at the query level, not the UI.

Get operational control — before it costs you more.

14-day free trial. No credit card required. Billed through Shopify.