Help for Aimeos

Hello,
I would like to use Aimeos for a B2B shop where each user has different prices for the same product/item. I wonder what would be the best way to achieve this? Is it a good start to use a separate price_list for each customer? Or better use different site_ids?
I did not find any good documentation about the price model and the possible options. If you have a good start for me, I'd appreciate your help.
Claudia

The Aimeos company is offering an extension for customer/group specific prices:
https://aimeos.com/extensions/#c823

Thank you. Is there a demo where I can have a look at it? I'd like to make sure that this extension fulfills our needs.

There's no public demo yet but you can have a look at the screenshot which contains the product price sub-panel. In the "advanced" section, you can add one or more customers and/or groups for each price. These prices will be only available for the customers or customer groups. Both, the customers and groups are used from the host system (Laravel, TYPO3, etc.). This does also work for products, categories, services and other items and where ever a price can be added.

Hi aimeos and nos3,

is it possible not only to offer fixed prices for users and groups but rebates for users and groups as a percentage substracted from the standard price or a percentage from the standard price?

If thats not possible, is it possible to extend the extension by ourselves to get this functionality.

By introducing rebates for the standard price editing catalog data is simplified and possible errors for editors are reduced.

Regards
Robert.

It would be no problem to allow the editors to enter rebate values in percent in the admin interface but in the database, the computed prices has to be stored. Otherwise, sorting by price won't show expected results. If that doesn't matter, you could write a basket plugin that recalculates the price including the rebate if a product is added to the basket. For the frontend (list/detail view) you would have to calculate the reduced prices either in the frontend or in the product controller.

Thanks for your feedback.

That sounds like the extension might not be necessary at all.

I´ll try to explain our scenatio a little deeper. We have different customer groups which get different rebates on different product areas. It´s like a two dimensional matrix. Customer group on one axis and the product area on the other.

The product areas are notcatalog catagories. We´ll define them via product attributes that are not visible in frontend.

So my assumption is the rebate matrix gets stored in the settings array and I will have to write the mentioned basket plugin and will have to extend frontend and product controller to calculate the rebated prices in the necessary areas.

Is that a strategy?

Regards
Robert.

Yes, an attribute for each product area and rebate is a good idea. You can also add customer groups to the attributes so they are only available for the right customers. Then, a basket plugin for recalculating the price in the basket is necessary.

If you have a good start for me, I'd appreciate your help.

After you've bought the ai-customergroups extension from the Aimeos company, you can add customers or customer groups in the extended view of the price items like shown above in the thread.