Changes required by the Magento plugin to multiprice search engines.
Decisions
The feed URL depends on the Store View. Hence, it looked like a bad idea to mix several Store Views into one Search Engine.
Also, it looks like the function of the Store Views is mainly translations (it allows for different languages to be set) and not multicurrency.
What we do right now is consider the Default Display Currency for a Store View and use it as the currency of the Search Engine.
However, it might be time to reconsider this as the real configuration for the allowed currencies for a Store View is actually in the Allowed Currencies field which can also be configured at Store View level.
If we use this, now we would have a Search Engine per Store View (configuring different languages) and a number of allowed currencies, which would configure the prices for every product in that Search Engine (this would be much similar to what we are doing with the other platforms).
Open Items / Questions
How are we going to handle the retrocompatibility/deployment?
Is there any update needed in the script?
Is there any update needed due to changes in the Installation search engine mapping?
How are we going to determine which currency symbol to use?
Is there any update on the response of the Doomanager create store request?
Changes required by the Magento plugin to multiprice search engines.
Decisions
Open Items / Questions