How Gap Inc. Re-Platformed Loyalty and Redesigned Encore at the Same Time, Live, With Zero Downtime

The session — Loyalty's New Operating System: How Encore Was Built to Move at the Speed of Culture — was presented by Kevin Meiners, Head of Loyalty and Payments at Gap Inc., and Emil Sarkissian, CEO and Co-Founder of Loyalty Methods. It walked through how Gap Inc. took Encore from strategy to launch to scale.

Encore replaced a program Kevin described as firmly anchored in points-equal-discount-on-product. It did so by unifying four iconic brands into a single membership built around access to fashion and entertainment rather than transactional discounting.

The technically interesting part was not that Encore shipped. It was the sequence Gap chose. Five things from the room are worth carrying home.

Kevin framed Gap's entire strategy around a single sequence: if you are relevant, you drive revenue, and you have to get it done in that order. His words were deliberately plain: "Relevance is something that says very easily and does very hard."

The practical version is that a large share of Gap's member base already shops more than one of the four brands — in some cases all four. The relationship already exists. What changed with Encore was the decision to talk to those members as people with interests, not as four separate transaction histories. Broaden the aperture, engage members beyond the product, and the engagement and conversion lift follows. Gap reported a significant uptick in engagement and conversion rates as a result.

For a CMO, this is the reframe. The loyalty program stops being a discount mechanism and becomes the place where the brand earns the right to be relevant in the first place.

Gap's old program was, in Kevin's words, super transactional: get points, pay with points. Encore did not soften that model. It replaced it.

The Encore Market is a marketplace where points buy things a discount cannot: autographed merchandise from the Christopher John Rogers collaboration, a visit with Zac Posen at his New York atelier, Coachella VIP experiences, a Japanese whiskey tasting, opening-day movie tickets, and family nights at the theatre. Marketplace redemptions are tied into the shopping-bag experience in the same flow, which pulls members toward the brands even when they arrived for the experience.

This is the part that is hard to copy quickly, because access is not a feature you configure. It is a set of relationships you have to have built already. Gap launched with Disney+, Live Nation, NBCUniversal, AMC Theatres, Playbill, and Ticketmaster because those relationships were real before the program needed them. The platform's job is to make redemption against that supply real-time and reliable at the moment a member acts.

Kevin was direct about what speed of culture demands: rethink the systems, the processes, the platforms, the partnerships, and the ways of working — because all of them have to change if you intend to keep pace.

His proof point was almost offhand. His team built two activation sizzle reels in two months, because he looked at the first one and called it tired. It was eight weeks old.

That is the real bar. If a brand needs an engineering ticket and a multi-week release cycle to put an offer in market, the cultural moment is gone before the offer is live. Encore was built so that marketers and brand teams can structure and launch offers themselves, without waiting on engineering. The requirement came from the calendar, not the technology — but the technology is what makes it possible.

This is also where the work shows up in the platform: time-to-market for the marketer, not just feature count for the developer. ReactorCX addresses it with a single polymorphic activity model and configurable promotion logic that lets program teams build tiers, challenges, streaks, and segmented offers without code, while still exposing deep mechanics for advanced users. As Emil put it, the goal was to balance the range so it is not too complicated for casual users and not too restrictive for advanced ones.

Here is the decision the session was really about — and the one most enterprises are counseled against. This was not a like-for-like replacement. Gap re-platformed the loyalty infrastructure and redesigned the program at the same time, and put new developments live on day one, at full scale, with no pilot.

That includes a brand-new marketplace launched cold and the shift away from static earn-and-burn rules toward non-purchase behaviors, gamification, and segmented offers. None of it phased in quietly.

The standard enterprise migration discipline — including the standard Loyalty Methods sequence on prior programs — is to move the platform first and evolve the program after. Move one variable at a time, because you cannot safely observe the blast radius of moving two. That discipline implicitly assumes the program logic is staying the same through the migration.

Gap's case broke that assumption on purpose. The new program logic had never run in production anywhere, so there was no legacy output to validate against for the new mechanics. The reason it was attemptable is the mechanism underneath it, and a second layer the team added on top.

SafeSwitch™ is how Gap migrated without members feeling a thing. The mechanics are specific and worth stating plainly, because zero downtime is easy to claim and hard to demonstrate at this scale.

ReactorCX is stood up and run in parallel with the live system — in the shadows — while every single transaction is compared against everything happening in current production until the two match. Live production traffic is replayed against the new platform in real time, validating a one-to-one match before any cutover. The replay runs faster than live production traffic, which doubles as proof the platform can absorb well beyond peak load before a single member is exposed to it. For the day-one program changes that had never run in production, Gap added a dark testing layer on top of the parallel run.

The scale this absorbed: more than 40 million active memberships, hundreds of millions of historical transactions reconciled, more than 2,000 stores, four brands folded into one experience. Zero downtime.

For a CIO, that is the whole argument. The orthodoxy says move one variable at a time because you cannot safely observe the blast radius of moving two. A parallel-run-and-compare migration changes what you can safely observe — and therefore what you can safely attempt.

It is worth being precise about what "migration" means here, because the word hides a lot. SafeSwitch is not a routine software update rolling out without interrupting service. It is a full cutover from a decade-old legacy system, with its own custom logic and integrations, to a new platform — with the new platform proven against full production traffic before the switch.

Underneath the migration sits the platform Emil described as built first for real-timeness. ReactorCX was designed not just to ingest data in real time but to event in real time, surfacing what is happening with every member in every moment. It is headless and API-first, with sub-second response times — which is what lets a member earn at one touchpoint and redeem at another inside a single session without the point-balance lag that erodes trust at peak moments.

Two more capabilities mattered for Encore specifically. FeedXChange handles partner data in any format and normalizes it for the rules engine, which is how a coalition of entertainment partners feeds a single marketplace. And ReactorCX is built for multi-program, multi-brand operation — multiple brands with different rule structures running on one platform, which is precisely the canvas Gap needed to hold four distinct brands without flattening them.

On security posture, the platform completed its SOC 2 Type II audit covering security, availability, and confidentiality — table stakes for a roster that includes BP, 7-Eleven, and MGM Resorts.

Buyers evaluating enterprise loyalty technology typically weigh the same requirements: real-time processing, integration depth, reward-engine flexibility, scalability, and migration risk. The Encore project illustrates how ReactorCX meets each.

The thread connecting all five is that the program redesign and the migration that delivered it were treated as one engineering problem rather than two sequential projects. That is the wedge Encore sharpened.

The takeaway from the room was not that loyalty is becoming experiential. Everyone says that. It was that the experiential program and the migration that delivers it are the same engineering problem — and the brands that can move both at once are the ones who built the architecture for it before they needed it.

Encore is the starting point, not the finish. As Kevin put it, you do not have a chance to participate in the cultural conversation unless speed, flexibility, and agility are built into your systems and your ways of working. The platform was not built for one cultural moment. It was built to move at the speed of whatever comes next.