Your Club Royale offer shrank because the ledger settled late.
The offer that came back a tier lighter
Picture a Signature-level player who sailed twice this spring. On the first cruise they played heavy. After they got home, they spotted a slot session that had posted to their SeaPass twice, disputed it with their card issuer, and won.
Then the next Club Royale offer landed. It read like it was written for a Prime card: an inside cabin, fewer nights, no FreePlay line.
No email explained it. Nothing flagged an adjustment.
That player is a composite, not one person's story. But it's the shape of a question that keeps coming back on the Cruise Critic Royal Caribbean casino board and r/royalcaribbean. Players swap the same suspicion in thread after thread: that a refund, a canceled sailing, or a disputed charge quietly knocked their next offer down a tier. The details change from thread to thread. Sometimes it's a canceled sailing refunded to the card, sometimes a disputed casino charge. The shape of the complaint doesn't.
The net-play ledger
Club Royale offers look like they're priced off net play: whatever is still standing on your record after every refund, reversal, and dispute has settled. Call it the net-play ledger.
The number you remember from the cruise is gross. Every dollar of coin-in, every hand at the table. The number the offer engine works from is whatever survived.
And the ledger doesn't settle when you walk off the ship. A card chargeback can take weeks to resolve Mastercard cardholders generally have up to 120 days from the transaction or expected delivery date to file a dispute (source), so the reversal can land after one offer was already generated and just before the next. One dispute, two offers touched: the one priced before the reversal and the one priced after.
RC doesn't publish its offer formula, and anyone posting one on a forum is guessing. The documented piece is the Club Royale Terms and Conditions language on point adjustments Upon cancellation of a Club Royale Membership, Members forfeit any unused points, tier status, and associated benefits. (source). Put that next to the forum reports and the net-play reading is the one that fits.
Why 'RC is punishing me' is the wrong read
The default forum explanation is intent. You disputed a charge, so the casino marked your account.
Maybe. There's no public evidence either way, and a punishment theory gives you nothing to plan around.
The ledger reading is more useful because it's mechanical. If tier credit reverses along with the money, the offer drop is arithmetic running on a smaller number. That swaps 'did I get flagged?' for 'what does my record show right now?', and the second question has an answer you can go get by calling Club Royale.
The other common read, that offers just swing, fails for a different reason. Offers do move cruise to cruise. But a player who logs every offer can usually spot a random swing, because it doesn't line up with anything. A drop that lands one offer cycle after a refund lines up with something.
What to save when a refund or dispute happens
Four kinds of events come up in the threads: a disputed casino charge, a casino charge the ship reverses on its own, a canceled offer-booked sailing, and a refunded fare on a paid sailing. RC doesn't say how, or whether, each one moves your points. So the practical move is to keep a paper trail that lets you match an offer change to a date.
Save these the day they happen. Six months later, you won't be able to reconstruct them.
How the lag plays out across two offers
Run the composite forward.
The player gets off cruise one with a strong session behind them. A couple of weeks later, the dispute goes in. The next offer email arrives while the dispute is still open, and it looks normal, because the ledger it was priced from still includes the disputed play. They book it.
Then the dispute resolves in their favor and the money comes back. If the tier credit tied to that play reverses with it, the ledger shrinks, and the offer after that gets priced from the smaller number.
So the downgrade shows up one cycle late. Nothing the player did that month explains it, which is exactly why it reads as random in a forum post. It isn't random. It's a delay.
Should you dispute a casino charge on your SeaPass?
Yes, if the charge is actually wrong. A double-posted slot session is real money, and protecting your next offer isn't worth paying for play you didn't make.
But go in with the right expectations. Fix it onboard if you can, while you're still on the ship and the casino staff can see the session. If it has to become a card dispute, assume the next offer or the one after it will be priced as though that play never happened, because if the ledger reading is right, it didn't.
The same goes for a canceled sailing that was booked from an offer. Keep the offer email. If the next one comes back lighter, you'll want the original in hand when you call Club Royale and ask what your record shows.
And if you're weighing whether to cancel at all, factor the ledger in. The refund is certain. What it does to your next offer isn't documented anywhere, so price in the downside.
Where a spreadsheet loses the thread
Most offer spreadsheets have one row per offer: ship, sail date, cabin, FreePlay, expiry. That row captures what RC sent. It doesn't capture why the next row looks different, and after a year of cruising, nobody remembers which month a dispute closed.
SailQuery keeps every Club Royale offer in one dashboard, side by side, so a drop is visible the day it lands instead of three offers later. Put that history next to the dates from the checklist above and the lag has a timestamp. That's the conversation you want to have with Club Royale: this offer, after this date, with the email to prove it.
We don't sell cruises and we don't take commissions. It's your offers, in one place, where you can see them.
What we're watching next
The open question is whether canceling a sailing booked from a casino offer moves the ledger the same way a card dispute does. The threads tend to blur the two into one complaint.
Until someone shows a clean split, treat both as ledger events and log them the same way.