Skip to content
Badgy Help

settings

Add custom storefront fonts

Learn how to add custom storefront fonts with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Upload only licensed web-font files, provide a readable fallback, and test supported weights on mobile. Font configuration should not delay essential campaign text from becoming readable.

Before you begin

  • Shop-owner or authorized staff access
  • A record of the current setting
  • A plan for how the change affects scheduled campaigns

Confirm the shop, current status, and intended consequence before changing anything. Use read-only status, preview, or history evidence first.

Step-by-step setup

Add custom storefront fonts shown in the Badgy admin, with numbered callouts for the controls and verification points described below.
Annotated Juniper & Trail example

  1. Check the current plan before configuring plan-dependent settings.

  2. Set and save the default timezone used when creating campaigns.

  3. Review Shopify Markets synchronization availability and its plan requirement.

  4. Name and upload an approved custom font for storefront campaign components.

  1. Open Settings → Custom fonts for the intended shop and confirm the current record and status.
  2. Enter the font name and choose a licensed file, upload, wait for Ready, and only then select it in badge/banner design; use Delete for an unused font.
  3. Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
  4. Verify fallback and every used weight on storefront desktop/mobile before relying on it.
  5. Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.

Upload only licensed web-font files, provide a readable fallback, and test supported weights on mobile. Font configuration should not delay essential campaign text from becoming readable.

Juniper & Trail example

Juniper & Trail records the current value, applies add custom storefront fonts, and verifies a draft preview before relying on the change for its next campaign. The documentation fixture uses realistic products, inventory states, variants, collections, and protected exclusions so the preview exercises the same decisions as a merchant catalog.

What shoppers will see

Some settings affect only admin presentation; storefront-facing settings should be checked in every supported locale and market. Check the relevant result from product through cart where applicable. For shopper-facing work, compare desktop and mobile and verify both an eligible and an ineligible item.

Common mistakes and troubleshooting

  • Acting on the wrong shop. Confirm the Shopify store and campaign before following Add custom storefront fonts.
  • Trusting a stale preview. Refresh after catalog, schedule, discount, theme, locale, or market changes.
  • Repeating a background command. Read status and History first; retry only when Badgy presents a recoverable failure.
  • Skipping the consequence check. Confirm what changes for shoppers and what the end or restore path will do.

If the status reports revoked authorization, reconnect Shopify before retrying. If the result still differs from the preview, preserve the campaign ID and approximate time, then open support from this identified shop. Never send customer data, access tokens, or full catalog exports in feedback.

Options reference

| Option | Use it when | Consequence | | --- | --- | --- | | Upload | Add licensed web font | Processing status follows | | Ready | Usable in design | Still test storefront | | Delete | Remove unused font | Audit dependent templates first |

Badgy behavior in this guide is reviewed against the repository's shipped UI, service rules, and feature design documents. Shopify-owned theme, Markets, Flow, billing, and discount behavior can also depend on the store's Shopify configuration; consult the Shopify Help Center for that platform configuration.

Was this guide helpful?