Engineering Receipt / Conflict Planning

Promotion conflicts get a plan first.

Eligible automatic promotions resolve into a deterministic plan before live cart mutation begins.

If coupons are applied while conflicts are still being discovered, traversal order can become business logic. A separate resolution plan makes ties, exclusivity and failure behavior explicit.

IMPLEMENTATION

How the claim is implemented.

Eligible automatic promotions resolve into a deterministic plan before live cart mutation begins.

Implementation point

Higher explicit priority wins; deterministic ties use stable coupon identity.

Implementation point

Stack, exclusive, conflict-group and Best Deal modes are represented explicitly.

Implementation point

Native WooCommerce individual-use constraints remain hard constraints and protected manual coupons are not evicted.

Implementation point

Best Deal chooses within explicit bounded groups rather than searching unbounded coupon subsets.

Implementation point

The resolver produces a minimal removal/application plan before the first live cart mutation.

EVIDENCE

What currently supports the claim.

If coupons are applied while conflicts are still being discovered, traversal order can become business logic. A separate resolution plan makes ties, exclusivity and failure behavior explicit.

Verification evidence

Best Deal scoring uses WooCommerce cart totals behavior on an isolated cart clone rather than custom discount arithmetic.

Verification evidence

Representative fixed-cart, percentage and fixed-product discount cases are covered against native WooCommerce behavior.

Verification evidence

The runtime keeps automatic ownership separate from coupon application mode so conflict resolution cannot silently claim manual state.

KNOWN BOUNDARY

What this receipt does not claim yet.

Free-shipping monetary value is not yet scored inside Best Deal groups, and WC_Cart_Totals compatibility remains a tracked release risk. Those limits are intentionally not hidden by this receipt.

VERIFIED ENVIRONMENT

IMPLEMENTED / KNOWN LIMITS

WordPress 7.0.3 / WooCommerce 11.0.1 / PHP 8.2.12 / MariaDB 10.4.32

Return to the public build record.

The Build Ledger shows which Product 001 layers already have receipts and which work is still waiting.

Open Build Ledger

PerkRule support room

Real support works better when people can talk.

The PerkRule Discord will be the direct place for setup questions, bug reports, compatibility notes and release discussion. Useful answers should not disappear into private tickets — recurring problems can become documentation and Engineering Notes.

Discord opens around Product 001 release