{"id":2361,"date":"2026-05-26T10:00:00","date_gmt":"2026-05-26T07:00:00","guid":{"rendered":"https:\/\/commerce-consulting-services.com\/en\/?p=2361"},"modified":"2026-03-24T09:47:19","modified_gmt":"2026-03-24T07:47:19","slug":"sap-commerce-promotion-engine-performance-fixes","status":"publish","type":"post","link":"https:\/\/commerce-consulting-services.com\/en\/sap-commerce-promotion-engine-performance-fixes\/","title":{"rendered":"SAP Commerce Promotion Engine Slow? Top 10 Performance Fixes"},"content":{"rendered":"

[et_pb_section fb_built=”1″ admin_label=”Hero” _builder_version=”4.27.5″ _module_preset=”default” custom_padding=”0vw||80px||false|false” locked=”off” collapsed=”on” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_row _builder_version=”4.18.0″ _module_preset=”5138c454-be54-4233-bd3b-f8e6a8747976″ global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.18.0″ _module_preset=”73121f80-a3ef-4484-8763-c3f18e3c56d2″ global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”SAP Commerce” _builder_version=”4.27.5″ _module_preset=”f0c675ea-2574-4d0e-b725-30f8550a8550″ title_level=”h4″ title_font=”IBM Plex Sans|IBM Plex Sans Condensed_weight||on|||||” title_text_color=”#1d3557″ title_font_size=”14px” title_letter_spacing=”1px” title_line_height=”1.4em” custom_margin=”||10px||false|false” locked=”off” global_colors_info=”{%22#1d3557%22:%91%22title_text_color%22%93}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_heading title=”SAP Commerce Promotion Engine Slow? Top 10 Performance Fixes” _builder_version=”4.27.5″ _module_preset=”ddeb8c09-9078-4424-bc15-2efb6572e28e” title_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_post_title title=”off” meta=”off” featured_image=”on” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_post_title][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

If you have spent any time profiling a slow SAP Commerce storefront, the promotion engine has almost certainly appeared near the top of the flame graph. Cart calculation, the process that evaluates promotions, applies discounts, and computes final prices, is one of the most performance-sensitive operations in any e-commerce platform. In SAP Commerce, it is also one of the most frequently problematic.<\/p>\n

We have debugged promotion engine performance issues across industries and scales: from retail storefronts with hundreds of concurrent promotions to B2B platforms with customer-specific pricing rules. The pattern is consistent: promotion evaluation starts fast with a few simple rules, then degrades as the business adds more promotions, more complex conditions, and more custom logic. By the time someone raises an alarm, cart calculation is taking 2-5 seconds, and checkout abandonment rates tell the story.<\/p>\n

This article presents 10 specific fixes, ordered roughly by effort and impact. Most can be implemented in a sprint or less. Together, they have produced 80-90% reductions in cart calculation time in real projects.<\/p>\n

[\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”How the Promotion Engine Works Internally” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

Before optimizing, you need a mental model of what the promotion engine does during cart calculation.<\/p>\n

When CommerceCartService.recalculateCart()<\/code> is called, the following sequence executes:<\/p>\n

    \n
  1. \n

    Load active promotions.<\/strong> The engine queries for all PromotionSourceRule<\/code> instances that are currently active (within their date range and applicable to the current site\/catalog).<\/p>\n<\/li>\n

  2. \n

    Compile rules to Drools.<\/strong> If not already compiled, source rules are converted to Drools rule definitions. The compiled rules are cached in the RuleEngineContext<\/code>.<\/p>\n<\/li>\n

  3. \n

    Build the fact model.<\/strong> The engine creates a set of facts (objects representing the current cart, its entries, the customer, the session) and inserts them into the Drools working memory.<\/p>\n<\/li>\n

  4. \n

    Fire rules.<\/strong> Drools evaluates all conditions and fires actions for matching rules. This is where conditions are checked (Is the product in the cart? Is the cart total above X? Is the customer in group Y?) and actions are queued (Apply percentage discount, add free gift, set fixed price).<\/p>\n<\/li>\n

  5. \n

    Apply actions.<\/strong> The fired actions are translated into PromotionResult<\/code> and AbstractPromotionAction<\/code> instances, which modify the cart’s discount values.<\/p>\n<\/li>\n

  6. \n

    Recalculate totals.<\/strong> The cart’s subtotal, tax, and total are recalculated based on applied discounts.<\/p>\n<\/li>\n<\/ol>\n

    Each step has performance implications, but steps 1, 3, and 4 are typically where the time goes.<\/p>\n

    [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Fix 1: Reduce Active Promotion Count” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

    This is the single highest-impact fix, and it requires no code changes.<\/p>\n

    Every active promotion is loaded, compiled, and evaluated on every cart calculation. If you have 200 active promotions but only 30 are relevant to any given cart, you are wasting evaluation time on 170 irrelevant rules.<\/p>\n

    Audit your promotions.<\/strong> Log into Backoffice and filter promotions by status. Look for:<\/p>\n

      \n
    • Expired promotions<\/strong> that were never deactivated. The date range may have passed, but if the engine still loads them to check the date condition, you pay a cost.<\/li>\n
    • Test promotions<\/strong> left over from development and QA.<\/li>\n
    • Seasonal promotions<\/strong> from past campaigns that are still marked as active.<\/li>\n
    • Duplicate promotions<\/strong> that were cloned for testing and never removed.<\/li>\n<\/ul>\n

      In one engagement, we found a retail client with 340 active promotions in production. After audit, only 85 were actually needed. Removing the rest reduced cart calculation time by 45%, with zero functional impact.<\/p>\n

      Establish governance.<\/strong> Create a process for promotion lifecycle management. Every promotion should have an owner, a start date, an end date, and a review date. Automate deactivation of expired promotions through a scheduled cronjob.<\/p>\n

      [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Fix 2: Simplify Promotion Conditions” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

      Complex conditions create exponential evaluation cost. A promotion with the condition “Buy any 3 products from Category A AND any 2 products from Category B AND spend over 100 EUR AND be a Gold member AND apply on weekdays only” requires the engine to evaluate multiple joins across cart entries, category memberships, customer groups, and date logic.<\/p>\n

      Decompose complex promotions.<\/strong> If a business rule requires 5 conditions, consider whether it can be split into 2 simpler promotions with a shared exclusion group. This is not always possible, but when it is, the performance improvement is significant.<\/p>\n

      Avoid cart-level conditions when entry-level suffices.<\/strong> A condition like “cart contains product X” requires scanning all cart entries. If the promotion only applies to product X, make it an entry-level promotion with the condition on the entry’s product, not a cart-level scan.<\/p>\n

      Review custom conditions.<\/strong> Custom condition definitions (implementations of RuleConditionDefinition<\/code>) can hide arbitrary complexity. A custom “customer has purchased product X in the last 30 days” condition that queries order history on every cart calculation is a performance disaster. If you have custom conditions, profile them individually.<\/p>\n

      [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Fix 3: Use Priority and Exclusivity to Short-Circuit Evaluation” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

      Drools evaluates rules in priority order. When a high-priority rule fires and is marked as exclusive within its group, lower-priority rules in the same group are skipped.<\/p>\n

      Set meaningful priorities.<\/strong> Do not leave all promotions at the default priority. Assign higher priority to promotions most likely to fire (site-wide discounts, common voucher codes) and lower priority to niche promotions.<\/p>\n

      Use promotion groups and exclusivity.<\/strong> If a customer qualifies for a 30% VIP discount, there is no business reason to also evaluate whether they qualify for a 10% newsletter signup discount on the same product. Define promotion groups (using PromotionGroup<\/code> or rule group concepts) and set exclusivity flags so that once a promotion fires for an entry, other promotions in the same group are skipped.<\/p>\n

      Configure maxAllowedRuns<\/code>.<\/strong> The maxAllowedRuns<\/code> property on the rule engine context controls how many rule evaluation cycles Drools performs. The default may be higher than necessary. If your promotions do not depend on each other’s results (rule chaining), a single pass is sufficient.<\/p>\n

      [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Fix 4: Cache Promotion Results Where Applicable” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

      Cart calculation is triggered frequently: when items are added, quantities change, voucher codes are applied, and sometimes on cart page load. Not every trigger requires a full promotion re-evaluation.<\/p>\n

      Implement result caching.<\/strong> If the cart contents have not changed since the last calculation, the promotion results are still valid. Store a hash of the cart state (entry PKs, quantities, voucher codes, customer group) alongside the promotion results. On the next calculation, compare hashes before re-evaluating.<\/p>\n

      Careful with cache invalidation.<\/strong> Promotion results must be invalidated when:<\/p>\n

        \n
      • Cart entries change (add, remove, quantity update)<\/li>\n
      • Voucher codes are applied or removed<\/li>\n
      • The customer’s group membership changes<\/li>\n
      • A promotion’s active status changes (start\/end date boundary)<\/li>\n
      • Price changes affect threshold-based promotions<\/li>\n<\/ul>\n

        Getting invalidation wrong means customers see stale discounts, which is worse than slow performance. Implement this cache with explicit invalidation triggers, not TTL-based expiration.<\/p>\n

        [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Fix 5: Optimize Cart Calculation Triggers” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

        Review every place in your codebase that calls recalculateCart()<\/code> or triggers cart calculation. In many projects, cart calculation is triggered more often than necessary.<\/p>\n

        Common over-triggers:<\/strong><\/p>\n

          \n
        • Cart page load.<\/strong> Does the cart need recalculation on every page view? If nothing changed since the last calculation, skip it.<\/li>\n
        • Add to cart.<\/strong> Some implementations calculate the cart after adding each item in a multi-item add. Batch the additions and calculate once.<\/li>\n
        • Address changes.<\/strong> Changing the delivery address triggers recalculation (for tax). But changing a field within the address form on every keystroke should not.<\/li>\n
        • Session restoration.<\/strong> When a returning customer’s session is restored, the cart is often recalculated. If the cart was calculated recently and no promotions have changed, this may be unnecessary.<\/li>\n<\/ul>\n

          Implement dirty flagging.<\/strong> Add a calculationRequired<\/code> flag to the cart. Set it to true<\/code> when cart contents change. Only run calculation when the flag is true<\/code>. Reset it after successful calculation.<\/p>\n

          [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Fix 6: Database Indexing for Promotion-Related Queries” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

          The promotion engine executes several database queries during evaluation: loading active promotions, resolving product-category memberships, checking customer group assignments, and more.<\/p>\n

          Index promotion lookup queries.<\/strong> Enable Flexible Search logging, trigger a cart calculation, and review the generated SQL. Look for slow queries and add missing indexes. Common candidates:<\/p>\n

            \n
          • Promotion source rules filtered by status<\/code>, website<\/code>, and date range.<\/li>\n
          • Category-to-product assignment queries (the Category2ProductRelation<\/code> table).<\/li>\n
          • Customer group membership queries.<\/li>\n<\/ul>\n

            Review the cat2prodrel<\/code> table.<\/strong> If your catalog has deep category hierarchies and products belong to many categories, the category membership check during promotion evaluation can be slow. Ensure the relationship table has appropriate indexes on both the source and target columns.<\/p>\n

            Monitor query plan changes.<\/strong> Adding products or categories can change the database query planner’s decisions. A query that used an index with 100,000 products might switch to a full table scan at 200,000 products. Monitor query execution plans periodically.<\/p>\n

            [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Fix 7: Batch Promotion Evaluation for Bulk Operations” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

            Bulk operations, importing orders, migrating carts, processing subscription renewals, expose promotion engine bottlenecks dramatically. Processing 10,000 orders with individual cart calculations takes 10,000 times the single-cart calculation time.<\/p>\n

            Batch processing strategies:<\/strong><\/p>\n

              \n
            • Disable promotion evaluation<\/strong> for operations that do not need it. Bulk order imports from an ERP system likely have pre-calculated prices and do not need promotion evaluation.<\/li>\n
            • Use CalculationService<\/code> directly<\/strong> instead of the full CommercePlaceOrderStrategy<\/code> for operations where you only need price calculation without promotion evaluation.<\/li>\n
            • Parallelize across threads<\/strong> for independent cart calculations. Each cart calculation is independent, so thread safety is not a concern at the calculation level (but database connection pool sizing becomes important).<\/li>\n<\/ul>\n

              [\/et_pb_text][et_pb_divider _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_divider][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][et_pb_heading title=”Fix 8: Review Custom Promotion Conditions and Actions for N+1 Queries” _builder_version=”4.27.5″ _module_preset=”default” global_colors_info=”{}” theme_builder_area=”post_content”][\/et_pb_heading][et_pb_text quote_border_color=”#457b9d” _builder_version=”4.27.5″ _module_preset=”2c55a9c4-feed-423b-9edb-ae0b5b365cac” text_font=”IBM Plex Sans|IBM Plex Sans_weight|||||||” link_font=”|IBM Plex Sans_weight|||||||” link_text_color=”#1d3557″ quote_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_2_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_3_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_4_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_5_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” header_6_font=”IBM Plex Sans Condensed|IBM Plex Sans Condensed_weight|||||||” locked=”off” global_colors_info=”{}” theme_builder_area=”post_content”]<\/p>\n

              Custom RuleConditionTranslator<\/code> and RuleActionStrategy<\/code> implementations are the most common source of hidden performance problems in the promotion engine.<\/p>\n

              The N+1 pattern in promotion conditions.<\/strong> A custom condition that checks whether a product has a specific attribute value will execute a database query for each cart entry, for each promotion that uses this condition. With 10 cart entries and 20 promotions using the condition, that is 200 queries.<\/p>\n

              How to fix it:<\/strong><\/p>\n