<a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg"> </a> <a name="product-expiry-simple"></a> <h2>Product Expiry Simple</h2> <p>This module is similar to the official <a class="reference external" href="https://www.odoo.com/apps/modules/11.0/product_expiry/">product_expiry</a> module that adds support for <em>Expiry Dates</em> on products, but it is both simpler and better:</p> <ul class="simple"> <li>Only one <em>Expiry Date</em> field instead of 4 fields (End of Life Date, Best before Date, Removal Date, Alert Date)!</li> <li>Use date field instead of datetime field for <em>Expiry Date</em></li> <li>No automatic computing of Expiry Date based on a delay configured on product because it is not used most of the time (for manufacturing companies, the rules that control expiry dates are usually more complex than that ; for reseller companies, they have to copy the expiry date written on the good when they receive it in their warehouse)</li> <li>List views of production lots and quants have a color depending on expiry date: green if expiry date is in the future, red if it is in the past.</li> <li>Ability to show stats about expiry dates on quants pivot table (because, with this module, the <em>Expiry Date</em> is a related stored field on stock.quant).</li> </ul> <p>This modules keeps the main feature of the official <em>product_expiry</em> module: the support of FEFO (First Expiry First Out).</p> <p>I decided to develop this module because, after implementing <em>product_expiry</em> at several companies, I noticed that I spent more time inheriting the official <em>product_expiry</em> module to make always the same kind of changes that re-developping a simpler and better alternative.</p> <a name="configuration"></a> <h3>Configuration</h3> <p>No configuration needed.</p> <a name="usage"></a> <h3>Usage</h3> <a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/154/11.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a> <a name="bug-tracker"></a> <h3>Bug Tracker</h3> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/stock-logistics-workflow/issues">GitHub Issues</a>. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.</p> <a name="credits"></a> <h3>Credits</h3> <a name="contributors"></a> <h4>Contributors</h4> <ul class="simple"> <li>Alexis de Lattre &lt;<a class="reference external" href="mailto:alexis.delattre&#64;akretion.com">alexis.delattre&#64;akretion.com</a>&gt;</li> <li>Alan Ramos &lt;<a class="reference external" href="mailto:alan.ramos&#64;jarsa.com.mx">alan.ramos&#64;jarsa.com.mx</a>&gt;</li> </ul> <a name="maintainer"></a> <h4>Maintainer</h4> <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a> <p>This module is maintained by the OCA.</p> <p>OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.</p> <p>To contribute to this module, please visit <a class="reference external" href="https://odoo-community.org">https://odoo-community.org</a>.</p>