A badge does not show
Check in this order:
- Does the badge have words? A row with empty What it says is not saved.
- Does the condition match? A sale badge needs a sale price that is active today; a chosen-products badge needs the right ids. Category ids include sub-categories, but a product id must be the product's own id (not a variation's).
- Full edition: is Active ticked, and is today between Starts and Ends? Are On the shop and category pages / On product pages on?
- Free edition: is it one of the first three badges, with a condition the free edition offers?
- Does your theme fire WooCommerce's hooks? Badges are printed on
woocommerce_before_shop_loop_item_titleandwoocommerce_before_single_product_summary. A page builder that draws its own product cards may skip them.
A product on sale shows two sale badges
One is WooCommerce's own "Sale!" flash. Full edition: tick Remove WooCommerce's own sale flash. In the free edition, either word your badge differently or hide the flash with your theme's CSS (.woocommerce span.onsale { display: none; }).
The badge appears in the wrong place
The stylesheet positions badges over the product image of WooCommerce's standard product cards and product page. A theme that uses different markup may need a line of CSS to give the card position: relative. Both editions also position the cards of a block theme's Product Collection block (li.wc-block-product), so the stack sits on the card rather than in the page corner.
Are badges styled on a page that is not a shop page?
Yes. The stylesheet is loaded in the head on WooCommerce pages — the shop, categories and products — and anywhere else it is added the moment a badge is printed, so a [products] shortcode on the home page or a Product Collection block on an ordinary page gets it too (printed in the footer).
Does it work with the Cart and Checkout blocks?
Badges are not shown in the cart or checkout; they are for product images. Both editions declare compatibility with the blocks and with HPOS.
Does it work with page caches?
Yes. Badges are ordinary HTML in the page. A cached page shows the badges it had when it was cached until it is rebuilt.
A "new" badge shows on an old product (Full edition)
"New" is measured from the day the product was first published. The full edition records that moment (_gmbg_published) the first time a product moves to Published, so a draft written in March and published today is new today; editing a published product, or unpublishing and republishing it, does not reset it. A product published before the plugin was installed has no such record and counts from its creation date instead — which is why an older product can still look "new".
Low stock never shows (Full edition)
The product must manage stock (Inventory → Manage stock?), be in stock, and have a quantity at or below its low-stock threshold. For a variable product, stock managed only on the variations does not make the parent "low".
Moving from the free to the full edition
Install and activate the full edition. Both editions use the option gmbg_badges in the same shape, so every badge carries over. The free edition stands down while the full edition is active; deactivate and delete it.
Going back to the free edition
Your badges stay. The first three are shown, top left, in the plugin's own style; corners, shapes, colours and schedules stay stored and are used again if you return to the full edition. Badges with the new, low-stock or featured condition are not shown.
What does uninstalling remove?
- Free edition: the
gmbg_badgesoption, but only if the full edition has never been configured or licensed on this site. - Full edition: its settings and badges, the licence state, the cached update payload, the licence-check cron event and the first-published date it wrote on products (
_gmbg_published).
Neither edition changes anything else on a product.
