• New

    • Multiple locations in price list: Upload prices for multiple locations using a single price list.
      • Use Case 1 - Locations A and B belong to Franchisee X and have same price list; Locations C and D belong to Franchisee Y. Two price lists can be created Pricelist_X and Pricelist_Y for locations A,B and C,D respectively, instead of creating price list for each location separately.
      • Use Case 2 - Similarly, if prices vary with geographic division or zone, price lists can be created for each zone rather than for each location.To know more, click here.
    • Schedule activation and deactivation of price list: Upload price list in advance with a scheduled activation and deactivation date.
      • Use Case 1 - During clearance or flash sale, products will be at a discounted price. The discounted price will be valid only for a sale period. Create a price list Pricelist_EOSS which will be activated when sale starts and deactivated when sale ends.
      • Use Case 2 - New prices would be effective from tomorrow onward from 10 AM. Upload the price list tonight with a scheduled activation at 10 AM to avoid any delay in upload due to heavy load in business hours. Your upload is complete in advance, only activation is pending, which will happen at scheduled time.
      • Use Case 3 - New prices will be effective for a merchant in Singapore at 4 AM IST. MIS users need not upload price list at wee hours; they can do it in advance and schedule the activation time.
        To know more, click here.
    • Channel-wise price list: Set different prices in different channels.
      • Use Case - Price in member facing website or app will be subsidized compared to staff operated BDA app to promote self-service. To create channel, go to Store Information > Channel Management > Add Channel. Select ‘Web’ for Storefront and ‘Apps’ for app based on API Integration.

        To know more, click here.
    • Price calculator: Get final price of SKU and price calculation trace.
      • Use Case 1 - Verify if price of SKU for a location, user group of channel is as per price list rule.
      • Use Case 2 - Verify if the price of SKU for present or future point of time is as per the scheduled activation/deactivation date.
      • Use Case 3 - Find complete detail of how price was calculated - based on price list, promotion or default price, and which price lists matched for the SKU and which one was the final price list.

      • To know more, click here.
  • Improved

    • Performance improvement: Performance of price engine was identified as root cause of several P0/P1 bugs in the past. It did not just slow down the price updates on storefront, but also brought down the entire system on a few occasions. The bugs reported were of types 'prices not showing on storefront hours after Price list upload’, ‘orders not getting placed’, etc.
      • Price Engine: Price engine is responsible for calculating the final price of a product based on different parameters such as location wise price, user group wise price, slab wise price and catalog promotions. Storefront and PWA get product prices from Price Engine through Web Service or API.
        What are the benefits of New Price Engine?
        • Predictability: The biggest advantage is predictability. In earlier version, it could take hours in showing updated price on storefront depending on the volume of price uploads. With the new version, it will not take more than 15 mins for price to show on storefront after location wise price or price list upload is complete, as cache invalidation is done after every 15 minutes. With real-time cache invalidation, which is a work in progress, price will start reflecting immediately in real-time. To know more, click here.
        • Single Source of Truth: There is one service to get price whether storefront or front api. Earlier, different services used their own logic to get price from different tables. To know more, click here.
        • Extensibility: New rules to Price List can be added without any performance downgrade and without much development effort. The earlier version was computationally demanding, hence it was not possible to add more rules to the Price List such as time based price list. With the new version, adding new rules has become easier. To know more, click here.
      • How does Server Response Time compare in v1 and v2? There is no compromise in server response with new Price Engine. For Price Get Developer API, average server response time is:
        •  V1 - 28 ms
        • V2 - 24 ms

    Note:  Please note that the objective of Price Engine v2 was not improving response time but the ones listed without compromising on get response performance.