{"id":167,"date":"2026-06-21T18:49:23","date_gmt":"2026-06-21T18:49:23","guid":{"rendered":"https:\/\/rikonrahman.com\/demo\/?page_id=167"},"modified":"2026-07-06T01:54:54","modified_gmt":"2026-07-06T01:54:54","slug":"bpme-2","status":"publish","type":"page","link":"https:\/\/rikonrahman.com\/r1\/bpme-2\/","title":{"rendered":"BPme 2"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

All case studies <\/a><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t

Mobile \/ Energy<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

BPme App: Designing Pay for Fuel and Click & Collect for a multi-market retail platform<\/h1>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"cover_photo_of_bp_pay-for-fuel-and-click-and-collect\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Overview<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

BPme began as a loyalty and station-finding app. But customers still felt that station visits took too much time: paying for fuel meant going inside the store, buying food or coffee meant searching in-store and waiting for preparation, and managing payments, rewards, discounts, and receipts felt complicated.<\/p>

I led product design for two of BPme\u2019s most important customer-facing initiatives: Pay for Fuel<\/strong> and Click & Collect<\/strong>, helping customers pay for fuel from inside the car, order food or coffee ahead of time, and make overall station visits faster across multiple regions.<\/p>

This case study follows how I worked on\u00a0Pay for Fuel<\/strong>\u00a0first, then used that foundation to shape\u00a0Click & Collect<\/strong>, with a shared design model that could scale across BP and Aral markets.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Project snapshot<\/h3>\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

I worked as a\u00a0Product Designer<\/strong>, focused on translating research and business constraints into a scalable app experience.<\/p>

For BPme, the challenge was not only to make this journey faster. It was to make it feel clear, safe, and repeatable across markets with different brands, reward systems, payment options, and engineering teams.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Business Context<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Designing for global scale <\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

By 2022, BPme<\/strong> operated across multiple regions and had reached 16 million active loyalty users worldwide<\/strong>. The app was already an important digital touchpoint for BP customers, supporting loyalty, rewards, station discovery, and transaction history across different markets.<\/p>

Each region had its own product and engineering team, with different brand requirements, payment expectations, loyalty models, language needs, and local market rules. Germany operated under the Aral<\/strong> brand, while markets such as the UK and Australia used the BP<\/strong> brand and their own local app structures.<\/p>

This local ownership helped each market shape the app around its customers, but it also created duplication. If every region designed and built station-service journeys separately, the experience could become inconsistent, slower to deliver, and harder to maintain.<\/p>

BP needed a more efficient way to introduce new station-service journeys across this ecosystem. Pay for Fuel<\/strong> and Click & Collect<\/strong> had to feel like part of the same BPme environment, while still giving local teams enough room to adapt the experience for their brand, language, payment options, loyalty model, and market rules.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

User Needs<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

What are the real problems users were facing<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

A fuel station visit is usually meant to be a quick stop, but the existing experience often turned it into a series of small, frustrating tasks.<\/p>

For fuel, customers had to leave their car at the pump, walk inside, queue at the main counter just to pay, and return to the vehicle.<\/p>

For food or coffee, they had to search the store, wait for their items to be prepared, and often queue a second time to complete the transaction or collect.<\/p>

After the visit, customers, especially business and fleet drivers, could struggle to find digital receipts for expenses, check if regional discounts were applied, or confirm their loyalty rewards.<\/p>

These small interruptions made routine station stops feel slower and more difficult, especially during morning commutes, work breaks, or short errands.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t
What this meant for BPme<\/h5>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

How might BPme<\/strong> make everyday station visits faster, while giving customers a clearer way to pay, collect, use loyalty, and access receipts?<\/p>

For Pay for Fuel<\/strong>, this meant letting customers activate the pump and pay from their vehicle, without walking into the store or queuing at the counter.<\/p>

For Click & Collect<\/strong>, this meant helping customers reduce waiting time by browsing the menu and ordering food or coffee before they arrived at the store.<\/p>

For BP<\/strong>, the bigger challenge was scale. These experiences needed to work across different regions, brands, and station formats, so each market could adopt the same core journey without designing and building its own version from scratch.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

My Role<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Designing Pay for Fuel first, then extending the foundation into Click & Collect<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

I\u00a0worked as the Product Designer<\/b><\/span> on BPme<\/b><\/span> from March 2022 to January 2023, across iOS and Android.<\/p>

The work started with Pay for Fuel<\/b><\/span>, because it was the first journey moving into detailed design and delivery. I led the design from early journey mapping and wireframes through to high-fidelity UI, prototyping, localisation, and engineering handoff.<\/p>

Click & Collect<\/b> was also part of the process from the early stages, but at first it was a lighter exploration stream. During the first few months, most of my time was focused on Pay for Fuel<\/b><\/span>, while around 20% of my time went into understanding the Click & Collect opportunity, reviewing early flows, and identifying where it could share patterns with Pay for Fuel.<\/p>

As the Pay for Fuel<\/b><\/span> patterns matured, I moved deeper into Click & Collect<\/b><\/span> and used that foundation to shape the order-ahead journey. This meant carrying forward shared parts of the experience, such as station selection, payment, loyalty, receipts, transaction status, and recovery states, while adapting the rules for ordering food or coffee ahead of arrival.<\/p>

I worked closely with the researcher, who led the service design and research activities. My role was to support synthesis, benchmark mobile payment and ordering patterns, and translate the findings into product flows that could work across multiple markets.<\/p>

I also worked closely with three product managers across Germany, the UK, and Australia, along with engineers, regional teams, and BP design leadership. Together, we reviewed decisions, worked through market-specific requirements, and made sure the experience could scale across BP and Aral markets.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Challenges<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

The business and system challenge<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

BPme operated across multiple regions, where the same core journeys had to support different brands, loyalty models, payment expectations, language needs, and market rules.<\/p>

In Germany, the product needed to support Aral<\/b><\/span> branding and Payback<\/b><\/span> loyalty. In the UK and Australia, the experience followed the BP design foundation, but visual treatment still differed by market, such as green accents in the UK and black accents for key actions in Australia, alongside local language, payment, and loyalty requirements.<\/p>

That meant core patterns such as station selection, payment, loyalty state, receipts, transaction status, and recovery states could not be treated as one fixed design that was simply translated or reskinned for each region.<\/p>

The challenge was to define what stayed consistent at the product level, and what regional teams needed to adapt for their market.<\/p>

If the design was too fixed, some markets would struggle to support their local brand, payment, loyalty, or regulatory needs. If it was too flexible, the experience could split into separate versions that were harder to design, build, govern, and maintain.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Design Sequence<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Solving the highest-risk customer journey first<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Pay for Fuel was the first journey to move into detailed design and delivery. It also tested the shared product foundations under the strictest real-world conditions, because the journey connected the app to a live forecourt transaction.<\/p>

The customer had to be at the right station, choose the correct pump, authorise payment, wait for the pump to activate, refuel, and trust that the transaction had completed correctly.<\/p>

That meant the design had to handle the core patterns early: station selection, proximity checks, pump selection, payment, loyalty, receipts, transaction status, and recovery states.<\/p>

Designing Pay for Fuel first helped me define which parts of the experience needed to stay consistent, and which parts needed to adapt by market or journey.<\/p>

That thinking later shaped Click & Collect. Some patterns could be reused, but the rules changed. Pay for Fuel required the customer to be near the station because it connected to a live pump transaction. Click & Collect needed to support ordering ahead, before the customer arrived.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Phase 1<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Pay for Fuel - Friends and Family version<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Proving the core transaction loop\u200b<\/strong><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The first release was the Friends & Family<\/strong> version. Its purpose was to validate the core Pay for Fuel<\/strong> journey before introducing more payment methods, loyalty options, and market-specific complexity.<\/p>

This version supported card payment only, which kept the first release focused on the core transaction: selecting an eligible station, choosing the right pump, setting a pre-authorisation amount, authorising payment, waiting for pump unlock, fuelling, and receiving confirmation.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The station step was the first point where the journey had to connect the customer\u2019s physical context with service availability. I designed variations for different station-selection states, including one nearby eligible station, multiple nearby stations, closed stations, loading, no connection, and cases where the customer was outside the allowed distance.<\/p>

This made the screen more than a simple location picker. It had to help customers understand whether Pay for Fuel was available, which station they were selecting, how far away it was, and whether they could continue.<\/p>

These states later became useful for Click & Collect as well, where station selection also depended on service availability, such as whether ordering was supported at that store.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Pump selection was one of the most sensitive moments in the Pay for Fuel<\/strong> journey. If a customer selected the wrong pump, they might not be able to start fuelling and may need staff help to fix the issue. The screen needed to work quickly in a real forecourt environment, including poor light, glare, rain, pressure from other cars, and small screens.<\/p>

In the early design, I explored pump selection through a simple list, larger numbered list items, and tile-based number layouts. The goal was to make pump numbers easy to scan and large enough to tap safely on a small screen. This gave the Friends & Family<\/strong> version a clear starting point, while leaving room to validate whether the interaction created enough confidence before payment.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The amount step introduced another trust moment. Customers needed to understand that the selected amount was a pre-authorisation, and that they would only be charged for the fuel they actually dispensed. I kept this step focused by separating amount selection from payment review, using fixed amount options, allowing custom entry, and confirming the reserved amount before authorisation.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Alongside the happy path, I also mapped and designed the key failure states across the journey, including payment failure, pump activation issues, connection loss, wrong pump selection, and delayed confirmation. Customers needed to understand what had happened, whether they had been charged, and what to do next.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This phase gave the team a working version of the core Pay for Fuel<\/strong> transaction. It also established patterns for station eligibility, pump selection, payment, transaction status, receipts, and recovery states. These patterns later supported the Production version and helped clarify parts of the Click & Collect<\/strong> flow, especially around store availability, payment, receipts, and order status.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Phase 2<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

What testing changed<\/h3>\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Responding to context earlier in the journey<\/strong><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Testing the Friends & Family<\/b><\/span> version showed that the German Start Fuel&Go<\/b><\/span> card made users tap before they could see whether Pay for Fuel<\/b><\/span> was available nearby.<\/p>

People opening the Aral<\/b><\/span> app at or near a station had usually already decided to refuel, but they still needed to know whether a nearby eligible station was available, open, and close enough to use. In the early flow, that information only appeared after they entered the Pay for Fuel<\/b><\/span> flow.<\/p>

I changed the card into a dynamic station-selection module. Nearby eligible stations appeared directly on the home feed, with availability shown earlier in the journey. This allowed users to understand whether they could continue before entering the full Pay for Fuel<\/b><\/span> flow.<\/p>

This removed an unnecessary tap and made the app respond to the user\u2019s physical context sooner.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Testing also showed that pump selection needed a stronger decision moment. The early tile-based layout made pump numbers visible, but users sometimes had to scroll to find the correct pump. That added effort at a moment when they were already sitting at the forecourt and trying to move quickly.<\/p>

There was also a risk in how fast the interaction felt. Because selecting a pump was a simple tap, users could choose a pump without clearly pausing to check whether it matched the pump next to their vehicle. For a low-risk screen, that might be acceptable. For Pay for Fuel<\/strong>, the pump choice affected a live physical transaction.<\/p>

I adjusted the pump selection pattern to make the selected pump more prominent, reduce unnecessary scanning, and create a clearer confirmation point before users continued to payment.<\/p>

The goal was to make the correct choice easier and the wrong choice less likely.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This phase helped refine the difference between speed and confidence. The journey still needed to be fast, but the most sensitive steps also needed to slow users down just enough to confirm the right decision.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Phase 3<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Production version of Pay for Fuel<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Expanding the payment, loyalty, and localisation model\u200b<\/strong>\u00a0<\/h4>

After the core journey was validated, the Production<\/strong> version expanded the payment and loyalty model.<\/p>

The Friends & Family<\/strong> version only needed saved card selection. Production needed to support a wider payment ecosystem, including payment cards, Apple Pay, Google Pay, PayPal, loyalty redemption, Payback in Germany for Aral customers, and Routex-related BP and Aral use cases.<\/p>

The payment step needed to grow without becoming a different journey for every region. I designed the payment step so payment methods could be added, removed, or reordered as modular options, without changing the surrounding screens or the core flow.<\/p>

This avoided a common problem in multi-market products: a new local payment or reward option should not force the whole payment journey to be redesigned.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Receipts and transaction history\u200b<\/strong><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Receipts were part of the same trust layer. Customers needed to see what they paid, what was fuelled, which discounts or points were applied, and where the transaction happened.<\/p>

Beyond showing transaction history in the app, receipts needed to be exportable as PDF, by email, or through native iOS and Android sharing. This was especially useful for customers who used fuel purchases as a business expense.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t

Localisation from the early layout stage<\/strong><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Localisation shaped the layouts from the early design stages because the same journey had to work across different markets without becoming a separate design for each one.<\/p>

German text could run significantly longer than English, and Aral required a different brand expression from BP. I considered text expansion, regional labels, local rewards, and different brand treatments before the screens were fully polished.<\/p>

This helped the same core flow work across BP and Aral markets, while still giving each region enough room to meet its own language, brand, payment, and loyalty requirements.<\/p>

I also checked the same core screens across BP and Aral visual treatments. This helped us see whether the interaction still worked when brand colours, labels, loyalty content, and regional payment options changed.<\/p>

By the end of this phase, Pay for Fuel<\/strong> had moved from a focused card-only transaction into a flexible, market-ready production journey. It established a stronger foundation for payment, loyalty, receipts, transaction status, recovery states, localisation, and market adaptation.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Phase 4<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Designing Click & Collect<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

For Click & Collect<\/strong>, the journey started with store selection. This was important because food and coffee availability depended on the selected store. Showing the store first reduced the risk of customers browsing items that were unavailable at their chosen location.<\/p>

From there, the flow moved into browsing, item detail, basket, payment, order confirmation, and collection. This made Click & Collect<\/strong> feel closer to an order-ahead store experience than the shorter transaction flow used for Pay for Fuel<\/strong>.<\/p>

The journey also needed to handle different product types. A packaged snack could go straight into the basket, while made-to-order items, such as coffee, needed a customisation step for choices like size, milk, or other options. I designed customisation as a conditional step, so simple items stayed quick to add, and more complex items gave customers the choices they needed before checkout.<\/p>

I reused familiar BPme<\/strong> patterns where they helped, including station selection, service availability, payment, loyalty, transaction status, and recovery states. The journey also needed new patterns for menu availability, item customisation, collection instructions, and order progress.<\/p>

A key design challenge was helping customers trust the timing of the order. They needed to understand where to collect, when the order would be ready, and what to do if an item became unavailable or the store could not fulfil the order.<\/p>

The final flow gave customers a way to choose a store, browse available items, place an order, and collect it at the station with clearer status and fewer in-store steps.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The Impact<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

Multi-market rollout, with commercial metrics omitted<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Global implementation:<\/strong> Pay for Fuel<\/strong> launched first in Germany and the UK, then expanded to Australia, Poland, and Spain. Click & Collect<\/strong> launched in the UK and Australia.<\/p>

Two connected station-service journeys:<\/strong> The work supported paying for fuel from the car and ordering food or coffee ahead of arrival.<\/p>

Delivery efficiency:<\/strong> For BP, the shared model helped reduce duplicated delivery effort across markets. Instead of each regional team designing and implementing its own version, teams could reuse the same core journey patterns and adapt the parts that needed to change locally.<\/p>

Public product signals:<\/strong> In the UK, the BPme app held a strong 4.8\/5 rating across more than 160,000 ratings<\/strong>. Pay for Fuel was central to the app\u2019s public value proposition, with the App Store positioning BPme around \u201cPay for Fuel in Your Car.\u201d<\/strong><\/p>

In New Zealand, the BPme App Store proposition highlighted \u201cPay for Fuel, Coffee & Carwash.\u201d<\/strong> Public reporting from that market showed that BP\u2019s fuel payment and coffee pre-order experience helped save customers more than 25,000 hours<\/strong> and contributed to a 6 to 10% uplift in visit frequency<\/strong>.<\/p>

For confidentiality reasons, I have omitted internal commercial performance metrics and transaction volumes.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t <\/polyline> <\/svg> Previous case study<\/span> <\/a>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t Next case study<\/span> <\/polyline> <\/svg> <\/a>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

All case studies Mobile \/ Energy BPme App: Designing Pay for Fuel and Click & Collect for a multi-market retail platform Overview BPme began as a loyalty and station-finding app. But customers still felt that station visits took too much time: paying for fuel meant going inside the store, buying food or coffee meant searching […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"elementor_header_footer","meta":{"footnotes":""},"class_list":["post-167","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/rikonrahman.com\/r1\/wp-json\/wp\/v2\/pages\/167","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rikonrahman.com\/r1\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/rikonrahman.com\/r1\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/rikonrahman.com\/r1\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rikonrahman.com\/r1\/wp-json\/wp\/v2\/comments?post=167"}],"version-history":[{"count":121,"href":"https:\/\/rikonrahman.com\/r1\/wp-json\/wp\/v2\/pages\/167\/revisions"}],"predecessor-version":[{"id":422,"href":"https:\/\/rikonrahman.com\/r1\/wp-json\/wp\/v2\/pages\/167\/revisions\/422"}],"wp:attachment":[{"href":"https:\/\/rikonrahman.com\/r1\/wp-json\/wp\/v2\/media?parent=167"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}