Customer References
by Space City Software L.L.C. https://spacecitysoftware.com/customer_references$ 99.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Discuss (mail) • Calendar (calendar) • Contacts (contacts) |
| Lines of code | 708 |
| Technical Name |
customer_references |
| License | OPL-1 |
| Website | https://spacecitysoftware.com/customer_references |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Discuss (mail) • Calendar (calendar) • Contacts (contacts) |
| Lines of code | 708 |
| Technical Name |
customer_references |
| License | OPL-1 |
| Website | https://spacecitysoftware.com/customer_references |
Customer References
Track referenceable customers, cap reference fatigue, and match
references to deals from your existing Odoo CRM.
A self-hosted reference-management alternative for
companies already on Odoo.
Stop paying per seat for reference management
A reference manager that lives inside the CRM you already pay for.
Reference-management SaaS - ReferenceEdge, SlapFive, Influitive - is typically priced per sales seat on annual contracts, starting in the low-hundreds-per-seat range and climbing into the tens of thousands per year for a full team. Most of what they do overlaps with what your Odoo CRM already tracks - partners, leads, opportunities, and the relationships between them.
This module turns Odoo into the system of record for every
referenceable customer. One-time purchase of $99 on the App
Store. Per-reference fatigue caps, approval workflow with
audit trail, customer-facing opt-out portal at
/my/references. No subscription, no per-seat
fee, no new tool to context-switch into.
Stop letting your best customers burn out
One reference per quarter, tracked in Odoo, opt-out on file.
Every B2B sales team eventually needs a reference call to close a deal. Without a system, your best customers get over-tapped and politely stop responding. Without a paper trail, you can't prove to compliance that the customer consented to be a reference in the first place.
This module turns Odoo into the system of record for every
referenceable customer. Per-reference fatigue caps. Approval
workflow with audit trail. Customer-facing opt-out portal at
/my/references. One-time purchase, lives inside
your existing CRM.
Backend reference profile
Products, use cases, geographic scope, fatigue cap, expiration.
Features
Per-reference fatigue cap
Each reference carries a
fatigue_cap_per_quarter field. Approving a
request automatically checks the count of approved uses in
the current calendar quarter and blocks the (cap + 1)-th
approval with a clear cooldown-remaining message. Real
differentiator vs. naive reference-tracking modules.
Approval workflow with audit trail
Sales reps create draft requests pointing at a reference and
a crm.lead. A manager approves or denies; the
decision stamps decided_at + approver_id. Approval
auto-creates a customer.reference.use row
tying the reference to the lead as audit evidence.
Customer-facing opt-out portal
Logged-in customers visit /my/references to see
which deals their company is on the reference list for and
opt out per row. Authorization is gated by partner
ownership (matched against the user's partner OR its
commercial parent for child contacts).
Restrict-on-delete on use history
The customer.reference.use rows are audit
evidence and outlive the references they point to.
References can't be silently destroyed without re-assigning
their use history first.
Geographic scope & metadata
Each reference carries free-text products, use cases, and a geographic scope (North America / Europe / LatAm / APAC / MEA / Global) for ad-hoc matching during a deal. Future versions may layer automated matching on top - for now this is the substrate.
Multi-company isolation
Per-company ir.rule records on every model
- references, requests, and use history. Tested for
cross-tenant isolation.
GDPR-ready
One-click forget action wipes free-text PII fields (products, use cases, internal notes) and marks the reference inactive while preserving the use-history audit trail intact.
Crm.lead integration
Use rows and requests both link directly to
crm.lead records, so a reference's history
rolls up against the deals it touched. Standard Odoo CRM
report views see this through related fields.
Approve a request in one click
Find a reference without leaving the deal
The Customer References tab on every crm.lead surfaces active, uncapped references inline. One click to send a request.
Customer opt-out portal
Customers see which deals they're listed on and opt out per row.
Why teams pick this over a separate SaaS
- Lives in your CRM. References sit alongside leads, opportunities, and partners. No new tool to context-switch into.
- One-time purchase. Pay once on the Odoo App Store. No recurring fees.
- Real fatigue protection. The per-quarter cap is server-side, not a UI guideline. Approving past the cap raises an error.
- Customer consent on file. Customer-facing opt-out portal gives you defensible evidence the customer chose to be a reference.
- Audit-evidence use history. Restrict-on-delete on use rows; GDPR forget wipes PII while keeping history.
- Multi-company from day one. Run separate reference programs per Odoo company in a multi-tenant install.
- Compatible with Odoo 18 Community and Enterprise. Standard CRM only; no Enterprise-only modules required.
- No external services. No third-party APIs, no recurring fees.
Requirements
Odoo 18 (Community or Enterprise) with the crm,
portal, and mail modules installed.
No external API keys, no third-party services, no recurring fees beyond the one-time App Store purchase.
More from Space City Software
Other Odoo apps that pair well with Customer References
Trust Center
Customer-facing security posture: compliance frameworks,
NDA-gated documents, and access-request workflow on
/trust.
Policy Acknowledgement
Versioned policy library, mass-acknowledge campaigns, and tamper-evident audit trail for SOC 2 and ISO 27001 evidence.
Roadmap Portal
Public roadmap with upvoting and an auto-published changelog on your Odoo Website. Email subscribers, double-opt-in.
Support
Bug reports and configuration questions are handled by the author within 14 days. Use the "Contact Author" button at the top of this page or reach out via email.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module