Project profile
Scope, role and technology
Visual evidence
Odoo configuration, product/customer records, invoicing and operational screens, together with integration evidence showing how the local ERP participates in BEMAR COLOR workflows.
Why Odoo was introduced
The objective was to move business operations away from disconnected manual tracking and toward a central operational system for customers, products, invoices, inventory, and order-related information.
Operational configuration
- Customer and product records.
- Invoicing and sales-related information.
- Inventory and operational tracking.
- Order/process information needed by staff.
Automation-ready integration layer
Odoo remains the operational system of record while Chatwoot/n8n customer-service workflows can read or structure information before an ERP action. The environments are separated: Chatwoot and n8n run on Hetzner; Odoo runs locally at BEMAR COLOR.
Local deployment and data layer
Odoo runs locally at BEMAR COLOR on Linux with PostgreSQL. It is not hosted on the Hetzner server. Integrations connect the Hetzner automation layer to the local ERP only where the business workflow requires it.
Architecture
Engineering perspective
- Avoid duplicating records across disconnected tools when an integration is possible.
- Validate required fields before automated writes.
- Keep people in control of business-critical changes while reducing repetitive navigation and data entry.