> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/eps-loyalty/configuring-eps-loyalty/shell-loyalty-stacking-in-fuel-transaction.md).

# Shell Loyalty Stacking In Fuel Transaction

## Quick Reference Summary

<table><thead><tr><th width="235" valign="top">Topic</th><th valign="top">Summary</th></tr></thead><tbody><tr><td valign="top">What this feature does</td><td valign="top">Enables loyalty stacking — multiple loyalty discounts in one fuel transaction — for Shell sites.</td></tr><tr><td valign="top">Shell Primary Loyalty</td><td valign="top">Fuel Rewards Network (FRN) — payment-based. Can be combined with ANY other discount.</td></tr><tr><td valign="top">Shell Secondary Loyalty</td><td valign="top">Third-party partner programme (e.g., Kroger, Jacksons) hosted by Shell EPS. One per transaction. Stacks with Fuel Rewards.</td></tr><tr><td valign="top">Local / Commander Loyalty</td><td valign="top">Site-managed loyalty (programme IDs 1001+). Can stack with Fuel Rewards but NOT with Shell secondary in the same transaction.</td></tr><tr><td valign="top">POP Discount</td><td valign="top">Site-level per-gallon promotion. Applied first, before any loyalty programme discount.</td></tr><tr><td valign="top">Priority order</td><td valign="top">1 — POP Discount 2 — Local loyalty 3 — Shell Secondary 4 — Shell Primary (Fuel Rewards)</td></tr><tr><td valign="top">Scenario 1</td><td valign="top">POP Discount + Local Loyalty + Shell Primary (Fuel Rewards) — no secondary programme.</td></tr><tr><td valign="top">Scenario 2</td><td valign="top">POP Discount + Shell Secondary (partner) + Shell Primary (Fuel Rewards) — stacked.</td></tr><tr><td valign="top">Customer action required</td><td valign="top">None. Customers pay as normal. Stacking is automatic.</td></tr><tr><td valign="top">Cashier action required</td><td valign="top">None. Stacking is handled automatically by Commander and Shell EPS.</td></tr><tr><td valign="top">How to enable</td><td valign="top">Turn on 'Multiple Loyalty Enabled' in the Commander back-office. Only for sites with new Shell EPS.</td></tr><tr><td valign="top">Old Shell EPS sites</td><td valign="top">Leave 'Multiple Loyalty Enabled' off. Standard single-loyalty mode. No impact.</td></tr><tr><td valign="top">Reports</td><td valign="top">POS loyalty report shows each programme's discount separately per transaction.</td></tr><tr><td valign="top">Applies to</td><td valign="top">Outdoor pump (DCR/OPT), indoor POS, self-checkout (SCO), and VISTA devices.</td></tr><tr><td valign="top">Available from</td><td valign="top">Base 057.01.00.</td></tr></tbody></table>

Shell has enhanced its loyalty programme by introducing loyalty stacking — the ability to apply multiple loyalty discounts to a single fuel transaction. Commander now supports this capability, allowing Shell sites to reward customers through a combination of Shell's own Fuel Rewards programme and one or more third-party partner loyalty programmes in a single fill-up.

This feature is part of Shell's strategic initiative to broaden its loyalty offering and strengthen its partnership with retailers and loyalty providers. From a customer's perspective, it means they can save more at the pump by earning discounts from multiple programmes simultaneously — without needing to choose between them.

{% hint style="info" %}
ℹ Note: Shell Third Party Loyalty Stacking is available from Base 057.01.00. It applies to Shell-branded sites where loyalty stacking has been enabled through the back-office configuration. Sites running an older Shell EPS version continue to operate in standard single-loyalty mode.
{% endhint %}

## Key Concepts — Understanding Loyalty Stacking

Before walking through how the feature works, here is a plain-English explanation of the loyalty programmes and terms involved:

<table><thead><tr><th width="215" valign="top">Term</th><th valign="top">What It Means</th></tr></thead><tbody><tr><td valign="top">Shell Primary Loyalty (Fuel Rewards Network / BSL)</td><td valign="top">Shell's flagship loyalty programme — Fuel Rewards Network (FRN). Customers earn cents-per-gallon savings by using a qualifying Shell credit card, gift card, or registered Fuel Rewards account. This discount is payment-based, meaning it is linked to how the customer pays, and it can be combined with any other discount in the same transaction.</td></tr><tr><td valign="top">Shell Secondary Loyalty (Third-Party Partner Programme)</td><td valign="top">A loyalty programme run by a third-party retailer or partner (for example, Kroger, Jacksons/Paytronix, or another partner) that has an agreement with Shell. Customers who belong to this partner programme earn a per-gallon discount at Shell stations. Only one secondary loyalty programme can be active in a single transaction.</td></tr><tr><td valign="top">Local / Commander Loyalty</td><td valign="top">Loyalty programmes managed directly by the Commander site controller — for example, a store-branded loyalty card or a site-specific points programme. These are separate from Shell's own loyalty programmes and are configured locally on Commander.</td></tr><tr><td valign="top">POP Discount (Point-of-Purchase)</td><td valign="top">A per-gallon discount applied at the time of the transaction, configured at the site level. Examples include a carwash discount, a site-specific promotional discount, or a daily special. POP discounts are site-driven and apply before loyalty programmes are calculated.</td></tr><tr><td valign="top">Loyalty Stacking</td><td valign="top">Combining multiple discounts — from different loyalty programmes and/or site discounts — in a single transaction. Instead of getting just one discount, the customer receives all applicable discounts applied in a defined order.</td></tr><tr><td valign="top">Shell EPS (Electronic Payment System)</td><td valign="top">Shell's payment and loyalty processing server. It communicates with Commander to authorise payments, deliver loyalty programme information, and calculate stacked discounts. The EPS hosts the third-party partner loyalty programmes (secondary loyalty).</td></tr><tr><td valign="top">Loyalty Stacking Enabled flag</td><td valign="top">A configuration setting in Commander's back-office that controls whether a site participates in Shell's loyalty stacking programme. Sites must have this setting enabled to receive stacked discounts from Shell EPS.</td></tr></tbody></table>

## How Loyalty Stacking Works

When a customer fuels at a Shell site with loyalty stacking enabled, Commander and Shell EPS work together to identify all applicable loyalty discounts and apply them in the correct order — automatically. The customer does not need to do anything differently at the pump.

<table data-header-hidden><thead><tr><th width="109"></th><th width="219" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td>1</td><td valign="top">Customer initiates fuelling</td><td valign="top">The customer lifts the nozzle or starts a transaction at the pump or indoor POS. They may present a loyalty card, use a Shell gift card, swipe a Fuel Rewards-linked card, or use any other accepted payment method.</td></tr><tr><td>2</td><td valign="top">Commander contacts Shell EPS</td><td valign="top">Commander sends the transaction details to Shell EPS for payment authorisation. Because Commander is now registered as 'Multiple Loyalty Capable', Shell EPS knows it can send back more than one loyalty programme discount for this transaction.</td></tr><tr><td>3</td><td valign="top">Shell EPS identifies applicable discounts</td><td valign="top">Shell EPS checks what loyalty programmes apply to this customer and this transaction. It may identify the customer's Fuel Rewards discount (primary loyalty), a partner programme discount such as Kroger or Jacksons (secondary loyalty), or a combination of both — stacked together.</td></tr><tr><td>4</td><td valign="top">Discounts are applied in priority order</td><td valign="top">Commander receives the loyalty information from Shell EPS and applies all discounts in Shell's defined priority order (see next section). Each discount reduces the per-gallon price, and the final price the customer pays reflects all applicable savings combined.</td></tr><tr><td>5</td><td valign="top">Customer pays the discounted price</td><td valign="top">Fuel is dispensed at the fully discounted per-gallon price. The customer sees the savings on the pump display and on the receipt. All discounts are itemised separately on the transaction record.</td></tr><tr><td>6</td><td valign="top">Transaction is recorded in Commander</td><td valign="top">Commander records all loyalty programmes that contributed to the transaction, each identified separately by programme. Site loyalty reports show a breakdown of each programme's contribution.</td></tr></tbody></table>

{% hint style="success" %}
✔ Good to know: The customer experience at the pump is unchanged. Customers still make one loyalty programme selection (if prompted). The stacking of primary and secondary discounts happens automatically in the background between Commander and Shell EPS.
{% endhint %}

## Discount Priority Order

When multiple discounts apply to a single transaction, they are applied in the following order. The order is defined by Shell and is applied consistently across all Shell sites with loyalty stacking enabled. Lower numbers are applied first.

<table><thead><tr><th width="110" valign="top">Priority</th><th width="144" valign="top">Discount Type</th><th width="181" valign="top">Source</th><th valign="top">Example</th></tr></thead><tbody><tr><td valign="top">1</td><td valign="top">POP Discount</td><td valign="top">Configured on-site in Commander</td><td valign="top">A carwash discount, daily site promotion, or any point-of-purchase per-gallon reduction set up in the site's back-office.</td></tr><tr><td valign="top">2</td><td valign="top">Local / Commander Loyalty</td><td valign="top">Commander loyalty programme</td><td valign="top">A store-branded loyalty card or site-specific points programme managed locally on Commander (programme IDs starting from 1001).</td></tr><tr><td valign="top">3</td><td valign="top">Shell Secondary Loyalty (Third-Party Partner)</td><td valign="top">Shell EPS — partner programme</td><td valign="top">Kroger loyalty, Jacksons/Paytronix, or another Shell partner programme. The customer earns a discount through the partner retailer's loyalty scheme, redeemable at Shell.</td></tr><tr><td valign="top">4</td><td valign="top">Shell Primary Loyalty (Fuel Rewards Network)</td><td valign="top">Shell EPS — Fuel Rewards</td><td valign="top">Shell Fuel Rewards (FRN) — earned via Shell gift card, Shell-branded credit card, or a registered Fuel Rewards account. Applied last because it is payment-based.</td></tr></tbody></table>

{% hint style="danger" %}
⚠ Important: Shell secondary loyalty (a third-party partner programme) and a local Commander loyalty programme cannot both be active in the same transaction. Only one of the two can apply per transaction. Shell primary loyalty (Fuel Rewards) can always be combined with any other discount.
{% endhint %}

## The Two Stacking Scenarios

Shell defines two standard transaction scenarios where stacking applies. Your site will follow one or both depending on the loyalty programmes your customers hold and the promotions active at your site.

**Scenario 1 — POP Discount + Local Loyalty + Shell Primary (Fuel Rewards)**

This scenario applies when a customer has a Fuel Rewards account and your site has a POP discount active, and the customer also holds a local Commander loyalty card. No Shell secondary (third-party partner) programme is involved.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Discount 1 — Applied First</td><td valign="top">Discount 2 — Applied Second</td><td valign="top">Discount 3 — Applied Third</td></tr><tr><td valign="top">POP Discount (site-level promotion)</td><td valign="top">Local / Commander Loyalty (store loyalty card)</td><td valign="top">Shell Primary Loyalty (Fuel Rewards / Shell gift card)</td></tr><tr><td valign="top">Example: 5¢/gal carwash discount</td><td valign="top">Example: 3¢/gal store points reward</td><td valign="top">Example: 10¢/gal Fuel Rewards saving</td></tr></tbody></table>

In this example, the customer saves a combined 18¢ per gallon — all three discounts applied automatically in the correct order.

**Scenario 2 — POP Discount + Shell Secondary (Partner) + Shell Primary (Fuel Rewards)**

This scenario applies when a customer has both a Fuel Rewards account and a qualifying Shell partner loyalty programme (such as Kroger or Jacksons), and your site has a POP discount active. Both Shell programmes stack together.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Discount 1 — Applied First</td><td valign="top">Discount 2 — Applied Second</td><td valign="top">Discount 3 — Applied Third</td></tr><tr><td valign="top">POP Discount (site-level promotion)</td><td valign="top">Shell Secondary Loyalty (Kroger, Jacksons, or other partner)</td><td valign="top">Shell Primary Loyalty (Fuel Rewards / Shell gift card)</td></tr><tr><td valign="top">Example: 5¢/gal carwash discount</td><td valign="top">Example: 15¢/gal Kroger rewards</td><td valign="top">Example: 10¢/gal Fuel Rewards saving</td></tr></tbody></table>

In this example, the customer saves a combined 30¢ per gallon. Note: in Scenario 2, there is no local Commander loyalty — it is replaced by the Shell secondary partner programme.

## Shell Loyalty Programmes — Reference

Shell EPS identifies each loyalty programme by a Programme ID number. Commander uses these IDs to determine which programmes are active in a transaction and how to apply them. The table below shows the current programme IDs in use:

<table><thead><tr><th valign="top">Programme ID</th><th valign="top">Programme Name</th><th valign="top">Stacked combination</th><th valign="top">Behaviour</th></tr></thead><tbody><tr><td valign="top">1 + 4</td><td valign="top">Stacking — Fuel Rewards + EPS Secondary</td><td valign="top">Stacked combination</td><td valign="top">Both programmes are active and applied together. The customer earns savings from both FRN and the partner programme in the same transaction.</td></tr><tr><td valign="top">2</td><td valign="top">Fuel Rewards Network (FRN)</td><td valign="top">Shell Primary</td><td valign="top">Shell's main loyalty programme. Applied when the customer pays with a Fuel Rewards-linked card or Shell gift card. Can be combined with any other discount.</td></tr><tr><td valign="top">3</td><td valign="top">Kroger loyalty</td><td valign="top">Shell Secondary</td><td valign="top">Discount earned through the Kroger loyalty programme at Shell stations. Stacks with Fuel Rewards (primary) when both are present.</td></tr><tr><td valign="top">4</td><td valign="top">EPS Secondary Programme</td><td valign="top">Shell Secondary</td><td valign="top">A Shell-hosted third-party loyalty programme. Stacks with Fuel Rewards (primary) when both are present.</td></tr><tr><td valign="top">1001+</td><td valign="top">Local / Commander Loyalty</td><td valign="top">Commander-managed</td><td valign="top">Loyalty programmes managed on Commander locally (not via Shell EPS). Can coexist with Shell primary loyalty but not with Shell secondary in the same transaction.</td></tr></tbody></table>

{% hint style="info" %}
ℹ Note: Programme IDs 1–999 are reserved for Shell EPS programmes. Programme IDs 1001 and above are Commander-managed local loyalty programmes. Additional Shell partner programme IDs may be added in the future as Shell expands its loyalty partner network.
{% endhint %}

## Site Configuration — Enabling Loyalty Stacking

Loyalty stacking is not enabled by default. A configuration setting must be turned on in Commander's back-office for sites that want to participate in Shell's loyalty stacking programme. This is done once during site setup by your system administrator or VeriFone support team.

<table><thead><tr><th width="238" valign="top">Configuration Item</th><th valign="top">Details</th></tr></thead><tbody><tr><td valign="top">Multiple Loyalty Enabled</td><td valign="top">The on/off switch for loyalty stacking. When enabled, Commander tells Shell EPS it can receive and process multiple loyalty programme discounts. When disabled, Commander operates in standard single-loyalty mode — compatible with both old and new versions of Shell EPS.</td></tr><tr><td valign="top">Default setting</td><td valign="top">Off (disabled) by default for all Shell sites. Must be explicitly enabled for sites participating in Shell's loyalty stacking programme.</td></tr><tr><td valign="top">Where to configure</td><td valign="top">Commander back-office configuration screen. Your site administrator or VeriFone support representative can locate and enable this setting.</td></tr><tr><td valign="top">Old Shell EPS compatibility</td><td valign="top">Sites running an older version of Shell EPS (INFX) should leave this setting disabled. Older EPS versions do not support the multiple loyalty capability and will reject the login if it is enabled.</td></tr><tr><td valign="top">New Shell EPS compatibility</td><td valign="top">Sites running the new Shell EPS with stacking support can enable this setting to activate loyalty stacking. Both single-loyalty and stacked-loyalty scenarios are supported with the new EPS.</td></tr><tr><td valign="top">No code change required</td><td valign="top">Enabling or disabling loyalty stacking is a configuration-only change. No software update is needed after the initial upgrade to Base 057.01.00.</td></tr></tbody></table>

{% hint style="danger" %}
⚠ Important: Only enable the 'Multiple Loyalty Enabled' setting if your site has been confirmed as using the new Shell EPS version with stacking support. Enabling it on a site with the older Shell EPS will cause login errors between Commander and Shell EPS.
{% endhint %}

## What Changed in Commander

The following is a plain-English summary of what was updated in Commander to support Shell loyalty stacking. No changes were made to the pump interface or the customer-facing payment experience.

<table><thead><tr><th width="247" valign="top">Change</th><th valign="top">What It Means for Your Site</th></tr></thead><tbody><tr><td valign="top">Commander registers as 'Multiple Loyalty Capable'</td><td valign="top">When Commander logs in to Shell EPS (at system start-up or after a restart), it now identifies itself as capable of handling multiple loyalty programmes. This tells Shell EPS that it can send back more than one loyalty programme discount for a transaction. This only happens when the Multiple Loyalty Enabled setting is turned on.</td></tr><tr><td valign="top">Discount stacking priority enforced</td><td valign="top">Commander now applies all incoming loyalty discounts in Shell's defined priority order (POP discount first, then local loyalty or secondary loyalty, then primary Fuel Rewards last). Previously, Commander applied discounts as they arrived, which could produce an incorrect total. The correct order is now enforced automatically.</td></tr><tr><td valign="top">Primary and secondary loyalty programmes tracked</td><td valign="top">Commander now identifies and distinguishes between Shell primary loyalty programmes (such as Fuel Rewards, programme IDs 1–999) and local Commander loyalty programmes (programme IDs 1001+). It uses this information to determine which combination of discounts is allowed in a given transaction.</td></tr><tr><td valign="top">Loyalty reports updated</td><td valign="top">The POS loyalty report now correctly identifies and categorises each loyalty programme separately — showing which discounts came from Fuel Rewards, which came from a partner programme, and which came from Commander-local programmes. No changes to report format were needed as Commander already distinguished programmes by their IDs.</td></tr><tr><td valign="top">Dynamic loyalty prompting blocked on secondary EPS</td><td valign="top">When Commander is acting as a secondary payment system (not the primary), it no longer shows the customer multiple loyalty programme selection prompts. A single programme selection is processed through the appropriate payment system. This prevents confusing or duplicate loyalty prompts from appearing on the pump or POS screen.</td></tr><tr><td valign="top">Compatibility with older Shell EPS preserved</td><td valign="top">Sites with an older Shell EPS version are protected — the multiple loyalty capability is only activated when the configuration flag is explicitly turned on. Older EPS sites continue to work exactly as before with standard single-loyalty mode.</td></tr></tbody></table>

## What Cashiers and Site Operators Will Notice

For most day-to-day operations, cashiers will notice very little difference. The payment and loyalty flow at the pump and indoor POS works the same way it always has. The changes happen in the background between Commander and Shell EPS.

<table><thead><tr><th width="268" valign="top">What You May Notice</th><th valign="top">Explanation</th></tr></thead><tbody><tr><td valign="top">Customer receives a larger discount than before</td><td valign="top">If a customer qualifies for both Shell secondary loyalty (e.g., Kroger) and Fuel Rewards, they now receive both discounts applied together. The total saving shown on the pump and receipt will be higher than a single programme alone.</td></tr><tr><td valign="top">Receipts show multiple loyalty discounts</td><td valign="top">The customer's receipt (and the site transaction record) may now show two or more separate loyalty discount line items — one per programme applied. This is expected and correct behaviour.</td></tr><tr><td valign="top">Loyalty report shows programme breakdown</td><td valign="top">The POS loyalty report shows each loyalty programme that contributed to a transaction, listed separately. You can see the contribution of Fuel Rewards, a partner programme, and any local Commander loyalty independently.</td></tr><tr><td valign="top">No change to the pump screen prompts</td><td valign="top">Customers still see the same prompts at the pump. They make one loyalty programme selection as before. The stacking of additional programmes (such as Fuel Rewards from their Shell card) happens automatically without any extra customer action.</td></tr><tr><td valign="top">No cashier action needed for stacking</td><td valign="top">Cashiers do not need to do anything differently. Commander and Shell EPS handle the stacking automatically when a customer is eligible for multiple discounts.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/eps-loyalty/configuring-eps-loyalty/shell-loyalty-stacking-in-fuel-transaction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
