You check your feedback dashboard and the average rating sits at 3.8. Fine, right? Not great, but not a crisis. Then you break it out by location and the picture changes: four shops at 4.6, one shop at 2.4. That 2.4 has been dragging down the number for weeks, and you had no idea which location it was coming from.
That's what happens when you collect feedback without tagging it to a place.
The problem with aggregated feedback
When feedback comes in from multiple locations and all of it lands in the same bucket, you're averaging together two different situations. A complaint about parking at one address gets combined with a compliment about the staff at another. Trends get blurred. You end up looking at a number that doesn't describe any single place you actually operate.
This isn't just a scale problem. Even two locations are enough to hide the signal. One high performer and one struggling shop can average into "good enough" when the reality is that one of them needs attention right now.
How locations work in Feedbaxster
In Feedbaxster, a location is a named record that you attach to one or more QR codes. When a customer scans a QR code and submits feedback, that submission is tagged with whichever location the QR code belongs to. No action required from the customer. The attribution is automatic, because it lives in the QR code.
To set it up, go to the Locations section in your dashboard sidebar and add each physical address or branch as its own location. Give it a name you'll recognize in filters ("Downtown," "Airport Kiosk," "Westside"). Then go to QR Codes and assign each code to the right location. That's the whole setup.
Once a location is assigned, every scan from that code is tagged automatically. If you rename the location later, all past submissions stay attributed correctly.
A worked example
Two coffee shops, one owner. Both have QR codes on the counter. The owner set up the locations in week one, assigned each code, and moved on.
Six weeks later, the suggestions feed shows a pattern: three complaints about slow service, two about cold drinks. All from the same location. The other shop has nothing like it. Without location tagging, those five complaints would be spread across a combined feed with no geographic signal. The owner would see the complaints, but connecting them to a single location would require reading each one and guessing. With location tagging, the filter is one click.
The owner adjusts staffing at the slow shop and adds a note to the morning checklist about drink temps. Two weeks later, the complaints stop.
What you see on the dashboard once locations exist
When you have at least two locations, a few things change:
The Overview page shows a location engagement map. Each location appears as a marker, sized by feedback volume, with a popup showing suggestion count, issue count, and positive-response percentage. If your locations have coordinates set, they plot on a real map. If not, they appear as a card grid instead. Either way, you get a single view that shows which shops are active and which are quiet.
In the Suggestions and Issues sections, a location filter appears at the top of the feed. You can scope the entire feed to a single location to review it in context, then switch to the next.
Analytics also picks up the location data, so date-range trends can be broken out per location once you have enough volume.
If you want sub-location detail: shift labels
Some businesses need one more level of attribution beyond physical location. A shop with a morning crew and an afternoon crew might get complaints that cluster by shift, not by address. Both crews work at the same location, so location tagging alone doesn't help.
Feedbaxster handles this with shift labels. You configure named shifts in your business settings (for example, "AM" and "PM" with the hours each covers), and the system automatically tags each submission with the matching shift name based on the time it was submitted. You don't need separate QR codes for each shift.
Shift labels show up in the submissions data alongside the location, so you can ask "which location, and which shift?" at the same time.
Get started
Go to the Locations section in your dashboard sidebar and add your first location. Then open QR Codes, find any code that is currently unassigned, and link it to that location. Repeat for your other locations.
From that point on, every scan is attributed. The dashboard will start sorting your feedback by place, and the patterns that were hidden in the aggregate will become readable.