Managing AI Credits And Usage

Go!BrightCart tracks AI drafting through team-based credits so sellers can control usage instead of guessing at cost.

Where to manage AI credits

Open Seller Settings to review:

• current AI credit balance
• monthly included credits
• purchased remaining credits
• cost per AI action
• hourly drafting limit on the current plan
• usage reporting for the current month
• available credit packs
• recent AI credit activity

If you need help with the actual drafting workflow, start with Using AI For Product Content.

How credits work

AI usage is tied to the active team.

The seller settings dashboard separates:

• monthly included credits that reset automatically
• purchased credits that stay available until used

When you spend credits, Go!BrightCart draws down the team balance and records the action for reporting.

Which actions consume credits

The current product AI workflow tracks two main action types:

• product draft for the initial prompt-based draft and draft refinements
• product field generation for single-field drafting such as subtitle, description, FAQ, specs, meta title, or meta description

The exact credit cost is plan-dependent, so the current source of truth is the AI credit panel in seller settings.

Monthly limits and hourly limits

Go!BrightCart can enforce both:

• a credit balance limit
• an hourly action limit

If your team reaches the hourly limit, AI actions are blocked until enough time passes for the rate limit window to clear.

If your team runs out of credits, new AI requests are blocked until the monthly pool resets or more credits are purchased.

What the usage dashboard shows

The AI usage view helps answer more than just “how many credits are left.”

It includes:

• credits used this month
• successful actions
• blocked attempts from low balance or rate limits
• credits purchased this month
• action breakdown by AI workflow
• top store consumers
• model mix and token volume
• recent AI issues
• recent AI credit activity with running balances

This makes it easier to see whether usage is healthy, concentrated in one store, or being slowed down by preventable blocked attempts.

Buying more credits

If AI demand is outgrowing the included monthly pool, use Buy More AI Credits in seller settings.

Purchased packs are useful when:

• a launch week creates a burst of catalog work
• one team member is doing a large cleanup pass across many products
• you want extra room before the monthly reset

How blocked requests appear

An AI request can be blocked when:

• your team has no active credit balance left
• your team has reached the hourly AI drafting limit
• AI drafting is not configured
• there is no active team context for the seller

Blocked attempts still matter operationally because they explain why sellers may feel the assistant is inconsistent. The usage dashboard surfaces these events so they are visible instead of mysterious.

Best practices for keeping usage healthy

• Use full drafting for blank-page work and field-level drafting for smaller edits.
• Review action breakdowns to see whether the team is spending more on full drafts than expected.
• Check top store consumers if one storefront is absorbing most of the monthly pool.
• Use purchased top-ups for concentrated catalog projects instead of waiting on the monthly reset.
• Watch blocked attempts so you can distinguish true provider problems from simple credit or rate-limit exhaustion.