Every feature. Your price.

WHAT €0 ACTUALLY MEANS

The zero-price option is the real product, not a funnel disguised as generosity.

A store choosing €0 should not discover that useful targeting, Auto Apply, stacking or administration suddenly require an upgrade. The commercial decision and the capability decision are intentionally separate. That means the product has to earn support through usefulness rather than through strategically placed missing features. It also means a store can evaluate PerkRule in its real workflow instead of judging a crippled demo and guessing what the paid version might feel like.

VALUE AFTER USE

Pay-what-you-want works only if the user can judge value after the product has done real work.

A promotion tool can be worth very different amounts to different stores. For one shop it may prevent an occasional coupon mistake; for another it may replace several paid extensions or save hours every month. PerkRule does not pretend those stores received identical economic value. The model asks the product to demonstrate usefulness first, then lets the owner decide whether and how much to contribute without changing the feature set.

A valid price

If paying is not right for you, keep using the full product.

Support follows value

Contribute when the product has actually saved time, prevented mistakes or earned its place in the store.

Lifetime Supporter

Once cumulative support reaches €200, supporter reminders disappear permanently.

SEPARATE THE TWO MODELS

Feature architecture should not be distorted by a pricing table.

Traditional plugin tiers often pressure product design into artificial boundaries: a rule exists in Basic, a slightly more useful rule becomes Pro, and compatibility or automation becomes a higher tier because the pricing page needs another column. PerkRule's engineering model does not need to ask which tier a capability belongs to. If a feature belongs in Product 001 and is ready to ship, it belongs in Product 001 for everyone.

WHAT PAYMENT CHANGES

Contribution changes supporter status and reminder cadence, not what the engine is allowed to do.

Support can be acknowledged without turning it into a feature entitlement system. Cumulative contributions are remembered, reminder frequency can become less frequent as support grows, and reaching €200 total grants Lifetime Supporter status with supporter reminders gone permanently. None of those states should alter checkout logic, rule availability or the promotion engine's core capability.

ADMIN ONLY

A commercial reminder belongs where the store owner works, never where the shopper pays.

Support reminders are intentionally an administration concern. They are throttled, non-blocking and kept out of storefront rendering and checkout execution. A shopper should never see a contribution prompt, and an unpaid or unreachable license service should never become a reason a cart cannot calculate. The commercial relationship is between PerkRule and the store owner; the customer should be completely insulated from it.

REMOTE FAILURE POLICY

Licensing, updates and supporter status are allowed to fail without becoming commerce failures.

The future private update and license infrastructure is useful for distribution and account state, but it is explicitly not a checkout dependency. Live promotion decisions must remain local. If the remote service is slow, unavailable or temporarily wrong, the correct response is to postpone remote work and keep the store functioning — not to block coupon validation, cart totals or payment because somebody else's server did not answer.