Skip to main content

Multi-location setup

Running Trustaroo across several branches raises three questions: what to call each location, whether every branch gets its own review destination, and how to tell which branch is doing well. This page answers all three. Read it before you print anything, because the naming decision is the expensive one to reverse.

Before you start​

The free plan allows two active locations. Beyond that you need Premium; see Free plan location limit.

Extra locations requires Trustaroo Premium

This is part of Trustaroo Premium. Upgrade from Account and billing in the app to switch it on.

Name locations once, properly​

Location names appear in the Reviews table, in the location filter, in your printed material and, if you switch it on, in the sentence on your public review page. Pick a pattern and use it everywhere.

  • Use the shortest unique identifier. Kerkstraat, Airport, Van 2. Staff already talk this way.
  • Add the city only when you need it. Utrecht - Central and Rotterdam - Central are worth spelling out; Kerkstraat alone is not, if you only have one.
  • Use one separator. Pick City - Site and stick to it, so the list sorts and reads cleanly.
  • Keep it customer-safe. With Show location name to customers on, the name lands in the question "How was your experience with Café Noord - Kerkstraat?". Internal codes such as NL-003 look wrong there.
  • Avoid dates, campaigns and staff names. Locations outlive all three.
Rename rather than replace

Renaming a location keeps its history and keeps every printed QR code valid, because the short link is not derived from the name. Archiving and re-adding starts the numbers from zero and forces a reprint. See Edit and archive locations.

This is the decision that matters most, and it follows your Google listings rather than your preference.

Use one shared review page when your business has a single Google Business Profile, or when you collect on Trustpilot, which reviews the company rather than the site. Leave Review page URL empty on every location and they all inherit the default from Location Defaults. You still get separate scan and rating numbers per branch, feeding one public profile.

Use one review page per branch when each branch has its own verified Google Business Profile. Then each branch's reviews should land on its own listing, because that is what local customers see when they search. Set Review page URL in each location's own dialog and it overrides the default for that branch only. See Per-location overrides.

Sending branch reviews to the wrong listing is hard to undo

Reviews belong to the Google profile they were written on, and you cannot move them afterwards. If your branches have their own listings, set the per-location URLs before you distribute any QR codes.

Keep the review filter and the threshold identical across branches unless the service is genuinely different. Two branches with different thresholds convert ratings into referrals at different rates by configuration, which makes any comparison between them meaningless. See Choosing your star threshold.

Compare your branches​

Trustaroo gives you branch-level numbers in two places, and they answer different questions.

  • The Locations panel shows a per-location settings summary that includes how many reviews that location has collected. It is the fastest way to see which branches are actually producing, and to spot a branch stuck at zero, which almost always means the printed material never went out.
  • The Reviews screen has Filter by location, so you can read one branch's ratings and written feedback on their own, then switch back to All locations. See Browse and filter reviews.

The Dashboard reports on your account as a whole, over 30 days, 3 months or 9 months. Use it for the trend across the business and use the two views above for the branch-by-branch picture. See Track progress over time.

Compare rates, not totals

A branch with twice the footfall should have twice the scans. What tells you something is the share of scans that turn into referrals and the shape of the ratings, not the raw count. Rating distribution is the view to use.

A workable rollout order​

  1. Create every location and name it with your chosen pattern.
  2. Set each branch's Review page URL, or confirm they should all inherit the default.
  3. Test one link per branch end to end, high rating and low rating.
  4. Download the printable PDF per branch and label the back of each sheet with the location name, so nobody puts Rotterdam's code on Utrecht's counter.
  5. Brief staff once, per site, on the one sentence they should say.
  6. Check the Locations panel a week later and chase any branch still at zero.