A Business requirement (BR) is the expression of a business need by a customer or internal project user.
A BR contains multiple different parts to explain the stakeholder need and how to meet his/her requirements:
- Customer Story: this is the requirement as expressed by the customer
- Scenario: How/where the current solution can provide a suitable scenario to answer the customer story
- Gap: For the uncovered part of the scenario, elaborate the gap/need for specific developments/setup
- Test case: A set of conditions under which a tester will determine whether the application, software system or one of its features is working as it was originally established for it to do.
- Deliverables to be provided to the customer/user
- Resources necessary to achieve the deliverables
- Additional information (approval, cost control etc.)
This set of modules was originally designed for the service/IT industry but the requirement management design has been kept as generic as possible so that it can apply to many other cases/industries (customer or internal projects):
- Construction
- Trading (New product development)
- Business Consultancy
- Web or IT development
- R&D projects
- etc.
More information about business requirements management:
- Wikipedia
- Six Sigma
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Track customer business requirements from the first story to approval, with scenarios, gaps, test cases and a portal page where customers can follow progress.
This module adds a Business Requirement area to Odoo for recording what a customer or internal stakeholder needs, and how the team plans to answer it.
Each requirement is a single record with a numbered reference and a short description. It holds the customer story, the scenario, the gap, the test case and terms and conditions, plus a stakeholder, a responsible person, reviewers, a priority and categories.
A status bar moves the requirement through Draft, Confirmed, Approved, In progress, Done, Cancel and Drop. Only managers can move a record to Approved, In progress or Done; other users get an error. Confirming or approving automatically records who did it and when, and going back to Draft clears those dates. A kanban view groups requirements by stage, and list, form, graph and pivot views are available.
Requirements can be published to the customer portal with a button on the form. Customers then see their own published requirements under My Account, can read the details and download a PDF Business Requirement Document. A chatter keeps the discussion history.
Categories are managed under Configuration, where you can also reach product templates. Access is controlled by Business Requirement User and Business Requirement Manager groups, and portal users can only read their own published records.
Depends on
Required by other modules
Menus it adds
Models and fields (2)
- business.requirement · new modelgap, date, name, state, origin (Source), user_id (Owner), priority, scenario, sequence, test_case, company_id (Company), partner_id (Stakeholder), approved_id (Approved by), description, category_ids (Categories), kanban_state, reviewer_ids (Reviewers), approval_date, change_request (Change Request?), to_be_reviewed, portal_published (In Portal), confirmation_date, confirmed_user_id (Confirmed by), requested_user_id (Requested by), responsible_user_id (Responsible), business_requirement (Customer Story), terms_and_conditions
- business.requirement.category · new modelname, parent_id (Parent Category)
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. The module is very large and only part of the code was read. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 6 confirmed, 3 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/business-requirement.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.