Extensions & Customisation
How to extend ERP and CRM platforms safely — avoiding upgrade lock-in while delivering business-specific functionality.
Extend Without Locking In
The most common ERP/CRM failure mode is over-customisation of the core: deeply modified code that makes every upgrade a project. Clavon's extension philosophy separates what belongs inside the platform from what belongs outside — keeping the core clean and the business logic portable.
ScopeWhat Extension Work Covers
Differentiate between configuration (standard functionality), extension (external services, APIs, workflows) and customisation (core modifications)
Define patterns for building extensions: side-by-side services, platform APIs, micro-frontends
Show how to implement user interfaces, business logic and reporting outside of the core to avoid upgrade lock-in
Provide version control and deployment strategies for extensions
Outline testing and validation practices for extended systems
Layered Extension Pattern
The separation of Configuration, Extension, and Customisation — and why it matters for upgrade safety.
Extension Patterns
Side-by-Side Services
Domain services deployed externally, integrated via API
Platform APIs
Vendor-published APIs for extending functionality safely
Micro-Frontends
Custom UI surfaces embedded in the core platform shell
Testing & Governance
Contract Testing
Verify extension interfaces do not break on platform updates
Regression Testing
Validate core functionality after extension deployment
Version Control
Branch strategy for extensions aligned to platform release cycles
Deliverables
Extension strategy document and architecture patterns
Change impact assessment template
Testing and deployment workflows for extensions