Changes, Quotas and Volume Bands
What counts as a change, what is free, where the use is shown, what happens at the limit, and how volume bands and extensions work.
Draft brief for authors. Replace with the final text; keep the structure. Reconcile the notice thresholds (catalog: 80 % and 100 %; application: fewer than 5 % left and at the limit).
Page type: Concept · Audience: Buyer, Administrator, Processor
Contains
- What counts as a change: one record sent to SAP for create, update, delete or an operation, whether SAP accepted or rejected it.
- What is free: reads, value helps, uploads, Mass Edit, previews, operations SAP already shows as done, unchanged records skipped.
- Where the use is shown (the notice in Staging Records, the assistant's capabilities answer); what happens at the limit: a new run is refused, a running background run pauses with "Add-on quota used up", uploading and editing continue; how a quota is extended and the paused run resumed.
- Volume bands and prorated upgrades; development and quality systems.
Related information: plans, managing-add-ons-and-quota, pause-resume-stop, concept-quota.
Source in the product repository: customer guide §4 "Quota", srv/lib/feature-metering.js, catalog FAQ.
Last updated: