Engineering Receipt / Native Ownership
WooCommerce owns the coupon.
PerkRule extends native WooCommerce coupons instead of replacing them with a parallel coupon domain model.
Coupon identity, native restrictions, usage, expiry and discount calculation already have a canonical home in WooCommerce. Duplicating that model would create synchronization risk and weaker ecosystem compatibility.
IMPLEMENTATION
How the claim is implemented.
PerkRule extends native WooCommerce coupons instead of replacing them with a parallel coupon domain model.
Implementation point
WC_Coupon is the persistence boundary for coupon data PerkRule does not own.
Implementation point
PerkRule metadata is limited to concepts WooCommerce does not natively represent, such as application mode, rule definition, priority and stacking configuration.
Implementation point
Coupon creation, update, duplicate, enable, disable, trash, restore and delete paths use native WooCommerce coupon persistence rather than a parallel coupon table.
Implementation point
Native coupon description and status remain authoritative instead of being mirrored into PerkRule metadata.
EVIDENCE
What currently supports the claim.
Coupon identity, native restrictions, usage, expiry and discount calculation already have a canonical home in WooCommerce. Duplicating that model would create synchronization risk and weaker ecosystem compatibility.
Verification evidence
Real WooCommerce integration coverage includes coupon collisions, trash/restore behavior and persistence rollback paths.
Verification evidence
Coupon-code lookup was hardened around WooCommerce datastore behavior without introducing a second coupon index owned by PerkRule.
Verification evidence
HPOS compatibility is treated as an official platform requirement; order data is not modeled through legacy postmeta assumptions.
KNOWN BOUNDARY
What this receipt does not claim yet.
This receipt proves the ownership model used by the current development branch. It does not claim compatibility with every WooCommerce extension until the compatibility lab is complete.
VERIFIED ENVIRONMENT
VERIFIED IN CORE
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 LedgerPerkRule 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