The recommendation
Don’t fight the frontend. Decouple it.
Odoo can remain the source of truth for products, categories, customer data, pricing, and operations. The public site can be purpose-built for SEO, content, speed, conversion, and brand presentation.
Build plan
Demo-ready phases
Frontend layer
Custom PHP/CodyHouse website with full control over URLs, page structure, schema, internal links, design, and conversion paths.
Catalog/API layer
A reusable PHP OOP class fetches or syncs Odoo categories, products, images, specs, and optional pricing into local display models.
SEO content layer
Application and product landing pages combine editorial content, comparison blocks, FAQs, schema, and product cards.
Conversion layer
Quote requests, drawing/file uploads, engineering questions, lead routing, and Odoo handoff can be controlled by the custom frontend.
Sales pitch
This path gives Framing Tech maximum control without operational disruption.
It lets the website become a growth engine while Odoo continues to do what it is good at: ERP, catalog management, and business operations.
Application and product family pages can be structured around search demand.
Pages can sell outcomes, use cases, and engineering support before showing SKUs.
A PHP OOP integration layer can be extended over time as scope grows.
No need to force Odoo’s website builder to do a job it was not designed to do well.
Demo value
This is the strategic story to show Anthony and the team.
We are not proposing a prettier website only. We are proposing a controlled growth layer that connects content, SEO, catalog data, quote generation, and Odoo operations.