Shopinvader Customer Price

Beta License: AGPL-3 shopinvader/odoo-shopinvader

Handle customer specific prices.

Provides:

Use case

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.

Rationale

One of the key points of Shopinvader’s speed is the delegation of products’ data indexing to external search engines.

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.

Warning

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.

Also, when setting the pricelist field for the partner, beware that prices in the indexes might differ from the prices in the cart.

Table of contents

Known issues / Roadmap

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.

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.

Things that would be needed to go for an indexed solution:

Bug Tracker

Bugs are tracked on GitHub Issues. 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.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Camptocamp

Other credits

The development of this module has been financially supported by:

  • Camptocamp
  • Cosanum

Maintainers

This module is part of the shopinvader/odoo-shopinvader project on GitHub.

You are welcome to contribute.