A note before you read
This Product Requirements Document (PRD) is a living document. We’re sharing it early with you so you can see where we’re headed and help shape it with your feedback. Nothing here is set in stone, and it shouldn’t be read as a firm commitment on features or timelines.
Your input will make the end result better , thanks for being part of the process!
- Martin
1. Problem Statement
Customers often have a registered legal name that differs from their trading or display name.
Current invoices and customer-facing documents only reflect the display name.
This creates audit and compliance risks, since legal documentation must reference the registered entity name.
At the same time, project managers need the display name for usability in day-to-day workflows.
2. Goals & Objectives
Provide support for a Legal name attribute on customers.
Ensure all invoices, PDFs, customer documents and API’s correctly display the legal name where required.
Maintain the existing display name for user workflows and internal navigation.
Enable seamless rollout of this capability across all Qondor modules without disrupting users.
3. Scope
Functional Requirements
Customer Record Enhancement
Add a dedicated Legal name field on the customer card.
Field is optional; defaults to existing name if left empty.
Invoice & Document Updates
If a legal name is present, it replaces the display name on:
Customer offer invoices
Customer form invoices
All PDFs generated for customers
Search & Usability
Legal name is fully searchable across Qondor (Customer List, Quick Search).
Display name remains available for fast recognition.
Merge Tag Support
New merge tag:
customer.legalName.Falls back to display name when legal name is not set.
Supported across all merge menus (e.g. email templates, invoices).
API & Integration Updates
Add
legalNameto all Customer API endpoints (GET/POST/PUT).Ensure CustomerView exposes
legalName.Legal name included in Excel import/export workflows.