PINO has a complex price calculation logic, which needs to be called from the ERP system in realtime. This causes performance issues for the store frontend. In order to improve the customer experience, we analyzed how many different types of price lists exist.
The result was: there are 95% of customers using the same price calculation logic. We decide to implement an import for that 95% of customers to avoid API requests to the ERP system and call the API for the other 5%.
Facts and figures
|Imported Entities||Products (Delivery Date only)|
|Import Frequency||Products/Prices/Tier-Prices [Frequency: once per day, Runtime incl. data aggregation: ~35 seconds]|
Amount of Data
|Websites||10 (3 active)|
|Stores||10 (3 active)|
|Store View||10 (3 active)|
|~ 1.400 Simples|
|~ 50 Bundles|
|M2IF PE 3.7.*||Default Mode (no Single Transaction)|
|Performance Booster (via Batch Processing|
|Product (with custom configuration; status update only)|