Skip to content
Badgy Help

billing

Understand plan limits

Learn how to understand plan limits with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Feature gates and usage limits depend on the current normalized plan. Review the limit before scheduling a campaign and do not assume a draft proves launch entitlement.

Before you begin

  • Shop-owner billing permission
  • The feature and usage requirement
  • Awareness that Shopify presents and confirms app charges

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

Step-by-step setup

Understand plan limits shown in the Badgy admin, with numbered callouts for the controls and verification points described below.
Annotated Juniper & Trail example

  1. Review the Free plan limits and included capabilities.

  2. Compare the Essential plan, price, limits, and support level.

  3. Compare the Pro plan and its unlimited campaign capabilities.

  4. Check current usage against lifetime campaign, product, and AI-credit limits.

  1. Open Plans → Usage for the intended shop and confirm the current record and status.
  2. Read campaign, lifetime product-update, billing-period update, and AI-credit meters in the context of the current plan.
  3. Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
  4. Verify entitlement before launch; creating a draft does not prove a metered launch can proceed.
  5. Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.

Feature gates and usage limits depend on the current normalized plan. Review the limit before scheduling a campaign and do not assume a draft proves launch entitlement.

Juniper & Trail example

Juniper & Trail checks whether understand plan limits is needed for its planned recurring promotion and confirms current price and approval on Shopify's hosted billing page. 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

Billing changes do not directly alter the storefront; avoid changing plans in a way that interrupts a scheduled feature without first reviewing its campaign. 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 Understand plan limits.
  • 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 | | --- | --- | --- | | Free campaigns | 10 lifetime | Launch gate | | Free updates | 10,000 lifetime | Product-write gate | | Essential updates | 10,000 per billing cycle | Cycle meter | | AI credits | Free 10 lifetime | Generation gate |

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?