Developer guide · WooCommerce
Connect WooCommerce without adding a loyalty plugin.
The early-access path links a store to the complete Reward Loyalty application. It uses WooCommerce interfaces, while the installation operator owns setup and operations.
- Source sale
- WooCommerce order
- Order input
- Signed update webhook
- Reward output
- Restricted store coupon
Short answer
Connect orders without hiding the ownership work.
Reward Loyalty has an early-access WooCommerce integration that uses a WooCommerce REST API key and a signed order webhook. The processor resolves the billing email, awards points when the order reaches the configured status, and can claw back the supported full-refund value. A separate points-to-coupon flow creates a single-use, email-restricted store coupon. Reward Loyalty supplies no WordPress plugin; the operator connects and runs the complete application.
Decision criteria
Design the order and coupon lifecycle together.
Store credentials, order status, billing identity, refund scope, coupon creation, and reconciliation all affect the production contract.
Award status
Choose whether the store should award at its configured paid-processing point or after completion. Test the payment gateway and fulfilment workflow that sets those states.
Identity and consent
Use the order billing email for member matching. A store purchase can support loyalty updates under the documented workflow; it does not grant offers-and-news consent.
Coupon policy
Set the points conversion, bounds, expiry, and support path. Decide how staff resolve an expired or unused coupon after points have left the member balance.
Connection model
Use WooCommerce REST and webhook interfaces.
The store and Reward Loyalty remain separate applications with a controlled credential and event handoff.
Systems involved
WooCommerce owns product, cart, payment, tax, order, refund, and coupon records. Reward Loyalty owns the loyalty member, linked card, points ledger, integration receipts, and role interfaces.
Authentication
The partner creates a WooCommerce REST API key with the documented access and submits the key pair through the partner workflow. Reward Loyalty stores the credential material in its encrypted integration field.
Webhook setup
The connection registers the current order-update webhook where the store permits it. The operator can use the documented manual fallback when automatic registration is unavailable.
Branding scope
White-label relevance: Supporting. Installation and business branding can align customer-facing loyalty surfaces. WordPress theme work, store email, source changes, and update responsibility stay with the buyer.
Order and identity
Award from a supported store state.
A store order is the source transaction; the loyalty ledger records the consequence.
Write direction
A signed order update enters the native processor. The configured order status can award points against a store-scoped order reference.
Member identity
The processor normalizes the billing email, matches an existing member or creates one, and attaches the linked card. Missing billing email causes the order to be skipped.
Duplicate handling
The delivery ID and integration-scoped order reference protect the native path from a repeated store webhook or a later status update awarding the same order again.
Read and notification direction
Operators inspect integration activity, receipts, members, and transactions in Reward Loyalty. Loyalty outbound webhooks remain a separate notification path for other systems.
Refund and coupon redemption
Make the cross-system order of work explicit.
A coupon and a points deduction must not drift into two independent promises.
Full refund
When refund deduction is enabled, a fully refunded order can claw back the points tied to the order, including the recorded welcome value from that order.
Partial refund
A partial refund does not move the order into the supported full-refund path. The operator must review and correct loyalty value under a documented policy.
Coupon creation
The redemption service validates the member and balance, creates a fixed-cart coupon in WooCommerce, then deducts points under a locked loyalty transaction. The coupon is single-use and email-restricted.
Failure consequence
If point deduction fails after coupon creation, the service attempts to delete the new coupon. Coupon expiry or non-use does not restore points, so support and reconciliation need the store and loyalty references.
Production controls
Operate credentials, webhooks, and queue work.
A connected status proves credential access at one moment, not an enduring order pipeline.
-
1
Test the store
Use safe records to test valid and invalid signatures, configured award states, a repeated delivery, a missing billing email, a full refund, a partial refund, coupon creation, and a forced coupon or deduction failure.
-
2
Choose execution mode
Webhook processing can run in the request or on the configured queue. When the queue is enabled, monitor workers, queued receipts, failed jobs, and integration errors.
-
3
Pause and disconnect with intent
A paused integration skips processing and does not imply historical backfill. On disconnect, remove the connection and revoke the WooCommerce key at the store.
-
4
Reconcile and rotate
Compare store order, delivery, refund, and coupon records with receipts, loyalty transactions, activity logs, and member support cases. Rotate exposed keys and retest after store or source changes.
Product and operating limits
Do not treat the connection as a WordPress plugin.
- The WooCommerce integration is early access. Confirm the current feature setting, store version behavior, permissions, and maintained documentation before launch.
- Reward Loyalty does not ship a WordPress loyalty plugin, hosted WooCommerce service, universal theme component, or managed store setup.
- Partial refunds and unused or expired coupon recovery require an operator policy. Paused processing does not promise a later backfill.
Implementation guides
Use current documentation for changing details.
Requirements, interfaces, settings, limits, and release behavior belong in the maintained product documentation.