Credits & account / PRODUCTION GUIDE
Which credits expire first, and which balance does a generation use?
Read the dates of the individual credit pools before planning future work from one total balance. Current allocation uses valid expiring pools in earliest-expiry order, then any remaining earlier balance. The amount available for your real request depends on its timing, current quote, access and account records.
Look at the dated balances behind the total
Open Credits & account and inspect the credit-balance entries available to your account. Separate a monthly pool, a rollover pool, an extra-credit pool and an earlier balance when they are shown. They need not share the same expiry. A displayed total answers an availability question at that time; it is not a promise that the whole amount will still be spendable on a later campaign date.
Use the pool dates shown for your intended operation. The worked alternatives below illustrate why the request time matters; they are not published plan entitlements or rates.
Follow expiry order for valid pools, then the remaining balance
The current wallet allocates a new reservation from valid pools with available amounts in earliest-expiry order. When expiry times tie, creation order and a stable pool order resolve the allocation. Any remaining required amount then comes from the earlier balance. The system does not simply choose the pool whose name sounds most closely related to the requested tool.
The worksheet below compares allocation before and after an expiry. Read the applicable quote and account adjustments before relying on its arithmetic.
Adobe says its monthly generative credits do not roll over. That is Adobe’s policy, not the allocation or rollover rule for CartVisual. Use this account’s own dated pools and terms.
Build an expiry worksheet for the actual work date
| Record | Read from your account | Planning question |
|---|---|---|
| Monthly or rollover pool | Available amount and expiry | Will it still be valid when work starts? |
| Extra-credit pool | Its own dated amount | Which pool expires sooner? |
| Earlier balance | Shown remaining allowance | What remains after pool allocation? |
| Current operation quote | Requested feature and credit amount | Is access allowed and allowance sufficient? |
| Credit adjustment or refund | Recorded source and outcome | Has the usable total changed? |
In the example, postponing the operation until after the monthly pool expires changes the applicable allowance. Do not treat a previously viewed quote as a reservation of that pool through its deadline. When the account display leaves timing unclear, obtain clarification rather than inventing an expiry hour. An external calendar reminder is your planning aid, not an automatic spending feature.
Compare two fictional alternatives from the same untouched starting balance: monthly M has 40 credits expiring October 23 at 10:00 UTC, add-on E has 60 valid until November 30, and the earlier balance has 30. Assume the request is allowed, its quote is 55, and there are no other jobs or adjustments.
| Alternative request time | Allocation in this example | Available amount left afterward |
|---|---|---|
| October 22, before M expires | 40 from M, then 15 from E | 45 in E plus earlier 30 = 75 |
| October 24, after M expires | 55 from E; expired M is unavailable | 5 in E plus earlier 30 = 35 |
These are alternatives, not two consecutive requests. The earlier balance is not used in either branch because valid pools cover the quote. The amounts, dates and 55-credit quote are invented, not plan entitlements or a current price. Check your actual pool dates and request quote; an old balance screenshot does not reserve credits through expiry.
Keep refunds and renewal separate from expiry
A recorded refund can return allowance to the source pool, but that does not remove the pool expiry. A return to an expired source is not newly spendable. Existing source adjustments can also affect the returned usable amount. Compare the actual job and credit records when reconciling a result. The tutorial cannot infer the account outcome from a loading error, an unsuccessful preview or a balance screenshot taken at a different time.
Renewal and rollover follow the applicable paid-period and account rules. Do not assume every leftover monthly credit carries into another period or that every receipt creates the same deadline. Read the entries actually shown after reconciliation. The hypothetical worksheet deliberately supplies no fixed number of expiry days, renewal price or guaranteed rollover amount.
Feature access remains a separate check. Enough credits do not necessarily grant the requested membership feature, and an active membership does not make an arbitrary future workload affordable. Review both conditions before starting. If an account adjustment changes availability, resolve it from the recorded account evidence rather than forcing the arithmetic to match an older planning note.
The current CartVisual credit terms describe source expiry and failure returns. If the allocation is not visible in your account, mark that split unknown and ask support to reconcile the task; do not infer it from this worksheet.
Schedule useful work without inventing urgency
Plan only requests you actually need and can review. An approaching expiry is not a reason to generate a large collection of unverified candidates merely to exhaust allowance. In the example, an approved source and clear buyer question matter more than spending all forty early credits. Download and reuse suitable accepted assets when another generation would add no needed information.
Use membership versus credit access to check permission separately. The accepted-asset cost guide helps compare allowance spent with usable results. Preserve a dated planning note and refresh it when the operation, timing or account record changes. Actual balances, expiry and charges always come from the current account workflow, not the invented example.
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- CartVisual: editorial scope and evidence policy · Review date not separately recorded
- Adobe: generative credits and eligible operations · Reviewed
- CartVisual: current credits, expiry and failed-task terms · Reviewed
Frequently asked questions
Does every credit pool have the same expiry?
No single common expiry should be assumed. Read the dates of the pools shown in your account.
Which allowance does a new generation use first?
Current allocation uses valid available pools in earliest-expiry order, with tie ordering, then the remaining earlier balance. Check the actual reservation and account records.
Does a refund make expiring credits permanent?
No. Returning credits to a source pool does not remove its expiry. Use the recorded outcome to determine current usable allowance.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in CartVisual.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Explore asset creation tools Check pricing and credits