ENGINEERING

The technical layer, when you actually want it.

Most merchants should not need an architecture lecture to decide whether a promotions app is useful. Agencies and technical buyers can inspect the deeper decisions here.

CHECKOUT

A PerkRule server should not sit between a shopper and the order button.

Promotion evaluation and storefront behavior run from the installed WooCommerce app. Account, licensing and update services stay outside the synchronous cart and checkout path.

WOO OWNERSHIP

WooCommerce keeps owning the store data and behavior it already owns.

Products, orders, cart state, validation and native discount arithmetic stay with WooCommerce. PerkRule adds the promotion workflow around that foundation instead of duplicating it.

COMPATIBILITY

Compatibility controls select shipped behavior; they do not inject arbitrary remote code.

Installed code can use supported adapters, fallbacks and circuit breakers. New executable behavior still arrives through a release.

Need implementation detail?

Use the docs and engineering notes when the merchant-facing explanation is not enough.

Open docs