The Club Royale Journal

Two Chrome Extensions, One Facebook Thread: Why Club Royale Players Keep Rebuilding the Same Offer Tracker

A Reddit build, two Chrome extensions and a Facebook plea, all in the same stretch of weeks. Each one points at the same gap in how Club Royale offers get tracked.

By The SailQuery Desk · Oct 2, 2026

A phone lying face down beside a notebook on a cabin desk

Club Royale players keep building the offer tracker RC never shipped.

The same question, asked four ways in one month

The Facebook post in September was one line long, asking whether there was an easier way to track Club Royale offers. No context. No screenshots. It didn't need any, because everyone reading it has the same folder of offer emails and the same camera roll full of offer screenshots.

The answers were already being built. A Reddit poster shared a URL tool they'd made by prompting Claude. A r/royalcaribbean thread titled "Unable to View Club Royale Offers in Royal Caribbean ..." had been up for about 11 months. A Chrome extension called RC Club Royale Offers Parser was live in the Chrome Web Store with a matching GitHub repo behind it. And Comp Royale, another extension, had reached version 2.3.5, updated September 13, 2026.

Nobody coordinated any of this.

That's the story.

The Rebuild Signal

Call it the Rebuild Signal. When strangers who don't know each other build the same tool for the same loyalty program in the same few weeks, the tool is telling you something the program's own page isn't.

One homemade tracker is a hobby. A spreadsheet is a habit. Three separate builds plus a public plea for a fourth option is a demand curve, and it points at one thing: Club Royale players want their offers out of the portal and into something they control.

That's not a UX nitpick. It's unmet demand, and so far volunteers have been the ones meeting it.

Why "just keep a spreadsheet" misreads the problem

The standard forum reply to that Facebook question is some version of: make a spreadsheet. Plenty of Club Royale players already have one.

And that's the flaw in the advice. The spreadsheet is the first rebuild. It's the same act as the Chrome extensions, done by hand: copy every offer out of the portal, retype the sailings and dates, and hope you caught the one that landed in a different inbox. The extensions exist because people got tired of the manual version. The Reddit tool exists because building one got cheap enough that tired people started doing it themselves.

Treating each of these as a personal quirk misses the aggregate. Every private spreadsheet is a vote. The public tools are the votes you can finally see.

What the four artifacts actually agree on

Strip away the names and the builds converge on one output: every current offer, pulled out of the Club Royale portal and into a single list you can scan, whatever form each tool happens to take.

A few details sharpen it.

Comp Royale's 2.3.5 version number suggests a long run of releases. Nobody keeps doing that for a toy. A tool that reads offers off a web page has to keep pace with that page, so a long release trail tends to reflect maintenance as much as new features.

The Offers Parser pairs its Chrome Web Store listing with a public GitHub repo. In a niche this small, publishing the source suggests the builder expected other players to check it, fork it or fix it.

Then there's the Reddit tool, made by prompting Claude. That detail matters more than it sounds. Once a personal tracker costs an evening to build, the number of trackers stops measuring how hard the problem is and starts measuring how many people have it.

How the rebuild happens, one batch of offers at a time

Picture a player holding several live offers at once: a couple in the portal, one that arrived by email, one on a mailer. Each covers its own list of sailings and its own booking window. Each stateroom offer must be booked prior to its own advertised Book by Date and applies only to sailings departing before its own advertised date. (source).

To answer a simple question, like which of these gets them onto Symphony of the Seas in the spring, they open each offer one at a time. Screenshot. Retype the sailing list into a sheet. Add the expiry in a column they'll forget to sort by. Then new offers arrive and half the sheet goes stale.

Around the third time through, one of two things happens. They stop tracking and book whatever's in front of them. Or they build something.

That's the whole Rebuild Signal in miniature. The portal answers "what is this offer?" The player wants to know which of their offers fits this trip best, and which one runs out first. Nobody's building that view for them.

What changes if the signal is right

If four separate artifacts point at the same gap, players are asking for an inbox: every offer from every source in one place, sortable by what they actually care about, visible before the booking window closes.

It also means the DIY route has a ceiling. A homemade parser works until the page it reads changes, and then its builder is back to debugging instead of booking. The spreadsheet works until the week you're too busy to retype. Both run on one person's spare time, and a cruise week eats spare time first.

Somebody has to maintain the tracker. The only choice left is who.

The inbox the DIY tools are reaching for

SailQuery is the purpose-built version of what these tools are reaching for. You log in, the app scans and syncs, and every Club Royale offer you hold lands on one dashboard. No screenshots, no retyping, no digging through email for the one you forgot.

From there it does the job the spreadsheet was for: sailings side by side, a day-by-day itinerary with ports of call, estimated taxes and fees, estimated upgrade costs, and expiring-soon labels so the offer that runs out first doesn't hide at the bottom of a list. Syncing happens in the app on iPhone, iPad or an Apple-silicon Mac, and the synced dashboard opens in any browser.

It's deliberately narrow. SailQuery doesn't track play, tier points or coin-in, and it doesn't send reminders. It keeps your current offers in one place so the next batch doesn't start with a rebuild.

The people behind these tools were right about the problem. Players shouldn't have to become builders to fix it.