Fuel and Convenience Loyalty Platform
ReactorCX: The Enterprise Fuel and Convenience Loyalty Platform
Loyalty Methods runs ReactorCX, the enterprise loyalty platform behind fuel and convenience programs at 7-Eleven, Speedway, bp, Amoco, ampm, Stripes, TravelCenters of America and Thorntons. ReactorCX is built for the one split that defines the vertical: thin-margin fuel at the pump, high-margin goods inside, and a member who moves between them in ninety seconds.
Promotion
Fuel-to-store bounce-back
v7Funding Split
50/50
Fuel brand · Site owner
Billing
Billing: per site · monthly dealer statement
Arbitration
Policy: best for customerStacks with card offer: no · Cents off per gallon capped per fillLimits
Window: three days after the fillPer member: once a day · Dealer sites: settle to ownerApproved by Fuel Marketing · dealer council notified
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
bp and Amoco fuel locations transacting through ReactorCX.
How this is measured
Fuel brands unified in the bp Earnify program on ReactorCX.
How this is measured
Distinct physical sites transacting through ReactorCX integrations, each counted once. As of 2026-Q3.
Definitions and as-of dates are on each figure.
Vertical figures are subsets of platform totals.
How does ReactorCX turn a fuel fill into a store visit?
Fuel margins are thin. In-store margins are not. Loyalty's job is to move fuel customers into the store. A member fills up but never comes inside, and there is no way to act on the fuel transaction while it is happening. By the time batch data catches up, they have already driven off.
- Real-time pump event processing: the fuel purchase triggers offer evaluation the moment it happens.
- Cross-line-of-business bouncebacks: "you just filled up, get bonus points on any in-store purchase in the next thirty minutes."
- Mobile push at the pump while the member is still on the forecourt.
- Trigger promotion engine evaluates every eligible promotion at the pump transaction.
How does ReactorCX handle peak transaction volume?
Morning commute and holiday travel spike transactions three to four times. The platform has to recognize the member and apply cents-off-per-gallon at the pump without adding a second of friction. Real-time forecourt decisioning means recognition and redemption at the pump as it happens, proven in continuous production at enterprise scale across 7-Eleven and Speedway.
How does ReactorCX unify corporate, franchise and dealer locations?
- Multi-layer program governance: corporate, region, franchise and location rules in one hierarchy.
- Bulk data ingestion across the point-of-sale systems in the network.
- Dual-program architecture: two brands on one engine with visibility controls.
- API-first integration that works with both legacy and target POS during a multi-year migration window.
Proof: bp runs one loyalty and discounting program unifying five US brands (bp, ampm, Amoco, Thorntons, TravelCenters of America) across sites on different underlying systems. Speedway moved off a legacy platform with SafeSwitch and ThreadSync and runs alongside 7-Eleven on the same engine.
How does ReactorCX run cents-off-per-gallon as a currency?
- Native currency earned and redeemed at the pump or in store alongside points.
- Spend tiers that roll fuel and c-store spend through the aggregates engine for real-time eligibility.
- Multi-currency redemption on the same transaction.
- Co-brand accrual on every linked-card purchase.
How does ReactorCX resolve overlapping offers at the register?
A convenience network runs hundreds of overlapping offers at once. ReactorCX resolves the whole offer universe at the register, in real time and by your policy: best for customer, best for business, priority order, or explicit override. Full discount library (percentage off, dollar off, BOGO, mix-and-match, combos); arbitration runs at the point of sale for every transaction, not only for enrolled members.
What happens to one fill
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.
Fuelled
The forecourt controller sends the pump transaction: site, owner type, grade, gallons, tender, and the member identified at the pump or in the app
Evaluated
Grade and site rules, store-visit rules, card and partner rules, owner-specific rules run in deterministic order
Arbitrated
Cents off per gallon, store offers and card offers resolved to the best combination under the brand's policy at the pump
Accrued
Cents off to the fuel purse, points to the member purse; the owner-funded share attributed to the site that funds it
Recorded
Execution log stores which rules fired and who approved them; liability moves by site owner; the settlement position moves by the funded share
Published
Site systems and the app updated, business events to CRM, replication events to the warehouse, ledger lines to finance, funded lines to dealer statements
See this run on a copy of your own fuel and convenience activity.
See a parallel migrationThe detail your team will want to check
Expand what you need.
ReactorCX speaks the fuel and convenience data modelOne activity record, every dimension a fuel and convenience 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
Forecourt and store
Site · pump · grade · gallons · store basket lines · car wash · tender · identification method
Ownership and network
Corporate · franchise · dealer · region · brand · site owner
Funding and settlement
Fuel brand · supplier · card partner · owner share · settlement party
Same engine, configured for fuel and convenienceWhat stays the same, and what adaptsReactorCX is one engine. What changes for a fuel and convenience 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 fuel and convenience |
|---|---|---|
| Signal | One activity record per event, from any channel, evaluated once | Pump transactions from the forecourt controller, store baskets from POS, car wash, app and pay activity, card and partner feeds |
| Currency | Any number of currencies and purses, each with source, expiry and burn order | Cents off per gallon as a currency alongside points; per-fill caps; multi-currency redemption on one transaction |
| Status | Tiers with configurable qualification and requalification | Usually visit or gallon based, often replaced by offer depth; requalification by activity |
| Offers | Offer library with eligibility, stacking, suppression and limits | Central: fuel-to-store and store-to-fuel bounce-backs, time-boxed offers, arbitration at the pump and the register including card offers |
| Funding | Partner wallets, source-tagged accruals, settlement from lineage | Fuel brand, supplier and card partner funding; owner share per site |
| Organisation | Multi-brand, multi-region, per-entity economics on one instance | Corporate, franchise and dealer sites as settlement parties; regions and brands on one instance |
| Servicing | Member Care Portal with line-level history and governed adjustments | Point-level history by fill and basket; site and contact-centre adjustments 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
One program, per-site accounting
A fuel network is a mix of sites the brand owns and sites it does not. Every earn and burn has to be attributed to the site that funds it, or the dealer relationship breaks.
Every earn tagged to its funder
Each accrual and each redemption carries the site, the owner and the funding split, applied at the pump, so the owner's share is known when the transaction settles.
Dealer statements from the ledger
Monthly owner statements are generated from lineage, line by line, and match what the dealer's own systems recorded.
Liability by owner
Outstanding cents off and points are reported by site owner and region, so corporate and dealer books each carry their own number.
| Who looks | What they see | Where it comes from |
|---|---|---|
| Customer | The cents off at the pump and the points earned in the store | Arbitration result and accruals on the activity |
| Dealer or site manager | A monthly statement of funded lines for their sites | Owner wallet, generated from lineage |
| Fuel marketing | Bounce-back redemptions and lift by site against a control group | Promotion dashboards on the execution log |
| Finance | Liability by owner and region and the settlement position 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 fuel and convenience stakeholder will want to check
- Fuel and convenience marketingCan we run bounce-backs across pump and store and see lift by site?Capability map above; promotion dashboards
- FinanceDoes liability by owner reconcile, and do dealer statements match?Financial integrity; the per-site section above
- Dealer and franchise relationsDo owners see their share at the line and settle without disputes?Organisation row above; partners and funding
- Forecourt and store ITHow do the forecourt controller, POS and the app connect in real time?System map below; POS and forecourt guide
- Store operationsCan store staff see and adjust a customer's balance at the counter?Member Care Portal
How ReactorCX fits a fuel and convenience estate
Pump, in-store, mobile-pay and partner activity all arrive as real-time activities.
ReactorCX holds fuel discounts as a currency, resolves overlapping offers at the register, and attributes every earn and burn to the corporate, franchise or dealer site that funds it before publishing events and ledger records downstream.
Nothing here replaces a system you already run. Fuel & Convenience channels keep their own systems of record; ReactorCX holds the loyalty state, and publishes what it decides back to them.
Which capabilities matter most for fuel and convenience?
Product and location group management
Rules by product group, site group, region and banner.
Gamification
Fuel-up streaks, visit challenges and milestone rewards. Gamification
Geo-targeted offers
Offers by site and proximity through the location API, with the nearest redeemable offers shown first. Personalization
Real-time transaction preview
Projected earn and discount shown at the pump before the transaction commits.
Member servicing and disputes
Member Care Portal backed by per-activity execution logs. Member Care
Source-tagged points and partner settlement
Franchise-level P&L and co-brand settlement from the same lineage. Financial Integrity
Does ReactorCX work with the stack you already run?
| Category | Systems and standards |
|---|---|
| Forecourt and POS | Verifone, NCR, forecourt controllers, kiosks, mobile app |
| CRM and data | Adobe, Tealium, Amperity, Snowflake, Databricks, Redshift |
| Marketing clouds | Adobe Journey Optimizer, Salesforce Marketing Cloud, Braze |
| Partners | FeedXChange partner data exchange; co-brand and fuel partners; vendor-funded offers |
| Open standards | API-first, Kafka event streaming, webhooks, callbacks, OIDC SSO |
FeedXChange unifies data from dozens of different point-of-sale systems. Integration patterns are documented in Integration Guides.
Enterprise security
Is ReactorCX built to clear enterprise IT and procurement?
Built on AWS and cloud-native, with role- and attribute-based access control, encryption in transit and at rest, OIDC single sign-on, audit trails across access, configuration and transaction activity, and two privacy modes including tokenized identifiers. SOC 2 Type II attestation and ISO/IEC 27001:2022 certification, with dates and scope on the Trust Center.
Migration
How did 7-Eleven move to ReactorCX?
With SafeSwitch and ThreadSync. 7Rewards was the first enterprise program migrated this way, running the legacy and target platforms in parallel and validating against live activity before cutover. Members kept earning and redeeming through the switch.
Frequently asked questions
What is the best loyalty platform for fuel and convenience retailers?
ReactorCX runs fuel and in-store loyalty on one engine, decides at the pump in real time, and unifies corporate, franchise and dealer locations across the point-of-sale systems they run. It powers programs at 7-Eleven, Speedway, bp, Amoco, ampm, Stripes and TravelCenters of America.
How does ReactorCX turn a fuel fill into an in-store visit?
The fuel purchase triggers offer evaluation the moment it happens. Cross-line-of-business bouncebacks and mobile push at the pump reach the member while they are still on the forecourt, before batch data would have caught up.
Can one program run across multiple banners and POS systems?
Yes. Multi-layer program governance runs corporate, region, franchise and location rules in one hierarchy, and FeedXChange unifies data from many different point-of-sale systems. bp runs one loyalty and discounting program across five US brands on different underlying systems.
How did 7-Eleven migrate to ReactorCX?
With SafeSwitch and ThreadSync. 7Rewards was the first enterprise program migrated this way, running the legacy and target platforms in parallel and validating against live activity before cutover.
See a fuel and convenience program run in real time.
Pump events, in-store bouncebacks, cents-off-per-gallon and arbitration at the register, configured for your network.