On an ordinary Tuesday a red "SALE" flag on a collection tile does real work: it separates four discounted products from ninety that are not. On 27 November 2026 every tile has one. At that point the badge is not information, it is wallpaper — and the thing you most need, which is to steer attention to specific products, is the thing you have given up.
This is the BFCM badge problem, and it is not solved by making the badge bigger.
Why the sale badge stops carrying information
A badge works by contrast. It means "this one, not those". When the discount is sitewide, the contrast is gone — the shopper already knows everything is reduced, because that is why they came.
Worse, a uniform badge actively flattens your merchandising. The product you most want to move looks exactly like the one you are indifferent about. You have spent your only visual signal on a fact the customer already has.
What to badge instead
During BFCM the useful badges answer questions the sitewide discount does not.
Depth of discount, not the existence of one
"40% OFF" separates products; "SALE" does not. If your discounts vary — and they almost always do — badge the number. The shopper scanning a collection is doing arithmetic anyway, so do it for them.
Scarcity, where it is true
"Only 4 left" is the badge that still carries information on the 27th, because it is about this product and nothing else on the page. It is also the one most easily abused — if it is not accurate, regular customers will notice within one season.
Ending
"Ends Monday" on the lines that genuinely revert on Cyber Monday. This is the badge that converts the browser who was going to come back in December.
Bundle and volume signals
"3 for £45" or "Save more at 2+" tells the shopper something the price alone does not, and it points at a larger basket rather than a cheaper one.
Nothing at all
The most underrated option. If seventy products in a collection carry a badge and thirty do not, the thirty are now the ones that stand out. Badge discipline is a merchandising decision, and in a sitewide sale fewer badges is usually the stronger one.
The Merchant Center problem, which BFCM makes worse
Google Merchant Center prohibits promotional overlays on product imagery. A price, a discount, or a "SALE" flag burned into the image file you submit is a disapproval, and the product stops showing in Shopping.
This matters more in November than at any other time for two reasons. The volume of badging is far higher, so the chance of one slipping into the feed rises. And the cost of a disapproval is at its maximum — a product pulled from Shopping on the 25th is pulled for the week that pays for the quarter.
The safe pattern is a display-layer overlay: the badge is rendered on your storefront and the image file Google receives is untouched. If your process involves editing the actual photo, BFCM is the worst possible time to be running it — and removing the badge afterwards means restoring a backup rather than flipping a switch.
Scheduling, because you will not be at a keyboard
Badges that go up by hand go down by hand, and the most common badge failure in this category is a sale flag still showing in the second week of December.
Set start and end times when you set the badge — on at midnight on the 27th, off when the sale ends. The reason is not convenience. It is that the end of the sale is the moment your prices go back up, and a badge promising a discount that no longer exists is the kind of thing customers screenshot.
Where badges actually get seen
Two placement details decide whether any of the above matters, and both get missed because they are invisible on a desktop mock-up.
The collection tile is the real estate. A badge on the product page is reaching someone who already clicked — the decision it influences has largely been made. The badge that changes behaviour sits on the tile, in the grid, against the ninety other tiles. If an app badges product pages well and collection tiles badly, it is solving the wrong half for BFCM.
Mobile crops differently. A corner ribbon that reads cleanly in a three-column desktop grid can land on the product's face in a two-column phone grid, or be cropped out entirely by a square aspect ratio. Most BFCM traffic is mobile. Look at your badges on an actual phone, on a real collection page, before the sale — not in the app's preview pane, which almost always shows a desktop tile.
How the main badge apps compare
Read from the live Shopify App Store listings on 8 October 2026. "Not listed" means the term does not appear on their listing, not that the app lacks the feature.
| Overlay (ours) | DECO | Lably | Flair | Labeler | |
|---|---|---|---|---|---|
| Rating (reviews) | 4.8 (8) | 4.9 (1,712) | 5.0 (662) | 5.0 (235) | 4.7 (143) |
| Built for Shopify | Yes | Yes | Yes | Yes | Yes |
| Free plan | Yes | Yes | Yes | No | Yes |
| Entry paid plan | $4.99 | $9 | $7.99 | $29 | $5.99 |
| Highest listed plan | $4.99 | $39 | $19.99 | $99 | $15.99 |
| Scheduling | Listed | Listed | Listed | Listed | Listed |
| Watermarking / image protection | Listed | Not listed | Not listed | Not listed | Not listed |
Reading that honestly
We publish Overlay, so the unflattering row first: 8 reviews against DECO's 1,712 and Lably's 662. That is not a close call on track record, and seven weeks before BFCM an app that has been through several of them with a thousand merchants is a reasonable thing to prefer.
Scheduling is on every listing here, so do not let anyone sell it to you as a differentiator — including us. It is the baseline.
Two rows do separate things. Ours is the cheapest paid plan in the set at $4.99, with no higher tier to climb to, which matters if badges are the only job you need done. And watermarking — the image-protection side, as distinct from badges — appears only on ours; the others are label and badge apps, which is a different product even though the categories overlap in search.
If what you need in November is badges on a large catalogue, DECO and Lably are the obvious shortlist. If you also want image protection, or you want the job done for five dollars, that is where we are worth a look.
A seven-week run-up
- This week: decide what you will badge that is not "SALE". Depth, scarcity, ending, bundle — pick two at most.
- Mid-October: confirm your badges are display-layer and your feed images are untouched. Check a sample in Merchant Center.
- Late October: set start and end times rather than planning to do it by hand.
- Early November: run a dress rehearsal on one collection. Look at it on a phone, which is where most of the traffic will be.
- Week of the 23rd: check Merchant Center for disapprovals one last time, while there is still time to fix one.
Where to go next
Overlay renders badges and watermarks on the display layer, so the file in your feed stays as shot. For the scheduling mechanics, see scheduled sale badges; for the feed rules in full, Google Shopping feed compliance; and seven badge strategies for the year-round version.
