Route every request to the right place — automatically
A standalone request-management app built around a real location hierarchy — region, site, building, floor, room — so every ticket is triaged, routed, and reported by where it actually happened.
The problem
A printer jam is on a specific floor. A dispatch belongs to a client site. An asset fault sits in a named data center. When your request tracker has no first-class concept of "where," you cannot triage by site, route work to the nearest team, or see which locations generate the most load — so location gets buried in free-text titles that nobody can filter or report on.
The solution
Generic Request Location gives every request a real, unlimited-depth location. Routing rules assign the right team and person the moment a request lands, dispatchers filter and group by site in one click, and bulk tools fix mis-routed requests across dozens of records at once — no ticketing ecosystem lock-in required.
Everything location-aware requests need
Every capability below is implemented in the module.
Unlimited-Depth Location Hierarchy
Build region > site > building > floor > room trees to any depth, with a computed full-path name shown throughout the app.
Location-Based Automatic Routing
Priority-gated routing rules match a request's location — and can cascade to its sub-locations — to auto-assign the accountable team and user.
Bulk Location Reassignment
Select any number of requests from the list or kanban and re-route them to a new location in one wizard, with a live summary of what changes.
Filter and Group by Location
Search, filter, and group requests by location from the standard list and kanban views, turning multi-site triage into a single click.
Teams With Covered Locations
Define teams with a leader, members, and the locations they cover, so ownership and routing scope are explicit, not tribal knowledge.
Live Request Counts Everywhere
Location and team forms show smart-button counts of open requests, so load hotspots are visible without building a single report.
Configurable Pipeline Stages
Drag-and-drop kanban stages with fold and closing-stage flags, editable from a simple configuration list — no code changes needed.
Priorities and Color-Coded Tags
Priority levels feed routing decisions, and color-coded tags keep requests consistently categorized across every team and site.
Standalone Operation
Runs on its own self-contained request model — no ticketing ecosystem or add-on stack required to get location-aware routing.
How it works
Map your locations
Build your region, site, building, floor, and room tree once, to whatever depth your organization needs.
Set routing rules
Define which team and person handle each location, with optional cascading to sub-locations and a minimum priority gate.
Requests auto-route
New requests are stamped with a location and immediately assigned to the matching team and assignee.
Triage and report by site
Filter, group, and bulk-update requests by location, with live counts on every location and team.
Frequently asked
No sales fog. If your question isn't here, email us and we'll answer it the same way.
No. Generic Request Location is fully self-contained — it ships its own request model, locations, teams, stages, and tags. You do not need to buy into any external helpdesk or ITSM ecosystem to use it.
Buy it on the Odoo App Store
Purchase, download and install directly from the official Odoo Apps Store — you'll always get the latest supported build.
Generic Request Location
Standalone request management with an unlimited-depth location hierarchy and location-based automatic routing — filter, group and bulk-reassign requests by site.
Buy on Odoo App Store