Quick answer: Amazon does not publish a sales velocity limit, so there is no number you can stay under. What Amazon does say is that it may reserve funds if it notices an unexpected change in your sales or account activity, and that it may deactivate an account immediately if it suspects fraudulent or deceptive activity. A sudden spike in orders, a burst of new listings or an abrupt jump in category or price can resemble a compromised or abused account. The response is not an apology. It is proof: the dated cause of the growth, supplier invoices covering the units you sold, evidence you fulfilled them, and evidence the same owner and bank controlled the account throughout. Build that file before a planned spike, not after.
Most sellers meet a velocity review in their best month. A launch works, a deal lands or Q4 arrives, and the payout that should have been the largest of the year shows as reserved, or Account Health shows a review, or selling privileges are switched off. The seller changed nothing except size. That is what makes these cases frustrating, and also winnable: if the growth was real and the supply genuine, the evidence exists, and the job is to assemble it in a form a reviewer can check quickly.
This guide covers how reserves and reviews work around sudden growth, how to tell an ordinary reserve from an enforcement hold, what documents Amazon asks for, how to prepare before a planned spike, and how to build the plan of action if the account is already deactivated. If funds are held on a closed account, see our disbursement and funds hold service alongside the evidence sections below.
What a velocity review actually is
A velocity review is Amazon slowing or stopping an account because its behavior changed faster than its history predicts. “Velocity” is a seller term, not an Amazon policy name. Amazon’s account level reserve page lists “your account is under review” as a common reserve reason and says it might reserve funds if it notices an unexpected change in your sales or account activity. The trigger is unexpected change, judged against your own history, not growth itself.
The reason is that legitimate success and risk can look alike in the numbers. An account that has been sold or taken over often changes category, price and volume at once. An account selling goods it cannot source sells more units than its supply supports. The review is where Amazon asks you to show which situation it is.
The patterns that tend to draw scrutiny
Amazon does not publish its triggers, and none of these is an Amazon rule. They are patterns we see associated with reviews in practice:
- A sales spike out of line with history. Orders or revenue rising sharply over days or weeks.
- A burst of new listings. Hundreds of offers created in one feed upload, often before sales move.
- An abrupt category or price shift. A seller of low-priced accessories suddenly listing high-value electronics.
- A change in fulfillment pattern. Switching channels, ship-from locations or handling times suddenly.
- Growth alongside an access or banking change. New users, changed logins or a new deposit method in the same window. This is the strongest takeover signal.
Which pattern applies decides what you must prove. A sales spike needs sourcing proof. A listing burst needs proof the line is legitimate and authorized. A pivot needs proof of continuity of control. An access or bank change needs a full account of who changed what and why.
Velocity alone, or velocity plus authenticity
A velocity review often arrives with a second flag, usually an authenticity complaint, because a sudden rise in sales raises the question of whether you could source what you sold. That combined case is worked as an authenticity case, with the growth as context. If your notice cites inauthentic or counterfeit complaints, read our guide to inauthentic versus counterfeit complaints first.
A growth spike can end five different ways. Pick yours.
Held money, a reserve, a review request and a deactivation look alike from the outside. Each one is read by a different part of Amazon and answered with different proof.
How Amazon holds money around a growth spike
Before treating a held balance as enforcement, separate ordinary machinery from a genuine withholding. Most alarms during a growth month are the normal reserve system working as designed, and no appeal changes it. Misreading it leads to panicked tickets and paying for “release” services that do nothing.
Delivery date reserves, shown as deferred transactions
Amazon’s page on payments based on delivery date says it typically reserves funds until a set number of days after delivery, and that the standard period is 7 days after delivery date, the “DD + 7” policy. Amazon’s example: an item sold January 1 and delivered January 6 has funds available for disbursement starting January 14. These appear on the Payments Dashboard as deferred transactions.
Two details matter in a growth month. Amazon says the reserve period may be extended following an assessment of your overall risk and historical performance, so seven days is not guaranteed. And without valid tracking from an integrated carrier, Amazon uses the latest estimated delivery date rather than the actual one, so untracked orders shipped during a surge release later. Because each order is held until delivery plus the reserve period, doubling orders roughly doubles the deferred balance. That is timing, not a penalty.
The account level reserve
Amazon describes the account level reserve as money held to cover refunds, claims or chargebacks not covered by delivery date reserves, and calls it a normal part of selling. Its listed reasons include open A-to-z Guarantee claims (reserved until resolved, which Amazon says can take up to 14 days or longer), chargebacks from transactions in the last 90 days, performance below Amazon’s benchmarks, the account being under review, and tax withholding where required. Reasons stack: Amazon’s example is a $40 chargeback plus a $20 open claim producing a $60 reserve. A spike raises claims and chargebacks in absolute numbers, so the reserve can grow for ordinary reasons before any review exists.
When the hold is not ordinary
A hold departs from ordinary mechanics when it is tied to an event: a review, a verification request, a performance notification or a deactivation. The rule for every funds case is that funds follow the account. The hold is a symptom and the cause is the case. Resolve the cause and the release follows; write about the money alone and nothing moves.
A worked example: the deal that tripled sales
These numbers are hypothetical. A seller has averaged about 1,500 units a month for two years. In November one ASIN joins a deal and goes from 300 units a month to 3,200 units in three weeks, lifting monthly sales from about $45,000 to $130,000.
The deferred balance grows first. If deliveries average four days, each order’s money is held about eleven days from shipment, so at three times the usual run rate the deferred line sits near three times its usual size, rolling as older orders release. A mid-deal snapshot looks alarming; it is a moving balance. Then the account level reserve rises: say 6 A-to-z claims and 2 chargebacks on the deal ASIN, each reserved while open. Two weeks in, Account Health shows a review and disbursements stop. Now there are three held amounts, and only one is caused by the review.
The response must answer the review: the deal, dated and documented; invoices for at least the 3,200 units sold plus remaining stock of that ASIN; proof the orders shipped on time; and proof nothing changed in ownership, users or banking. “Please release our funds” addresses none of it.
The sourcing arithmetic
The decisive question is arithmetic: does documented supply cover the flagged volume? Amazon’s invoice requirements ask for quantity sufficient to cover your sales volumes and in-stock inventory for each cited ASIN over the past 365 days. If the seller sold 3,200 units and holds 600 more, invoices for fewer than 3,800 units of that ASIN leave a gap a reviewer will see. Reconcile per ASIN before submitting.
Do your invoices cover the spike?
Amazon asks for invoices that cover sales and in-stock inventory for each cited ASIN. Enter your own numbers for one ASIN and see the gap a reviewer would see.
What Amazon may ask for, and the standard documents must meet
Requests after a growth review fall into four groups: supply, the growth driver, fulfillment, and identity and control. Amazon’s funds disbursement eligibility policy says it may request information about your identity, financial instruments or supply chain, and may validate it with third party services or government agencies. Assume everything you send will be checked.
Supplier invoices
Amazon’s invoice requirements page says invoices must show supplier contact information (name, phone number, address and website), an issue date within the past 365 days before the performance notification, sufficient quantity, and clear product identifiers such as model numbers or UPC, EAN or ISBN, with variation details matching your listing and every component listed for bundles. Files must be PDF, JPG, PNG or GIF, no larger than 10MB. You may remove pricing, but everything else must stay visible, and Amazon may contact the supplier to verify.
Amazon will not accept invoices sent by email instead of through Seller Central, quotes or pro forma invoices, self-issued invoices or ones where supplier and buyer appear to be the same entity, manipulated or editable files such as Excel or Word, or illegible and inconsistent documents. Retail receipts fall short for reasons covered in why Amazon doesn’t accept receipts.
Driver, fulfillment and continuity
The driver is the documented, dated cause: the deal or coupon record, the launch purchase order and listing dates, prior year sales for a seasonal peak, or a business customer’s purchase order. It must line up in time with the spike. Fulfillment proof is shipment confirmations with valid tracking, FBA inbound records and your late shipment and cancellation figures for the period. Continuity proof shows the owner, users and deposit method did not change, or explains exactly who changed what and when. Amazon’s funds policy names “falsifying or misrepresenting your identity or activity” among the conduct it looks for, so continuity goes straight to the reviewer’s concern.
| What the reviewer needs to believe | Evidence that proves it | Common weakness |
|---|---|---|
| The growth had a real, dated cause | Promotion record, launch PO, prior year seasonal sales, wholesale PO | Cause asserted with no dates, or dates that miss the spike |
| The units were genuinely supplied | Compliant supplier invoices covering units sold plus stock per ASIN | Invoices covering a fraction of volume; pro forma or self-issued |
| The account fulfilled the volume | Tracking, FBA inbound records, on-time and cancellation figures | Untracked merchant orders; unexplained metric slips |
| Control and banking did not change | User permission and deposit method history, owner identity | A new user or bank account in the spike week, unexplained |
| The supplier is real | Registration, address, website, reachable contact | No web presence or a mismatched address |
How to verify your own position
Everything needed to diagnose a velocity situation is in your Seller Central and your records. Work through these checks before contacting anyone.
| Question | Where to check | What to look for |
|---|---|---|
| Is held money ordinary delivery timing? | Payments, Transaction view filtered to Deferred transactions, or the Deferred transactions report in the Payments Reports Repository | Expected release dates for each transaction, arriving on schedule |
| What makes up the account level reserve? | Payments report Statement View (legacy) or Manage Transactions (new Seller Central) | The reserve figure, then open A-to-z claims and chargebacks from the last 90 days |
| Is there a review or request? | Account Health dashboard and Performance Notifications | Any review or document request, dated against the reserve’s onset |
| Where does account health stand? | Account Health Rating on the Account Health page | Amazon’s bands: 200 to 1,000 Healthy, 100 to 199 At Risk, 99 or lower Unhealthy |
| Did a sent payment arrive? | Bank Transfer ID on the Payments report, or Trace ID in Manage payouts | Amazon says funds can take up to five business days to appear after payment starts; after that your bank can trace it |
| Does sourcing cover the volume? | Order and inventory reports by ASIN, plus your invoices | Units invoiced at least equal to units sold plus units in stock |
| Is the supplier verifiable? | The supplier’s state business registry, found through nass.org | An active entity whose name and address match the invoice |
| Did access or banking change? | User Permissions and deposit method settings | Any change in the spike window, with who made it and why |
If the held money is deferred transactions releasing on schedule, the answer is a release schedule. If the reserve maps to open claims and recent chargebacks, resolve those; Amazon lists that among the ways to get paid faster. If a review or request lines up with the onset, it is an event hold and the evidence file is the work. Note that Amazon’s Account Health Rating page says it may deactivate immediately, regardless of score, if it suspects fraudulent, deceptive, illegal or otherwise harmful activity. A healthy score does not shield an account in a velocity review.
Preparing before a planned spike
The cheapest velocity case is the one you never argue. Nothing guarantees Amazon will not review an account, but a file built in advance lets you answer in hours instead of weeks.
- Buy the supply first, from a verifiable source. Purchase inventory covering the expected volume from a manufacturer or authorized distributor, and check every invoice against Amazon’s requirements on arrival. Store originals unaltered.
- Document the driver in advance. Save the deal confirmation, launch plan, ad schedule or customer purchase order.
- Confirm fulfillment capacity. FBA inbound timing for extra units, or staff and carrier capacity for merchant orders, with valid tracking on every shipment.
- Freeze account changes. Avoid adding users or changing the deposit method or business details around the spike. If you must, document why.
- Stage large catalog uploads. Add a new line in batches, with the distributor agreement and first invoices ready.
- Watch daily during the spike. Check Account Health and notifications, answer requests the same day, resolve A-to-z claims quickly, and keep a running tally of units sold against units invoiced.
- Plan cash flow for reserves. Both reserves scale with volume, so assume part of the spike’s revenue arrives later, and possibly much later if a review occurs.
Is your account ready for the growth you are planning?
Switch on what is already true for your account and watch the readiness level move. The heavier items are the ones a reviewer asks for first.
Building the explanation when a review arrives
A velocity review asks one question: is this volume legitimate and supplied? Treat it as an affirmative proof exercise. There is often no fault to confess, and writing as if there were implies a violation where none exists. Build on three pillars:
- The driver. Name it and place it against the spike: “Units on ASIN B0XXXXXXX rose from about 300 a month to 3,200 between November 4 and 25, driven by a deal running November 5 to 18; deal record attached.”
- The supply. List invoices by supplier, date and quantity, and state the reconciliation: invoiced, sold, in stock. Never round in your favor.
- The continuity. State that ownership, users and deposit method were unchanged, with evidence, or explain any change fully.
If the surge exposed a genuine strain, such as a shipping backlog or a supplier who nearly ran short, add a forward control: who checks supplier capacity before promotions, and how often someone reconciles units sold against units invoiced. That is not an admission; it shows the business is built to scale.
Amazon does not read your story first. It reads this.
Four kinds of spike leave four different trails. Switch between them and tap any line to see what it means and what proof answers it.
Potentially how it looks. A fictitious reconstruction based on Amazon’s published policies and cases we have handled. It is not an Amazon screen or tool, and every figure is invented.
If the account is already deactivated
Amazon’s funds disbursement eligibility policy says you may appeal a deactivation by following the instructions in the notice or in Seller Central, and that if the account is reinstated, funds are released according to your disbursement schedule. The account appeal is therefore also the main route to the money. For timing in general, see how long appealing on Amazon takes.
Diagnose before you write. Record the exact reason, date and any documents requested, run the verification table, and decide whether this is pure velocity, velocity plus authenticity, or velocity with an access or banking change. Answering the wrong case is the most common way these appeals fail. Then build the plan of action:
- Root cause. In a pure velocity case it is usually not a fault but the specific, dated event that changed the account’s behavior. Where there was also a real weakness, such as disorganised invoices or an undocumented access change, name it specifically. Blame no one else.
- Corrective actions already taken, with proof. The per-ASIN reconciliation, the invoices uploaded through Seller Central, any listings paused where supply could not be documented, any access secured, any buyer issues resolved. One exhibit per item.
- Preventive controls with owner and date. A supplier capacity and invoice check before promotions, owned by a named person from a stated date; a weekly reconciliation; a rule that users and deposit details do not change without a documented reason. “We will monitor more closely” does not count.
From deactivation notice to submitted appeal, screen by screen.
Click through the sequence our case team follows. Nothing gets submitted until the last screen is complete.
The separate funds appeal
Amazon’s funds policy says that if it deactivates an account under Section 3 of the Business Solutions Agreement and determines your actions may create risk, it may withhold funds to cover returns, refunds, A-to-z claims, removal costs, fees and damages. Even if the account appeal fails or you do not appeal, Amazon says you can separately appeal for withheld funds by contacting disbursement-appeals@amazon.com at any point after 60 days from deactivation. It says it releases remaining funds, less offsets, after evaluating the account and confirming your identity, and may permanently withhold payments if it finds deceptive or fraudulent activity or cannot confirm identity. For more, see our guide to getting held funds back.
Two tracks start on the day of deactivation. Drag to your day.
The account appeal can start at once. The separate funds appeal opens 60 days after deactivation. Move the slider to the number of days since your notice.
This is educational information about Amazon’s published policies, not legal advice. If a large sum stays held after the ordinary routes, speak with a qualified attorney about your agreement with Amazon.
When genuine documents cannot cover the volume
Viability turns on the supply chain, not the writing. If the units were genuinely sourced, the case is a proof exercise and usually strong. If volume outran documented supply, no narrative fixes it, and a velocity review can become an authenticity investigation.
Never create, edit, backdate or “clean up” an invoice, and never ask a supplier to issue one for a transaction that did not happen as described. Amazon says documents must be authentic and unaltered and that it may verify with suppliers, third parties and government agencies. A fabricated document turns a review into an integrity deactivation; see forged or manipulated documentation suspensions.
The honest paths: request complete genuine copies of misplaced invoices from the real supplier; where some units came from a source whose paperwork falls short, say so, stop selling those units and narrow the appeal to what your documents support; move future sourcing to manufacturers or authorized distributors; and if the facts do not support reinstatement, accept that rather than compound it. Never open another account to get around a deactivation; that is circumvention, a further violation.
Struggling to get it back on your own?
Send us the notice and we will read the case before you pay anything.
Common mistakes in velocity cases
- Apologising for growth. A generic apology and fix answers a question nobody asked.
- Appealing a normal reserve. Ticket after ticket about deferred funds releasing on schedule.
- An undated driver. “We had a great sale” is not evidence; a dated deal record is.
- Partial invoices. A coverage gap will be noticed.
- Documents Amazon rejects. Quotes, pro formas, editable files or emailed invoices.
- Ignoring continuity. An unexplained new user or bank account keeps the takeover question alive.
- Changing details mid-review. New users or banks during a review add a fresh anomaly.
A repeatable routine for growing accounts
- Weekly reconciliation. For top ASINs, compare units sold plus stock against units invoiced and fix gaps before any spike.
- Invoice filing. File every invoice on receipt, unaltered, by supplier and ASIN, checked against Amazon’s requirements.
- Payments review. Weekly look at deferred release dates, the account level reserve, and open claims and chargebacks.
- Account Health check. Daily during events, weekly otherwise; answer requests the day they arrive.
- Change log. Record every change to users, permissions, deposit methods and business details with date and reason.
- Pre-event file. Two weeks before any deal, launch or seasonal push, assemble driver, supply coverage and fulfillment plan in one folder.
For broader stock discipline, read common Amazon inventory management mistakes.
Frequently Asked Questions
Does Amazon have a sales velocity limit?
Amazon does not publish one. Its account level reserve page says it might reserve funds if it notices an unexpected change in your sales or account activity, so the comparison is with your own history.
Why is so much of my money held during a sales spike?
Delivery date reserves hold each order’s money until delivery plus a reserve period, 7 days as standard per Amazon, so more orders mean a larger deferred balance. Open claims, recent chargebacks or a review can add an account level reserve on top.
How do I see when deferred funds will release?
In Payments, open the Transaction view, filter for Deferred transactions and click Update. Amazon says this lists each held transaction with its expected release date.
What documents does Amazon want after a growth spike?
Usually supplier invoices covering units sold and in stock, and sometimes identity, financial or supply chain information. Add dated proof of the growth driver and evidence you fulfilled the orders.
How many units must my invoices cover?
Amazon asks for quantity sufficient to cover sales volumes and in-stock inventory for each cited ASIN over the past 365 days, with an issue date within 365 days before the notification.
Should I apologise in a velocity appeal?
Not for growing. Prove the growth was real, supplied and controlled by the same owner, and name any genuine weakness the surge exposed along with the control you added.
Can I get funds back if the account stays deactivated?
Amazon says you can appeal separately for withheld funds at disbursement-appeals@amazon.com any time after 60 days from deactivation, and it releases remaining funds, less offsets, after evaluating the account and confirming identity.
How long does a velocity review take?
Amazon does not publish a timeline for these reviews. A complete, documented response sent promptly helps, but no one can promise a date Amazon controls.
Get Help With an Amazon Velocity Review or Funds Hold
If growth has led to a review, a held disbursement or a deactivation, our team can help you identify which situation you are in, reconcile supply against the flagged volume and build a documented response. See our Amazon suspension service, submit your case, or book a consultation.
This article is general educational information based on Amazon’s published Seller Central help pages at the time of writing. It is not legal advice and does not guarantee any outcome, timeline or release of funds. Amazon’s policies change; check the current help pages and your own notices before acting.
Sources
- Amazon Seller Central: What is account level reserve?
- Amazon Seller Central: Payments based on delivery date
- Amazon Seller Central: When will I be paid?
- Amazon Seller Central: Funds disbursement eligibility policy
- Amazon Seller Central: Invoice requirements for appealing a policy violation
- Amazon Seller Central: Account Health Rating program policy
