New Badge

(BU)New Badge adds a label such as New or Just In to a WooCommerce product. Show it automatically for a fixed number of days, or use a custom field to decide which products get the badge. You can place it beside a title or over a product image without changing the product itself.

Before you start: Go to Bricks → BricksUltimate → General Elements and enable Badge. That is the name in the settings; in the Bricks editor the element is named (BU)New Badge. Save your settings and reopen the editor.

Add the Badge to Products


  1. Open a WooCommerce single-product template or a custom product grid in Bricks. Add (BU)New Badge and set Using in to WooCommerce.
  2. Leave Product ID blank in single-product templates and query loops. Inside a loop, place the badge inside the repeated product card so each item is evaluated individually.
  3. Choose Days or Dynamic data(Custom field) under Filter by and configure the rule below.
  4. Set Badge Text, style the element, and check the published page with one qualifying product and one that should not show the badge.

On a regular page with no current WooCommerce product, enter a numeric Product ID to check a particular product. This is a fallback: if a WooCommerce product is already in context, the element uses that product rather than replacing it with the entered ID.

Choose When the Badge Appears


Days: Mark Recent Products Automatically

Choose Filter by → Days and enter an age limit, such as 14. The badge appears while the WooCommerce product's creation date is less than 14 days old. A product created 7 days ago qualifies; one created 30 days ago does not.

Days is a rolling age window. A product stops qualifying once it reaches that age. Editing a description, changing a price, or restocking does not reset the creation date. Use a positive number of days. The Days control also accepts dynamic data, so you can read a per-product duration from a numeric custom field.

Dynamic Data: Choose Products Manually

Use this mode for a curated launch, a restock you want to highlight, or an older product that should carry a campaign label. This rule does not expire based on the product's age.

  1. Create or use a product custom field that returns a consistent text value. For example, set a field named badge_status to new on the products you want to label.
  2. Choose Filter by → Dynamic data(Custom field). In Dynamic data, use the Bricks dynamic data picker to select the custom field for the current product.
  3. Set Returned value to new. The badge appears only when the rendered field value and the expected value are non-empty and match exactly. Use consistent capitalization and avoid trailing spaces.
  4. Set Badge Text to the customer-facing label, for example New Arrival. The label and the value used for matching are separate.

If you use a select field, confirm what its dynamic tag actually returns: the saved value and the displayed option label may differ. Check the output in a temporary Bricks text element before setting Returned value.

Using the WordPress Post or CPT Option

The editor also offers WP Post or CPT. Its Days rule reads the post's publication date. In the current implementation, however, rendering the badge text still depends on a WooCommerce product object. Do not rely on this mode in a plain post or custom post type template without verifying it on staging. For non-product content, a Bricks text element with your own visibility condition is an alternative.

Style and Position the Badge


  • Badge Text: Use a short label such as New. This field also supports Bricks dynamic data when the visible label should vary by product.
  • Tag: Use span for an inline label or div for a standalone element. Use the display control to determine how it takes up space.
  • Size & Layout: Adjust width, height, margin, padding, background, and typography. For a compact label that grows with the text, choose inline-block, leave width and height unset, and use padding. For a flex layout, use Justify Content and Align items to position the text.
  • Image overlay: Put the badge inside the image wrapper. In Bricks, set the wrapper to Relative and the badge to Absolute, then set the top and side offsets. Leave room for other overlays such as a sale badge or wishlist button, especially on mobile.
  • Hide In-Builder Editor? Hides the demonstration badge in the editor only. The storefront still follows the configured rule. Seeing the demo text in Bricks does not mean the product qualifies.

The standalone element is separate from the native Bricks WooCommerce Products element's New badge controls. Use the standalone element in custom cards or templates. If a native badge is already visible in the same layout, avoid rendering both.

Troubleshooting


  • The element is missing: Enable Badge under General Elements, save, and reopen the builder.
  • It appears in the editor but not on the storefront: The editor shows a preview. Verify the product's creation date or custom-field output, and make sure Badge Text is set.
  • All cards show the same result: Confirm the badge is nested inside the repeated card, the query returns products, and Product ID is blank.
  • The badge did not disappear when expected: Check whether Days or Dynamic data(Custom field) is selected. Only Days expires automatically; page caching can also delay a visible change.
  • A restocked product is not new: The Days rule does not use the restock date. Use a custom field if you want to promote new stock on an older product.

To highlight sales volume instead of product age, see the Best Selling Badge guide. For image framing and overlays, see Product Image.