How to Review PrestaShop Discount Rules Before a Campaign

Visual checklist for reviewing PrestaShop discount rules before a campaign.

Creating a promotion in PrestaShop may look straightforward: choose a discount, select the applicable products and define when the campaign should run.

The complexity usually appears when the store already has other pricing rules in place.

A product may have its own specific price, belong to a catalog promotion and later be added to a cart where the shopper enters an additional voucher.

Each rule may be correct on its own while the final amount charged to the customer is still different from what the campaign team intended.

That is why a promotion should be tested as a complete purchase rather than checked only on the product page.

Start by identifying the type of discount

PrestaShop provides different mechanisms for applying pricing conditions.

A specific price is useful when the condition is directly related to a particular product.

Catalog price rules can cover broader sets of products and use conditions such as customer group, country, currency, quantity and campaign period.

Cart rules are designed for purchase-level conditions and vouchers. They may include requirements involving order value, products, categories, carriers, customer groups and compatibility with other cart rules.

Before troubleshooting a campaign, ask a simple question:

Which mechanism is responsible for each discount?

Knowing that makes unexpected pricing considerably easier to diagnose.

List every rule that may affect the order

A new campaign rarely operates in isolation on an established store.

Before activating it, review:

  • active specific prices;
  • catalog price rules;
  • cart rules;
  • public voucher codes;
  • customer-specific or group-specific vouchers;
  • quantity discounts;
  • existing category promotions;
  • automatically applied rules without a voucher code.

The objective is not only to find the new campaign. You want to identify any existing rule that may affect the same product, customer or cart.

Define the expected result before testing

A common testing mistake is completing an order and then deciding whether the total “looks right”.

A better process starts with an expected result.

For example:

Product price: $200
Campaign discount: 15%
Expected price: $170

Then document what should happen in additional scenarios.

Should another voucher be accepted?

Does the promotion apply to every customer group?

Is there a minimum quantity?

Does the offer include shipping?

Can products that are already discounted receive another voucher?

Once those rules have been defined, testing becomes objective.

Review voucher compatibility

PrestaShop allows cart rules to be configured in relation to other cart rules.

This deserves explicit testing.

A store may launch a new site-wide promotion while an older voucher is still valid for a previous campaign or a particular customer segment.

If both rules can be used together, the effective discount may be different from the one considered when the new campaign was prepared.

Do not review only the application order.

Also decide whether those discounts should be allowed to coexist.

Test at least:

  • the new promotion alone;
  • the existing voucher alone;
  • both conditions together;
  • a voucher that is expected to be incompatible.

Test anonymous and authenticated shoppers

Commercial conditions may differ according to the customer context.

A promotion may be available to a particular customer group while another rule applies to everyone.

At a minimum, test:

An anonymous visitor

and

An authenticated customer

If the store has additional groups — wholesale customers, resellers, VIP accounts or other segments — include representative accounts from every group affected by the campaign.

A discount that works correctly during an administrator’s test may behave differently for the actual customer.

Test quantities around the threshold

Quantity-based discounts require boundary testing.

If a promotion begins at three units, test:

  • 2 units;
  • 3 units;
  • 4 units.

This simple approach verifies the point immediately below the threshold, the threshold itself and a value above it.

It is often enough to reveal an incorrect quantity condition.

Verify campaign dates and times

For time-limited promotions, review:

  • start date;
  • end date;
  • configured time;
  • store timezone;
  • older rules with overlapping periods.

This is particularly important for promotions scheduled to begin or end at midnight.

A timezone mismatch can make a valid rule become active or expire earlier than expected.

Do not stop at the product page

A correct product-page price is only the beginning of the test.

Continue through the entire purchase journey.

Product page

Confirm the displayed price and the selected product variation when applicable.

Cart

Review unit price, discount, quantity, subtotal and voucher application.

Checkout

Confirm that the values remain consistent after address, shipping and other purchase conditions have been selected.

Final amount

The total should match the scenario documented before testing began.

When a discrepancy appears, record the exact stage where the amount changed.

That information usually makes the responsible rule much easier to locate.

A practical test matrix

Promotion testing does not need to become a large quality-assurance project.

A compact matrix is often enough:

ScenarioCustomerQuantityVoucherExpected result
1Visitor1NoStandard promotion
2Customer1NoStandard promotion
3Customer1YesAccording to compatibility rules
4Special group1NoGroup-specific pricing
5CustomerPromotion thresholdNoQuantity discount
6CustomerPromotion thresholdYesValidate combined rules

The important part is defining the expected behavior before running the test.

Any difference then becomes something to investigate rather than something to justify afterwards.

Treat discounts as business rules

Promotions directly affect pricing, margins and customer expectations.

They should therefore be tested as business rules, not merely as visual changes to a storefront.

Before publishing a campaign:

  1. identify all relevant pricing rules;
  2. define the expected outcome;
  3. test different customer contexts;
  4. validate quantity thresholds;
  5. review discount compatibility;
  6. complete the cart and checkout flow;
  7. record the results.

This is a small amount of work compared with correcting an incorrect promotion after customers have already seen it.

If your PrestaShop store uses complex pricing conditions or you need a technical review before launching a campaign, AGTI can help analyze and adjust the configuration.