Several licenses, one counter
Each license is its own tenant with its own team, jobs and FastBound connection. Move an item between them and it is one tracked transfer, not two things somebody has to remember to write down.
Point by point.
- A license is a tenant
- Its own users, its own work orders, its own FastBound account. Administrators switch between them; the data never mixes.
- One work order, several licenses
- A customer brings three firearms to one location and two of them need work done at another. One work order, items moving independently, one conversation at pickup.
- Transfers that hold their state
- A transfer is a tracked thing with a status, not a note someone wrote. You can see what is in flight and what has landed.
- Roles scoped per license
- Someone can be a technician at one location and nothing at all at another.
- Money by license
- Internal cost against customer charge, per license, so reconciliation between locations is arithmetic rather than archaeology.
How it actually works.
The decisions that matter once you are using it every day rather than looking at it on a slide.
Isolation is enforced per request
Every operation that takes a record id checks that record belongs to a license the caller can see. Record ids are printed on tags as DataMatrix codes, so knowing an id is normal and is never treated as permission.
Both books, or neither
An inter-license transfer writes the disposition and the acquisition as one workflow with retry, rather than leaving one side written and the other not.
Audit trail across all of them
Who did what, on which license, when — in one trail rather than one per location.
Come and see it
on a real counter.
Thirty minutes, screen shared, your questions. If BenchMaster is wrong for your shop you will know inside the first ten minutes, and we will both have saved a week.
Talk to the people who use it every day