Skip to content
Badgy Help

templates assets

Manage reusable fonts

Learn how to manage reusable fonts with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Reusable fonts must be licensed for web use and tested for fallback, weight availability, load behavior, and legibility. A missing custom font should degrade to a readable configured fallback.

Before you begin

  • Confirm the asset is approved for storefront use
  • Know which campaigns depend on it
  • Keep source artwork and licensing records

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

Step-by-step setup

Manage reusable 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 a purpose-based font name, choose a licensed supported web-font file, upload it, and wait until its status is Ready.
  3. Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
  4. Apply it in a draft and verify fallback, available weight, load behavior, and mobile legibility before deleting any dependency.
  5. Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.

Reusable fonts must be licensed for web use and tested for fallback, weight availability, load behavior, and legibility. A missing custom font should degrade to a readable configured fallback.

Juniper & Trail example

Juniper & Trail names the reusable item Trail Weekend — Manage reusable fonts and tests it in a fresh draft rather than changing the active 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

Templates are not visible by themselves; shoppers see the campaign-specific configuration created from them. 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 Manage reusable 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 | | --- | --- | --- | | Ready | Font passed processing | Available to editors | | Fallback | File fails or loads slowly | Text remains readable | | Delete | Font is no longer needed | Review existing designs 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?