Pre-Build Odoo Checklist That Determines How Much Custom Code You Write

A practical requirements-gathering checklist for Odoo ERP projects argues that the discovery phase directly determines how many custom modules a team will maintain for years. The guide recommends mapping a client's core business terms to existing Odoo models early, since mismatches can silently balloon into costly new modules if left unresolved. Developers are advised to collect precise transaction volumes — such as daily orders and concurrent users — rather than vague descriptors like 'high volume,' as these numbers drive infrastructure and UI decisions that are expensive to reverse. Every document that leaves the business, from invoices to EDI payloads, should be collected as actual files rather than descriptions, since formatting details and legal requirements rarely surface until user-acceptance testing. The checklist also flags numbering sequences and peak-period loads as critical early inputs, emphasising that systems should be designed for worst-case months, not average ones.