Furniture retailers live in the gap between "a sofa on the showroom floor" and "the exact sofa in the customer's fabric, delivered and assembled six weeks later." A sofa isn't one SKU — it's a frame, a fabric grade, a leg finish, a cushion fill and a set of dimensions, each combination priced differently and lead-timed differently. Odoo core gives you product.template/product.product variants and attributes, sale orders, and inventory, but it runs out of road once you need showroom quotes that price a made-to-order configuration correctly, a delivery calendar that respects two-person vans and assembly crews, deposit-then-balance payment terms, and a single view of "where is my order" that spans supplier, warehouse, delivery and installation. Off-the-shelf apps.odoo.com modules cover fragments of this, but they don't model furniture retail as one connected flow, and they leave you stitching automations together by hand.

This package is a set of custom Odoo modules we design and build for your retail operation. At the data layer we extend the ORM with dedicated models (models.Model) — for example a furniture.configuration linking selected attributes to a computed price and lead time via @api.depends compute fields, and a furniture.delivery.slot model for capacity-bounded delivery windows. Product setup uses Odoo's attribute/variant engine plus configurator logic so a showroom quote reflects the real chosen combination rather than a flat SKU. Fulfillment is driven off the standard stock.picking and mrp/purchase flows where relevant, with furniture_status compute fields rolling supplier, warehouse and delivery state into one customer-facing stage. Access is governed properly through ir.model.access.csv and record rules so showroom staff, warehouse pickers and delivery coordinators each see the right scope. The UI ships as XML/OWL views — showroom quote screen, delivery planning calendar, and a fulfillment kanban — and customer-facing documents (order confirmation, delivery booking, assembly worksheet) are QWeb reports. Automated actions and scheduled jobs handle deposit reminders, delivery-day SMS/email triggers, and stale-order escalation, and everything is reachable over Odoo's XML-RPC/JSON-RPC API if you need to feed a website, marketplace or courier integration.

Because this is built to your scope, it fits how your stores actually operate rather than forcing you onto a generic template. We target Odoo 17.0, 18.0 or 19.0 and build against your edition — most workflows run on Community, while a few conveniences (native full studio-style customization, some accounting and field-service niceties) assume Enterprise; we confirm the Community-vs-Enterprise boundary during scoping so nothing is promised that your license can't deliver.

Delivery is build-to-order. After a short scoping call we agree the exact models, fields, views and reports, then build on a staging instance, run UAT with your team, and deploy to production with a rollback plan and a git repository handover. Typical delivery is 2 to 4 weeks from confirmed scope, depending on how much configuration logic, integration and data migration your operation needs. Pricing starts from $349 (indicative, single-company base scope); multi-company or multi-warehouse rollouts, courier/e-commerce integrations, deeper product-configurator logic, and large product/customer data migration volume increase the quoted scope. You get a firm fixed quote after the scoping call — never a surprise invoice.