Project Scope¶
About this document
Definition of what the NestPOS implementation delivers, what it excludes, and the assumptions and constraints that frame the engagement.
| Field | Value |
|---|---|
| Project | NestPOS Implementation |
| Platform | Odoo 17 Community + custom add-ons |
| Document version | 1.0 |
| Date | 27 July 2026 |
| Prepared by | Systems / Development |
| Status | For approval |
Scope is defined from the deployed module inventory. Items marked as inferred should be confirmed with the project sponsor before sign-off.
1. Purpose & Objectives¶
This document defines the scope of the NestPOS implementation: the business functions to be delivered on Odoo 17, the boundaries of that delivery, and the assumptions, constraints, and dependencies that apply.
The objective is to stand up a single, multi-branch platform that unifies point-of-sale, inventory, purchasing, accounting, HR, payroll, and employee financing, with local payment collection and consistent branded reporting.
Key objectives
- Run point-of-sale across multiple branches from one Odoo database.
- Keep inventory, sales, and finance continuously reconciled.
- Manage the full HR and payroll lifecycle, including loans and salary advances.
- Enforce spend controls through multi-level purchase approvals.
- Collect payments locally via the Selcom gateway.
- Deliver dashboards and exportable reports to management.
2. In Scope¶
The following functional areas are in scope and are backed by modules already deployed on the instance.
| Area | Deliverable | Basis |
|---|---|---|
| Point of Sale | Multi-branch POS with stock-availability enforcement | pos_multi_branch, pos_stock_restrict |
| Sales | Sales order management with customised workflow and a sales dashboard | sales_order_override, sales_dashboard |
| Inventory | Stock management, valuation reporting, inventory dashboard | stock_dashboard, inventory_valuation_report |
| Purchasing | Purchase orders with multi-level approval | purchase_multi_approval |
| Accounting & Finance | Accounting kit, dynamic financial reports, budgeting, partner statements, invoice reminders | base_accounting_kit, dynamic_accounts_report, base_account_budget, direct_budget_management, partner_statement, thalia_invoice_reminders |
| HR | Employee lifecycle: onboarding, transfers, resignation, documents, rewards/warnings, reminders, leave, HR dashboard | ohrms_core, hrms_dashboard, hr_* / oh_* suite |
| Payroll | Payroll processing with accounting posting and local customisation | hr_payroll_community, hr_payroll_account_community, payroll_custom_module |
| Loans & Advances | Loan management, employee loans with accounting, salary advances | advanced_loan_management, ohrms_loan, ohrms_loan_accounting, ohrms_salary_advance |
| Payments | Selcom payment gateway integration; portal paywall / access control | codenest_selcom_payment, codenest_portal_paywall |
| Multi-branch / company | Branch- and company-scoped data and operations | multi_branch_base, hr_multi_company |
| Reporting | Excel export engine and management dashboards | report_xlsx, report_xlsx_helper, thalia_mgmt_dashboard_v17 |
| Branding | Product branding, back-office theme, themed report layouts | nesterp_branding, mtewele_web_theme, mtewele_report_theme |
| Staff services | Customised lunch / canteen management | lunch_custom_module |
3. Out of Scope¶
The following are out of scope for the current phase — no corresponding module is deployed. They can be added later as separate change requests.
Inferred exclusions
This list is inferred from the absence of the relevant modules in the current build and should be confirmed against the signed requirements.
| Excluded area | Reason |
|---|---|
| Manufacturing / MRP | No manufacturing modules deployed |
| eCommerce / public website & online shop | No website/eCommerce modules deployed |
| CRM & marketing automation | Not part of the current module set |
| Project management / timesheets | No project modules deployed |
| Field service / repairs / fleet | Not deployed |
| Payment gateways other than Selcom | Only the Selcom integration is in scope |
| Data migration from legacy systems | To be confirmed — not implied by the module set |
| Third-party integrations (e.g. e-fiscal, banks, BI tools) | None present unless separately specified |
| Custom mobile applications | Access is via the standard Odoo web/PoS client |
4. Deliverables¶
| Deliverable | Description |
|---|---|
| Configured Odoo 17 instance | NestPOS running on the hosted environment with all in-scope modules installed and configured |
| Branch & company setup | Branches, companies, users, and access rules configured |
| Chart of accounts & finance setup | Accounting, budgets, and reporting configured |
| Payroll setup | Salary structures, rules, and payroll-to-accounting mapping |
| Selcom payment integration | Live payment collection through Selcom |
| Reports & dashboards | Operational dashboards and Excel/printed report templates |
| Documentation | Product Documentation, Project Scope (this document), Project Timeline |
| Training & handover | Admin and end-user enablement (to be confirmed) |
5. Assumptions¶
- Odoo 17 Community is the target version; add-ons remain compatible with it.
- Hosting is provided on the existing containerised environment (Docker + CapRover on the Contabo VPS).
- The deployed add-on inventory represents the agreed functional footprint.
- Business processes can be accommodated by the configured modules with limited customisation.
- Required master data (products, employees, partners, accounts) will be provided by the client in a usable format.
- Selcom merchant credentials and API access are available for the payment integration.
6. Constraints¶
- Functionality is bounded by the deployed modules; anything beyond Section 2 is a change request.
- Community-edition limits apply — Odoo Enterprise-only features are not available.
- Customisations must remain upgrade-safe against the Odoo 17 base.
- Performance is bounded by the capacity of the single hosting VPS.
- Payment collection is limited to the Selcom gateway.
7. Dependencies¶
| Dependency | Owner |
|---|---|
| Selcom merchant account & API credentials | Client / Selcom |
| Master data (COA, products, employees, partners) | Client |
| Hosting environment & access | Systems / Hosting provider |
| Business process sign-off per module | Client / Project sponsor |
| User acceptance testing participation | Client |
8. Stakeholders¶
Note
Confirm names and contacts before sign-off.
| Role | Responsibility |
|---|---|
| Project sponsor | Approves scope, budget, and go-live |
| Project manager | Coordinates delivery and timeline |
| System administrator / developer | Deployment, configuration, custom modules |
| Finance lead | Accounting, budgeting, reporting sign-off |
| HR / Payroll lead | HR, payroll, and loans sign-off |
| Branch / operations leads | POS, sales, and inventory sign-off |
9. Acceptance Criteria¶
- All in-scope modules are installed, configured, and demonstrably functional in the production environment.
- POS operates per branch with stock enforcement, and sales post to accounting.
- Payroll runs end-to-end and posts to the ledger; loans and advances recover correctly.
- Purchase approvals enforce the agreed authorisation tiers.
- Selcom payments are collected and reconciled successfully.
- Dashboards and reports produce accurate figures against source data.
- The three project documents are reviewed and approved.