Read The Sync-Mode Rules
Open the related page.
Resources
What Is A Credit
A credit is the customer-facing unit WPFlow uses to estimate, approve, reserve, and settle scoped WordPress work. It is not a developer hour, token amount, or internal supplier-cost disclosure.
Short Explanation
A credit is WPFlow's customer-facing unit for scoped WordPress work, not an hour, token, or internal cost metric.
- Architect scopes the request and shows an estimated credit cost before build work starts.
- The approval cap is the maximum credit amount the customer has approved for that request unless a revised scope is approved.
- PAYG credits are GBP 1 per credit in the current GBP price book, with a 5-credit checkout minimum.
- Core and Pro bundle monthly credits at a lower effective rate for regular one-site work.
- Automatic top-up can buy quantity-based PAYG credits inside the monthly budget cap the customer sets, but it never approves work or live publishing.
Example
A simple example or comparison usually makes the rule easier to understand.
| Credit truth | What it is not |
|---|---|
| A public unit for scoped work and approval caps | A timesheet or open-ended retainer hour |
| PAYG capacity from GBP 1 per credit | A fixed multi-credit pack |
| A capped spend control before build starts | Surprise overage after the work is done |
Related Links
Useful next reading if you want the full delivery context.
Next step
Want To See How This Applies To Your Site?
Use the signup flow and describe the kind of changes you need.