Skip to main content

No discount target

Use None when the discount should exist in Flux, but Flux should not calculate a product, fee, gift, or total price reward from the discount itself.

This is useful when the discounted price is calculated somewhere else but you still want Flux to track the usage and control which other discounts it can be combined with.

When to use None​

Choose None when:

  • The discount is external and another system calculates the reward.
  • You want to track an external discount in Flux.
  • You want Flux to control combination rules for a discount from another system.

External discount example​

An external system may decide that a customer should receive a special product price. Flux does not calculate that price, but you still want Flux to:

  • Know that the discount exists.
  • Decide whether it can combine with other discounts.
  • Track discount usage.
  • Show statistics later.

In that case, create the discount, set the target to None, and enable Is external discount.

Discount code or customer discount example​

Sometimes the main discount record is used as a container for discount codes or customer discounts.

If the reward is not set directly on the discount itself, None can be used on the main discount. The actual application can then be managed through the relevant discount code or customer discount setup.

What None does not do​

None does not reduce product prices, fees, or cart totals by itself. It also does not add gifts by itself.

If Flux should calculate the customer reward, choose one of the other targets:

  • Line item for product or order line discounts.
  • Buy X get Y for quantity-based item discounts.
  • Total price for order total discounts.
  • Fee for fee discounts.
  • Gift for gift products.

Good practice​

Use a clear name and description for discounts with no target. People reviewing the discount later should be able to tell which external system or business process creates the actual customer reward.