Cosmetics retail lives and dies on SKU granularity. A single lipstick line becomes forty shades, each with its own barcode, price, cost, and batch; foundations carry undertone and coverage attributes; skincare carries expiry dates that must never be sold past. A stock Odoo install gives you product.template with variants and a working POS, but out of the box it does not encode the beauty-specific reality: shade-level attributes that generate clean product.product combinations, per-batch expiry surfaced at the register, tester and sample units that move stock without revenue, or a loyalty scheme that rewards repeat buyers of consumable products. Teams end up hand-configuring hundreds of variants, disabling expiry warnings, and running promotions in spreadsheets — which is where margin quietly leaks.

This is a made-to-order retail configuration app that ECOSIRE builds for your specific catalog and store operations. We model the cosmetics domain properly: product.attribute sets for shade, finish, size, and undertone drive variant generation, with a compute layer (@api.depends on the attribute lines) that keeps display names, barcodes, and internal references consistent across every combination. We enable and tune lot/serial tracking so each incoming batch carries an expiry, and we extend the POS order flow so expiring or expired lots are flagged (or blocked) at scan time. Tester, sample, and gift-with-purchase units are handled as distinct routes so they deplete inventory without polluting sales figures. Everything ships as a proper Odoo module — its own __manifest__.py, models under models/, views in XML/OWL, access rights in ir.model.access.csv, and record rules for multi-store or multi-company visibility.

Technically, the build layers on top of Odoo's native Point of Sale, Inventory, and Sales apps rather than replacing them, so you keep every core feature and upgrade path. We add server-side logic via models.Model extensions and automated actions (for example, low-stock or near-expiry alerts), QWeb reports for shade-level sell-through and batch aging, and — where you need to feed a webstore, marketplace, or BI tool — clean integration points over the XML-RPC / JSON-RPC API. The app is written and tested for Odoo 17.0, 18.0, and 19.0, and we confirm at scoping whether your workflow depends on Enterprise-only features (advanced POS, studio-style customizations) or runs entirely on Community, so nothing you're shown assumes a license you don't hold.

Because this is build-to-order, delivery follows a short, predictable path: a scoping call to confirm your catalog structure, store count, and must-have workflows; a fixed written quote; a build on a staging environment; UAT with your team; then installation on production with a documented rollback plan. Typical delivery is 2 to 4 weeks from confirmed scope, depending on catalog size and integrations. Pricing starts from $349 (indicative, single-company base scope); multi-store or multi-company rollout, marketplace/webstore integration, localization depth (tax, receipts, language), and the volume of legacy product/stock data to migrate increase the quoted scope. You receive a firm fixed quote after the scoping call — never an open-ended bill.