Licence: OPL-1 · Revision: 273c56f5fe61
This selection is for Odoo 20.0. Install this app and its required dependencies in the addons directory configured for your Odoo 20.0 server, using the same Odoo version for each app.
Know where every received garment stands
Keep intake tags, processing stages and customer collections connected. Split work across batches, route failed inspections for rewash and reconcile every piece without duplicating the original intake.
Record garment descriptions, tagged-group quantities, stains, existing damage, a photo, service and promised date.
Assign washing, pressing and inspection. Split a batch in its current stage and track repeat processing without adding intake pieces.
Collect ready pieces in several visits. Track rejected returns, damaged returns and manager-acknowledged losses separately.
Each batch stays attached to its original garment tag. Rewash cycles, split lineage, named operators and exception notes remain visible in native forms and lists.
Includes an intake receipt, garment-group tags and a collection summary. Native HTML report rendering has been verified. PDF generation requires a working Odoo server PDF engine; server PDF output has not been qualified on the tested target. Manager reversals retain the original event and its correction reason.
A Laundry Manager explicitly creates one linked quotation using accepted intake quantities and native service pricing. Review and confirm it in Sales, then explicitly create a draft invoice. Repeating the laundry action opens the existing document. No automatic sale confirmation, invoice posting, payment or compensation is included.
Requires Odoo 20 with sale_management, account and mail. Assign Laundry Operator or Laundry Manager access. Normal data includes editable Wash and Press / Press Only routes, native service products and numbered intake, tag and batch references. Review example product prices, taxes and your accounting setup before use.
Tested on Odoo 20 Enterprise, including installation with and without demo data and focused workflow checks. Community edition has not been qualified. No paid device service or external integration is required.
Yes. Ready quantities decrease only by the number collected. Remaining processing and held pieces stay outstanding.
No. It retains the batch quantity and original tag and increments the reprocessing cycle count. Any additional charge must be deliberately reviewed in the native sales order.
No. Their recorded dispositions account for custody only. Managers handle financial adjustments separately through native accounting.
A tag identifies an intake line and its quantity. Use quantity one for individual garment tracking, or group identical garments intentionally. Splits remain attached to that original tag.
POS replacement, paid device integration, automatic messages, barcode hardware, weight-based invoicing, treatment guarantees, route scheduling and automatic compensation.
English RST and Markdown manuals are included.
Support: support@corvusnexus.com