Stacking is one of the few Black Friday tactics that pays for doing paperwork instead of spending more. A shopping portal pays cash back for starting the trip through its link, and that reward arrives in addition to whatever the credit card used at checkout normally earns. Two rewards on one purchase, no extra spending required. The catch is that the stack is worth less than the headline math suggests, for three reasons: the portal percentage applies to eligible spend rather than the whole checkout total, the reward takes weeks to confirm, and the portal layer is the easiest money in the cart to lose by accident.
What each layer is, and what it is calculated on
| Layer | How it is earned | Calculated on | When it arrives |
|---|---|---|---|
| Sale price | Buying during the promotion | The item price at checkout | Immediately |
| Portal cash back | Clicking through the portal to the store, then completing the purchase in that session | Eligible spend only. Rakuten states taxes and shipping fees are never eligible, and gift card portions can be excluded | Typically 3 to 14 weeks to be confirmed for online purchases, per Rakuten |
| Card rewards | Paying with a rewards card | The amount charged to the card, under the card's own category rules | With the statement cycle, under the card's terms |
| Promo code | Entering a code at checkout | The item price, under the code's terms | Immediately, if accepted |
Portals commonly pay in the range of 3 to 10 percent, and the published stacking examples are attractive for a reason. CardRatings illustrates the arithmetic plainly: 10 percent back through a portal combined with a card paying 5 percent cash back can net a 15 percent return. That arithmetic is correct. It is also the best case, calculated on spend the portal agrees to count, in a session where nothing breaks the tracking.
The five ways the portal layer breaks
Rakuten's own help pages read like a list of good intentions gone wrong. Each of these is drawn from the portal's published reasons for cash back not being earned.
- A coupon code from somewhere else. Using a code that is not listed on the portal may void the cash back, because the code can override the portal's tracking. The code saves a few dollars now and can cost the whole portal layer.
- A blocked or broken session. Ad blockers, VPNs, and cookie blockers can interfere with tracking. So can completing checkout in a different tab from the one the portal opened, or letting the session sit idle too long.
- A cart filled too early. Cash back has to be activated before items go into the cart. Some stores cannot link a purchase to the portal account if the items were added before activation.
- The wrong way of paying. Most gift cards are excluded from earning, and some stores exclude purchases paid for with gift cards. Rakuten Canada is blunt about its side of the border: no cash back on the portion of a purchase paid with gift certificates or store credit.
- A return, even a partial one. Returned or cancelled orders do not earn cash back, and a partial return adjusts the reward, or may void it. The December return run reaches back into November's stack.
Notice what is not on the list: effort. None of these failures come from shopping badly. They come from ordinary habits, pasting a code from a search result, paying with a gift card from a birthday, returning the wrong size. The stack does not need more cleverness. It needs a clean run.
A worked stack, with the costs subtracted
Worked example, with labelled assumptions. The rates below are assumptions chosen to match the published stacking example's shape, not live rates for November 27, 2026, because portal rates change daily and sometimes hourly. An item sells for $400. The portal is assumed at 8 percent and the card at 2 percent. The item is the whole order, with $30 of tax and shipping on top.
| Line | Math | Value |
|---|---|---|
| Portal cash back | 8 percent of the $400 eligible item price; tax and shipping excluded | $32.00 |
| Card cash back | 2 percent of the $430 charged to the card | $8.60 |
| Total stack | $32.00 plus $8.60, on a $400 item | $40.60, about 10 percent of the item price |
| If the balance is carried for 3 months at an assumed 22 percent annual rate | About $430 times 22 percent times 3 divided by 12, a rough interest estimate of about $23.65 | More than half the stack, gone |
Two lessons fall out of that table. First, the stack is worth roughly a tenth of the item price in this example, which is real money, and it is not the 15 or 20 percent of the loudest examples unless the rates genuinely line up. Second, the stack cannot survive being borrowed. Carrying the balance for a quarter of a year at a typical card rate hands more than half of it back, and the portal share may still be sitting in the pending column, because online cash back typically takes 3 to 14 weeks to confirm. Spending the reward before it confirms is spending money that a return can still cancel.
There is one more cost the table cannot show. If a portal rate pulls the purchase to a retailer charging $425 for the same item available at $400 elsewhere, the $25 price gap beats the stack before it starts. Compare the item's price across retailers first, on the price tracker's evidence, and stack second. A portal aggregator such as Cashback Monitor, which compares portal rewards for a store across programs, settles which portal to use. It should never settle which store to use.
The clean session procedure for sale day
- Decide the store on price first. Confirm the item and the retailer using price history, then compare portal rates for that store only.
- Open a clean session. Use one browser, pause ad blocking and VPN software for the shopping session, and accept the store's cookies when prompted.
- Activate before the cart exists. Click through the portal to the store, confirm the cash back is active, and only then add items.
- Stay in that tab and finish. Complete the purchase in the tab the portal opened, in one sitting, without detouring to coupon sites or other reward extensions.
- Use only codes the portal lists. A code found anywhere else is a trade: a small certain discount against the whole portal layer. Run the numbers before pasting.
- Pay with the rewards card, not a gift card. Keep the full amount on the card whose rewards form the second layer, and plan to pay the statement in full.
- Screenshot the activation and the order. If the cash back does not appear, the portal's missing cash back process starts from the order details. A dated screenshot is the evidence.
What success looks like: the shopping trip shows in the portal account, the order appears as pending, and the confirmed amount that lands weeks later matches the eligible spend math done on the day. If the trip never appears, that is a tracking failure, which is a different problem from an exclusion, and the portal's own help treats the two separately.
Questions readers ask about stacking
Can a coupon and portal cash back really combine?
Yes, when the code is one the portal lists. Codes and cash back work by different mechanics, a code reduces the price paid and cash back returns a percentage of eligible spend. The risk is only with codes from outside the portal, which may override its tracking.
Does the portal percentage apply to the full checkout total?
Generally no. Taxes and shipping are excluded, gift card portions can be excluded, and individual stores set category exclusions and different rates by category. Value the stack on the item subtotal, then be pleasantly surprised if the confirmed figure is kinder.
Is it worth opening accounts with several portals?
For a large planned purchase, comparing two portals through an aggregator takes minutes and the rate gap can be several percent of a big ticket price. For everyday small orders, one portal used cleanly beats three portals used carelessly, because a broken session pays zero everywhere.