A guest's final price on Booking.com reflects more than one discount at once, and this explains how Genius and other active promotions stack and what you actually net per booking.
You opt into the Genius program expecting one discount to apply, and then a booking comes in at a price that looks lower than that discount alone would explain. Usually that's because more than one promotion is active on the same rate at once, and working out what you actually net means separating them rather than assuming Genius is the only thing touching the price.
A guest books at a price that's lower than your standard rate, and when you check the reservation, more than one discount is listed against it — a Genius discount tied to the guest's loyalty level, alongside a separate promotion you've opted into for those dates, such as a last-minute or mobile-rate deal. Each one is doing exactly what you set it up to do; the confusion comes from seeing the combined effect on one line and trying to reverse-engineer which part came from where.
This is more noticeable on last-minute and mobile bookings specifically, since those are the categories most likely to have an additional promotion layered on top of whatever Genius discount already applies to that guest.
Genius is a loyalty program built into the guest's account, not a promotion you toggle for specific dates, so it's active by default for eligible guests on any rate plan you haven't explicitly excluded from it. A separate promotion you opt into — tied to a booking window, a device, or a last-minute date range — is a different mechanism entirely, and the platform doesn't treat the two as mutually exclusive unless you've specifically set a rate plan to exclude Genius guests. The result is that an eligible guest booking during an active promotion window can see both discounts applied to the same price.
This isn't a bug in either program; it's the expected behaviour when two independent discount mechanisms both have a legitimate claim on the same reservation and neither one has been configured to block the other.
Open the specific reservation in the extranet rather than comparing your standard rate card to the booked price in your head — the reservation detail should show which discounts were applied, not just the final number. Cross-check that against which promotions you currently have active for those dates and whether the rate plan the guest booked allows Genius discounts to apply on top. If a booking's price still doesn't reconcile after accounting for both, that's worth checking against your rate plan's current promotion settings rather than assuming the extranet made an error.
Prime Shield compares the rate you sent, the rate you intended to charge, and what the guest actually paid, and flags any gap worth more than 5% in plain money rather than leaving you to reconstruct which discount did what from the reservation screen alone. If stacked discounts have made your net pricing hard to track, that structural check is the fix — you can see it on the public demo at try.primehostpartners.com without signing up.