Retail Loyalty Platform
ReactorCX: The Enterprise Retail Loyalty Platform, Across Every Format, Banner, and Point of Sale
Loyalty Methods runs ReactorCX, the enterprise loyalty platform built for retail at scale, across convenience, fuel, multi-brand apparel, franchise and dealer networks, and multi-format retailers. The dividing line in retail loyalty is whether the engine recognizes the same member in real time across every store, banner and point of sale, or stitches those identities together after the fact.
Promotion
Cross-banner bounce-back
v4Budget And Funding
60/40
Brand marketing · Banner
Attribution
Attributed at the line to the selling banner
Arbitration
Policy: best for businessStacks with loyalty reward: yes · Clearance SKUs excludedLimits
Per member: once per visitChannels: store, web, app · Returns reverse the accrualApproved by Brand Marketing Director · rolled out to Outlet after simulation
How this is measured
Member records migrated onto ReactorCX in the Gap Inc. Encore unification across Gap, Old Navy, Banana Republic and Athleta. As of February 2026.
How this is measured
7-Eleven stores in the US and Canada on which 7Rewards runs through ReactorCX, per 7-Eleven's public store count at the as-of date. As of 2026-Q3.
How this is measured
Distinct physical sites transacting through ReactorCX integrations, each counted once. As of 2026-Q3.
How this is measured
Distinct active promotions per month in the largest single retail deployment. As of 2026-Q3.
Definitions and as-of dates are on each figure.
How does ReactorCX run retail loyalty on one engine?
Most stacks stitch, and the seams show up where they cost the most: a point earned online that will not redeem in the store, a balance that lags a day behind the register, a franchise location running its own punch card while headquarters runs another. ReactorCX removes those seams.
Recognize one member across every banner and point of sale
- One canonical member profile resolved across card, app, web, POS and partner identifiers.
- Real-time eligibility calculated at the moment of the transaction rather than the morning after.
- A clean division of labor: ReactorCX owns who is a member, what they have earned and what they are eligible for; your ESP or SMS provider renders and sends the message.
- Deterministic accounting: every point traces to the rule, activity and member that created it, consumed in a configurable burn order, on an auditable history.
Run franchise and independently owned networks
- One member database with cross-store earn and burn: earn at any location, redeem at any location, and the end of store-siloed punch cards.
- Settlement between owners: a redemption funded by one owner and earned at another nets out correctly.
- A funding model agreed up front: central, franchisee-funded or hybrid, including ad-fund or co-op models.
- Provable, dated liability: outstanding points tracked, breakage flagged and recognized under standard rules, reporting by owner and rolled up for headquarters.
Run multi-format and grocery retail
A flagship banner, a value banner, a premium banner, a delivery brand, a pharmacy and fuel, each with its own economics, for one shopper who treats them as a single relationship. Rules at the department, category, brand and item level; cart-level arbitration across the full basket; household accounts with shared balances; pharmacy, fuel, delivery and curbside as first-class activity types. Grocery
Work for brands that do not own the point of sale
FeedXChange ingests activity from systems you do not operate, in real time or in batch. Consumer and trade programs share one engine without sharing rules, siloed by role. Registration, reviews and referrals keep the program alive between purchases that arrive every few years. Value beyond discounting: early access, exclusive products and recognition.
Independently owned, centrally connected
The operators keep their autonomy, the customer gets one program. Funded-value settlement is reconciled between owners and rolled up to headquarters, with liability tracked and dated by location.
What does multi-brand retail on ReactorCX look like?
ReactorCX runs four apparel brands, Gap, Old Navy, Banana Republic and Athleta, on one engine: a single profile and balance follows the shopper across every brand; points earned in one brand count across the portfolio; the Encore program extends redemption past markdowns into experiences and partner rewards; and a basket spanning multiple brands splits earning to the right brand, so each brand keeps clean economics while the shopper sees one program.
ReactorCX also runs distributed franchise and fuel networks in production at national scale, the same engine behind the franchise and settlement model above.
How this is measured
Active members across the four Gap Inc. brands at cutover. As of February 2026.
How this is measured
Elapsed months from kickoff to cutover for Gap Inc. Encore. As of February 2026.
What happens to one order
One activity, evaluated once, with every downstream effect recorded and published. The same path a demo walks through, in the order the engine runs it.
Purchased
Point of sale or the order system sends the order: member, banner, channel, every SKU line with category and brand, tender, promotion codes
Evaluated
SKU, category and brand rules, tier benefits and channel rules run in deterministic order against the whole order
Arbitrated
Loyalty rewards, promotions and coupons resolved to the best combination under the banner's policy before the total is shown
Accrued
Points to the member purse, tier credit to its track; each promotion's cost attributed to the banner and funding source at the line
Recorded
Execution log stores which rules fired and who approved them; liability moves by banner; a later return reverses from this same record
Published
Business events to CDP and messaging, replication events to the warehouse, order context back to the order system, ledger lines to finance
See this run on a copy of your own retail activity.
See a parallel migrationThe detail your team will want to check
Expand what you need.
ReactorCX speaks the retail data modelOne activity record, every dimension a retail program tracksReactorCX holds every event in one extensible record, so every field stays searchable and actionable across the console, the API, the warehouse and reporting. Add a field…
ReactorCX holds every event in one extensible record, so every field stays searchable and actionable across the console, the API, the warehouse and reporting. Add a field once and it propagates everywhere. Marketing, operations and finance query the same record the source system wrote.
Data model documentation
Core activity
Member ID · type · date · channel · value
Order and item
SKU · style · category · brand · banner · markdown flag · promotion code · tender
Channel and fulfilment
Store · web · app · marketplace · pickup in store · ship from store · return · exchange
Attribution and funding
Banner · campaign · funding source · partner · settlement party
Same engine, configured for retailWhat stays the same, and what adaptsReactorCX is one engine. What changes for a retail program is the signals it reads, the currencies it holds, the offers it arbitrates and the organisation it settles to. All of it is configuration, versioned and approved, not custom code.
| Dimension | Same in every industry | Configured for retail |
|---|---|---|
| Signal | One activity record per event, from any channel, evaluated once | Order with SKU lines from POS and e-commerce, returns and exchanges, marketplace sales, app and web activity |
| Currency | Any number of currencies and purses, each with source, expiry and burn order | Points; tier credit; brand or banner sub-balances where the program separates them |
| Status | Tiers with configurable qualification and requalification | Spend or visit tiers with annual requalification; member pricing and early access as tier benefits |
| Offers | Offer library with eligibility, stacking, suppression and limits | Central: SKU, category and brand rules, member pricing, promotion codes, basket-wide arbitration with clearance and markdown exclusions |
| Funding | Partner wallets, source-tagged accruals, settlement from lineage | Brand marketing and banner co-funding; partner and marketplace settlement |
| Organisation | Multi-brand, multi-region, per-entity economics on one instance | Banners and brands on one instance; store, e-commerce and marketplace channels; franchise stores as settlement parties |
| Servicing | Member Care Portal with line-level history and governed adjustments | Point-level history by order line; store and contact-centre adjustments and return reversals without escalation |
Other industries swap the signal and keep the engine: a grocer's basket, an airline's flown segment, a hotel's folio close. The engine and the ledger do not change. All industries
Returns, exchanges and cross-banner baskets that reconcile
Retail loyalty is undone by what happens after the sale. A return three weeks later, at a different banner, has to reverse exactly what was earned and exactly what was funded.
Reversal from the record
A return or exchange reverses the specific accrual and the specific promotion cost from the original activity, not an estimate. Partial returns reverse the affected lines only.
Mixed baskets settle at the line
A basket that crosses banners is attributed to each banner's P&L line by line, so no allocation rule is needed at period close.
Liability by banner
Outstanding value is reported per banner and per funding source from the same lineage, so each business unit sees its own number.
| Who looks | What they see | Where it comes from |
|---|---|---|
| Shopper | The reward on the receipt and the points earned, and the reversal if they return | Arbitration result and accruals on the activity |
| Merchandiser | Promotion redemptions and lift by SKU and banner against a control group | Promotion dashboards on the execution log |
| Banner finance | Promotion cost and liability for their banner | Line-level attribution in the ledger |
| Group finance | Liability across banners and the export to the general ledger | Ledger export at transaction level |
Partner wallets and settlement are documented in the partners and funding concept; the ledger in the ledger and lineage concept.
What each retail stakeholder will want to check
- Merchandising and brand marketingCan we run SKU, category and brand rules by banner and see lift by promotion?Capability map above; promotion dashboards with control groups
- FinanceDoes liability by banner reconcile, and do returns reverse cleanly?Financial integrity; the returns section above
- Store and e-commerce operationsDoes earn, burn and return work the same across store, web, app and marketplace?Organisation row above; POS guide and app and web guide
- IT and integrationHow do POS, the order system, the CDP and the warehouse connect?System map below; integration guides
- Loyalty and CX teamCan we change promotions and tiers without engineering?Marketer experience
How ReactorCX fits a retail estate
Store, web, app and call-center activity reaches ReactorCX through the same APIs, so a member sees one balance everywhere.
Promotions are arbitrated at the SKU level at checkout, and every accrual, redemption and expiry flows out as events and ledger records to the systems finance and merchandising already run.
Nothing here replaces a system you already run. Retail channels keep their own systems of record; ReactorCX holds the loyalty state, and publishes what it decides back to them.
Which ReactorCX capabilities matter most for retail?
Behavioral segmentation and targeting
Segment by spend, frequency, category, banner or channel, and personalize by lifecycle stage or predicted value, internally or by ingesting external segments. Personalization
Flexible program types
Points, tiers and invitation-only program types, with hidden and invite-only tiers, from one admin hub without development.
Member servicing
A 360 member view in the Member Care Portal lets store, contact-center and service teams check status, balances and history and handle merges, links and adjustments without escalation.
Analytics and exportable data
Pre-built dashboards, direct data warehouse access and streaming to your own CDP or BI tool, with a zero-PII data model where preferred.
Triggered communications
ReactorCX owns the logic and fires the event in real time off shopper activity; your ESP or SMS provider renders and delivers the message.
Catalog and named-list sync
FeedXChange keeps product, SKU, location and partner data current, and named product lists update running promotions automatically when the list refreshes.
Does ReactorCX work with the stack you already run?
ReactorCX is headless and API-first, so it integrates into the stack you already operate rather than replacing it. Loyalty is usually one of the last layers a brand adds, on top of POS, ecommerce, marketing and data systems, and ReactorCX is built to slot in there.
| Category | Systems and standards |
|---|---|
| Commerce and POS | In-store POS, ecommerce platforms, mobile app, kiosks |
| Marketing and messaging | ESP, SMS providers, marketing automation platforms |
| CRM and data | CDP, CRM, data warehouse, Snowflake, Databricks |
| Finance | Liability and breakage export, ERP integration, financial journaling |
| Partners | FeedXChange partner data exchange, partner-funded earn and burn |
| Open standards | API-first architecture, Kafka event streaming, webhooks, callbacks, OIDC SSO |
Integration patterns are documented in Integration Guides; the event catalog in Events.
Enterprise security
Is ReactorCX built to clear enterprise IT, procurement and compliance?
Built on AWS and cloud-native, with role-based access control and attribute constraints by brand, banner and owner; encryption in transit and at rest; OIDC single sign-on; audit trails across access, configuration changes and transactions; program-integrity controls (budgets, per-member limits, throttles, merge and unmerge handling); and privacy by design with tokenized-identifier and zero-PII modes. SOC 2 Type II and ISO/IEC 27001:2022, with dates and scope on the Trust Center.
Migration
How do retailers migrate a legacy loyalty program without downtime?
Loyalty Methods migrates legacy programs with SafeSwitch and ThreadSync, which run the legacy and target platforms in parallel until cutover rather than forcing a hard cut. Because the migration runs alongside live activity and validates against it before cutover, shoppers keep earning and redeeming through the switch, balances and historical transaction data carry over, and a replatform and a program redesign can happen in a single move.
Frequently asked questions
What is the best loyalty platform for retail?
ReactorCX, the enterprise loyalty platform from Loyalty Methods, is built for the way retail actually works: one shopper who appears across more banners, formats and channels than any single system was designed to watch. It resolves that shopper into one member profile across card, app, web, POS and partner identifiers, decides eligibility in real time at the transaction, reconciles funded value between independently owned stores, and runs multi-format and multi-brand portfolios on one instance. It powers enterprise multi-brand retail programs including Gap, Old Navy, Banana Republic and Athleta.
Can one platform run loyalty across multiple banners, formats and stores?
Yes. ReactorCX runs as one engine with format-specific and brand-specific rules, so a flagship banner, a value banner, a delivery brand, a pharmacy and fuel can each keep their own economics while a single shopper carries one identity and one balance across all of them.
How does ReactorCX handle franchise and independently owned retail networks?
Members earn at any location and redeem at any location from one database, and settlement logic reconciles funded value between owners, so a redemption funded by one owner and earned at another nets out correctly. Funding can be central, franchisee-funded or a hybrid, reporting is filtered by owner and rolled up for headquarters, and liability is tracked and dated by location.
Can ReactorCX recognize a shopper in real time at the register?
Yes. ReactorCX is a real-time, event-driven engine with synchronous responses, so it recognizes a shopper and returns eligibility, balances and offers in the moment at the point of sale, including a printout of what they earned on the receipt where the POS supports it. It handles returns, adjustments, account merges and partner activity while keeping an accurate member state.
Want to see ReactorCX for your formats and banners?
The shopper was always one person. The engine underneath should be too. Walk through your formats, banners and franchise model with the team behind enterprise retail loyalty at scale.