Tested trust badge placements on Dawn and Horizon

Before you add a trust badge, it helps to know where it can sit in your theme. A promise about returns reads differently above the price than under the buy button, and a badge in the cart drawer has less room than one on the cart page.

This guide sums up the automated placement tests we run for YeahBadges on the free Shopify themes of the Dawn and Horizon families. It covers what was tested, where each place ends up and what the tests do not cover. The results describe our app, but the way these themes are built is the same for any badge you add.

Two families of free themes

The free themes tested here come in two families. Each family shares most of its code, so a place behaves alike across the themes of one family. The tests cover the 23 free themes the Theme Store listed in early October 2026:

Within a family, the differences that matter for badges are the cart type and a few special sections. Trade, for example, sells through a quick order list.

How the tests work

For each theme, a tool saved the product page and the cart page of its demo store, with a product in the cart. These are the standard templates of each theme in its demo store. The test suite then loads every page at a desktop width of 1280 pixels and a phone width of 390 pixels, in Chromium and in WebKit, the engine of Safari.

The pages load without a network connection. The theme's own stylesheets and scripts come from the saved files, so layout and cart drawer work as in the store. One badge sits at every place, and the tests check for each theme and width:

• exactly one visible badge at each place,
• the badge sits where the place says, measured against the price, the buy form, the footer or the checkout button,
• nothing overflows the page sideways,
• the badge script reports no error.

The suite runs with every regular test run of the app, so a change that breaks a place shows up in the tests.

Product page: six places

All six places showed exactly one visible badge in all 23 themes, at both widths. From top to bottom:

Every place except the last one stays in the column of the buy form, also on a phone, where that column fills the screen. One theme needs a note: Trade puts its quick order list in a section below the product information, so the end of the product information sits above that list.

Which place suits which badge is your call, but a few patterns are common. A short delivery note fits after the price. Promises about shipping, returns and secure payment fit under the buy buttons, where the shopper decides. Payment icons fit close to the buy button too. Before the footer is a place for longer information that should not push the buy button down.

Cart page: top and bottom

On the cart page, the top place sits before the cart form in both families. The bottom place differs:

• In the Dawn family, it sits just below the checkout button.
• In the Horizon family, it sits after the checkout button and the express payment buttons.

The demo stores show no express payment buttons. In a separate check on Dawn with such a block added by hand, the bottom badge moved below that block.

Cart drawer and added to cart popup

What opens after a shopper adds a product depends on the theme, and so do the places:

• Dawn, Craft, Sense, Studio, Ride, Taste, Crave, Colorblock, Spotlight and Trade show a popup with "Item added to your cart". The top and bottom badges appear in that popup, as wide as its checkout button.
• Refresh, Origin and Publisher open a drawer. Both badges sit inside it, as wide as the drawer. The bottom badge sits after the cart items and above the area with the checkout button, not directly under the button as on the cart page.
• The Horizon family opens a drawer. Both badges sit inside it, as wide as the checkout button, with no duplicates.

A badge fixed to the screen

Besides the fixed places, a badge can stay on screen while the shopper scrolls, and a sticky bar can show at the bottom edge on phones. Both were checked in every theme: the badge stays in view after the page scrolls, and the bar appears on the phone width only.

What the tests do not cover

Tests are only as good as their limits, so here they are:

• Demo store pages, not your store. The pages use each theme's standard templates. Your own templates, added sections and code changes can move a place.
• No theme fonts and images. Text falls back to another font and images are empty boxes of the same size. Line breaks and heights differ from a real store; the order of the places does not.
• No platform buttons. Wallet and express checkout buttons come from Shopify at runtime and are missing from saved pages.
• The state of October 2026. The pages were saved on October 11, 2026. When Shopify updates a theme or adds a new free theme, the results apply to the old state until the pages are saved again.
• Free themes only. Paid themes and themes from other developers are not part of these tests.

Check placement in your own store

Whatever tool you use, a short round in your own store catches what a test cannot:

1. Open a product for each product template you use, on desktop and on a phone.
2. Add the product to the cart and look at the drawer or popup.
3. Change the quantity, then open the cart page.
4. If a badge is missing at one place, try the place next to it.

How YeahBadges handles it

In YeahBadges, the six product places are the choices of Place on the product page, and the cart places are Top of cart and Bottom of cart. The app lists the tested themes in its store check under Tested themes. If a badge does not find its place in another theme or a changed template, the store check reports it, and free placement lets you drag the badge to a spot on your real store page in the preview. For the causes behind a missing badge, see Trust badge not showing on Shopify; for the drawer, see trust badges in the cart drawer.