Search 1.9 billion lines of Odoo code on GitHub
shopinvader_customer_price
<h1 class="title">Shopinvader Customer Price</h1>
<p><a class="reference external" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external" 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.png" /></a> <a class="reference external" href="https://github.com/shopinvader/odoo-shopinvader/tree/14.0/shopinvader_customer_price"><img alt="shopinvader/odoo-shopinvader" src="https://img.shields.io/badge/github-shopinvader%2Fodoo--shopinvader-lightgray.png?logo=github" /></a></p>
<p>Handle customer specific prices.</p>
<p>Provides:</p>
<ul class="simple">
<li>endpoint <cite>/customer_price/products</cite> to fetch customer prices for products.</li>
<li>backend configuration to state which pricelist should be used by partner
(by selecting a partner field that relates to pricelists)</li>
</ul>
<p><strong>Use case</strong></p>
<p>Thousands of customers and at least 1 pricelist per each customer.
You want to display customer specific prices in the frontend on demand.
For instance: product page, wishlists, etc.</p>
<p><strong>Rationale</strong></p>
<p>One of the key points of Shopinvader's speed
is the delegation of products' data indexing to external search engines.</p>
<p>While this is perfect for generic data and not so complex price rules,
if you have very special prices per each customer that's a blocker,
and you'd need to index all prices for all customers to make it work seemlessly.</p>
<p><strong>Warning</strong></p>
<p>It's strongly recommended to not call the endpoint for each product on search results
otherwise you'll get potentially thousands of requests to Odoo.</p>
<p>Also, when setting the pricelist field for the partner,
beware that prices in the indexes might differ from the prices in the cart.</p>
<p><strong>Table of contents</strong></p>
<div class="contents local topic" id="contents">
<ul class="simple">
<li><a class="reference internal" href="#known-issues-roadmap" id="id1">Known issues / Roadmap</a></li>
<li><a class="reference internal" href="#bug-tracker" id="id2">Bug Tracker</a></li>
<li><a class="reference internal" href="#credits" id="id3">Credits</a><ul>
<li><a class="reference internal" href="#authors" id="id4">Authors</a></li>
<li><a class="reference internal" href="#contributors" id="id5">Contributors</a></li>
<li><a class="reference internal" href="#other-credits" id="id6">Other credits</a></li>
<li><a class="reference internal" href="#maintainers" id="id7">Maintainers</a></li>
</ul>
</li>
</ul>
</div>
<a name="known-issues-roadmap"></a>
<h2><a class="toc-backref" href="#id1">Known issues / Roadmap</a></h2>
<p>Probably the best option would be to have 1 index per customer
which would even allow to sort and filter products by customer's prices
but this requires a lot of work with current implementation of search engine machinery.</p>
<p>If you use Algolia this is probably a no-go as it would cost too much.
In the context of ElasticSearch instead you could afford it.</p>
<p>Things that would be needed to go for an indexed solution:</p>
<ul class="simple">
<li>make language not required on indexes (at the momemt the whole SE machinery relies on languages)</li>
<li>automatically generate one index per each pricelist/customer</li>
<li>make the frontend capable of switching indexes depending on the customer</li>
</ul>
<a name="bug-tracker"></a>
<h2><a class="toc-backref" href="#id2">Bug Tracker</a></h2>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/shopinvader/odoo-shopinvader/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
<a class="reference external" href="https://github.com/shopinvader/odoo-shopinvader/issues/new?body=module:%20shopinvader_customer_price%0Aversion:%2014.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">feedback</a>.</p>
<p>Do not contact contributors directly about support or help with technical issues.</p>
<a name="credits"></a>
<h2><a class="toc-backref" href="#id3">Credits</a></h2>
<a name="authors"></a>
<h3><a class="toc-backref" href="#id4">Authors</a></h3>
<ul class="simple">
<li>Camptocamp</li>
</ul>
<a name="contributors"></a>
<h3><a class="toc-backref" href="#id5">Contributors</a></h3>
<ul class="simple">
<li>Simone Orsi <<a class="reference external" href="mailto:simahawk@gmail.com">simahawk@gmail.com</a>></li>
</ul>
<a name="other-credits"></a>
<h3><a class="toc-backref" href="#id6">Other credits</a></h3>
<p>The development of this module has been financially supported by:</p>
<ul class="simple">
<li>Camptocamp</li>
<li>Cosanum</li>
</ul>
<a name="maintainers"></a>
<h3><a class="toc-backref" href="#id7">Maintainers</a></h3>
<p>This module is part of the <a class="reference external" href="https://github.com/shopinvader/odoo-shopinvader/tree/14.0/shopinvader_customer_price">shopinvader/odoo-shopinvader</a> project on GitHub.</p>
<p>You are welcome to contribute.</p>