troubleshooting
Contact Badgy support with useful context
Learn how to contact Badgy support with useful context with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Open support from an identified Help session so the correct shop, guide, heading, and bounded recent Help trail are attached. Include campaign ID, time, status, and failure code—never credentials or customer data.
Before you begin
- Do not repeatedly launch, end, or restore while a job is running
- Capture the campaign ID, status, and approximate time
- Check Shopify authorization and theme status first
Confirm the shop, current status, and intended consequence before changing anything. Use read-only status, preview, or history evidence first.
Step-by-step setup
Use the summary cards to check live, scheduled, and sale-product totals.
Inspect the active campaign and use its view, edit, revert, or end actions.
Check theme embed, badge, banner, background-job, and countdown health.
Search and filter past campaigns before opening their records.
- Open the relevant Help guide from the identified shop for the intended shop and confirm the current record and status.
- Start chat with the current guide/heading attached and provide campaign ID, approximate time, status, and failure code—never tokens, customer data, or full exports.
- Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
- Confirm the support trail shows the bounded guide context, not merchant-entered form/catalog values.
- Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.
Open support from an identified Help session so the correct shop, guide, heading, and bounded recent Help trail are attached. Include campaign ID, time, status, and failure code—never credentials or customer data.
Juniper & Trail example
Juniper & Trail uses contact badgy support with useful context on one affected campaign, records its status and failure code, and avoids starting a second command while recovery runs. 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
Prioritize price correctness and misleading offer removal. If the storefront message is wrong, use the documented safe stop path while recovery continues. 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 Contact Badgy support with useful context.
- 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.
Related guides
Options reference
| Option | Use it when | Consequence | | --- | --- | --- | | Identified chat | Merchant needs account support | Shop + bounded Help context | | Guide feedback | Documentation issue | Structured reason first | | Anonymous | Public reading/rating | No merchant chat |
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.