Your customer does not divide your brand into an ecommerce business, a branch network and an app. They expect the points earned in one place to mean something in the next. The architecture behind loyalty should respect that expectation.
The real decision is where the balance lives
An independent loyalty ledger is a record of earning, redemption, expiry, reversal and adjustment that sits outside any single sales channel. The website, POS and app send it transactions and request authorised reward actions. They can display a balance without each becoming a separate source of truth.
This is not the general ledger used for the company's accounts. Finance still needs an agreed reconciliation process and accounting treatment. Nor does external mean uncontrolled: access, data ownership, service levels and export rights still need to be defined. The useful separation is from the sales channel, not from business responsibility.
Magento, WordPress and Shopify: what is the limitation?
An ecommerce-bound loyalty feature can be a sensible starting point for a business that operates in one environment. It becomes the wrong foundation when the brand needs a wider program and the chosen implementation cannot support it. The problem is the boundary of the implementation, not the name of the ecommerce platform.
Magento and Adobe Commerce should not be treated as identical editions. Adobe documents reward-point functionality for Adobe Commerce, including balance history and website scope. For a Magento implementation, check the edition and extension actually being proposed. Native or extension-based functionality is not, by itself, proof that a separate POS estate and mobile app share an authoritative balance.
WordPress is the underlying publishing platform; WooCommerce supplies ecommerce functionality. The official WooCommerce Points and Rewards documentation describes purchase points redeemable for discounts and states that multisite installations have separate balances for each site. That is a concrete limitation of that extension, not a claim about every WordPress loyalty product.
Shopify supports a third-party loyalty ecosystem, and Shopify documents loyalty app access from POS checkout. Some services available through Shopify already operate across channels. Calling all Shopify loyalty apps unsuitable would be inaccurate. Ask whether the selected service can support your other channels independently, including a future move away from Shopify.
What a shared ledger changes
Imagine a customer earning online, redeeming in a branch and returning part of the original order. With separate balances, every handoff needs an agreement about which system is correct. With one authoritative ledger, the channels refer to the same transaction history and apply agreed rules to the same relationship.
That does not make the integration automatic. Customer identity must be matched safely. Orders need unique references. Repeated notifications must not award the same points twice. Redemptions need protection against simultaneous spending, and refunds need a traceable link to the original earning event. These are acceptance criteria to test, not benefits to assume from a diagram.
- One customer identity strategy across participating channels.
- One authorised record of reward transactions and reversals.
- Explicit rules for pending points, refunds, expiry and adjustments.
- A reconciliation process that can explain differences by channel.
Independence is valuable when the business changes
A brand may replace its ecommerce platform, add a delivery app or acquire stores running another POS. If the reward record is inseparable from the old storefront, migration can become a customer-service project as well as a technical one. An independent service can reduce that coupling, provided the new channels can integrate with it and the contract gives you usable access to your data.
Independence also creates a dependency of its own. If the central service is unavailable, the channels need a documented policy. Can earning wait in a queue? Must redemption stop? How will staff explain the interruption? Test recovery and reconciliation after an outage. A shared service without an operational plan is not a complete solution.
The decision to make before you buy
Ask the vendor to demonstrate a cross-channel purchase, redemption and partial return, then replay an event and attempt a duplicate redemption. Ask for a sample transaction export and a clear explanation of what remains available if you replace the storefront. A connector logo is not a substitute for those tests.
For a single-store ecommerce business, a well-chosen plugin may remain the most proportionate option. For an omnichannel brand, our recommendation is to make the loyalty relationship independent of any one checkout. Let Magento, WooCommerce, Shopify, the POS and the app do their channel jobs. Give them a shared loyalty record they can trust.
Original editorial imagery created with AI for this series. Images are illustrative; people shown are not customer endorsements.
Put the thinking to work.
Bring one customer journey and your current systems. Let’s explore what a connected loyalty program would need to do for your brand.
Book a demo
