Two clocks start the day Amazon publishes the report, and they run at the same time. A Plan of Action within 7 days, and remediation inside 21 days for High findings and 60 days for Moderate, counted from the publication date. The Plan of Action window does not extend the remediation window, the days are calendar days, and no extensions are granted.
🔴 A note on where these numbers come from, before you plan against them. Amazon does not publish this process in its SP-API developer documentation. We checked: the vulnerability management guide states the 7 day and 30 day windows from clause 2.7.3 and says nothing about an assessment portal, a Plan of Action, an assessor or a 21 and 60 day schedule. Everything on this page is what the assessment notices Amazon issues to Solution Providers state, observed in October 2026. A single observation is one data point, not a published constant. Your severities, your dates and your deadlines are in your own report and your own portal, and those are the ones that bind you. Read this as a map of the process, then confirm your own numbers.
This is not the clause 2.7.2 clock
The most common confusion is worth clearing first, because it changes who should be worried.
| Your DPP obligation | Amazon’s assessment of you | |
|---|---|---|
| Who finds the issues | You, through scanning, code review or your own pentest | Amazon |
| Who sets severity | You | Amazon |
| The clock | 7 days critical, 30 days high, from discovery | 21 days High, 60 days Moderate, from report publication |
| Day counting | Not specified | Calendar days |
| Who closes it | You | An Amazon assessor |
| Source | Published in developer docs | Not published in developer docs |
Clause 2.7.2 requires a penetration test at least every 365 days, and clause 2.7.3 sets the 7 and 30 day remediation windows. Those are yours. The full reading of that clause, including which restricted roles pull you into section 2 at all, is on our SP-API DPP pentest pillar.
Passing your annual test does not exempt you from an assessment, and an assessment does not replace the annual test.
What the Plan of Action has to contain
One Plan of Action per finding, filed against the tasks listed as Unresolved. Three required elements:
- The actions you will take to remediate the finding.
- The resources allocated to that work.
- A timeline with projected completion dates.
Each task also carries an Estimated Completion Date, which is that individual task’s due date rather than a guideline.
Our SP-API DPP evidence checklist sets out the eight areas Amazon asks a Solution Provider to produce under the Data Protection Policy and its Solution Provider Security Assessment, which is the document set an assessor is working from.
The resources line is the one providers underweight. Against a High finding on a 21 day calendar clock, “internal team, best effort” invites a follow up question from the assessor and burns days you do not have. A provider who can name an engaged external firm, with an engagement letter behind it, is answering the question as it was asked. That is a practical argument about the Plan of Action rather than a claim about what clause 2.7.2 requires, which is a separate and genuinely unsettled question covered on the pillar.
The two traps
These are the ones that cost real days, and both are stated in Amazon’s own guidance to providers.
Uploading is not submitting
Your response and your evidence do not reach the assessor until the Submit Task step is completed. Attaching files is not the same as submitting them.
A provider who attaches files and writes a reply has done work that Amazon cannot see. The sequence that actually registers:
- Open the finding from the Unresolved Tasks queue. Not Incomplete Blocking Tasks, not Unverified Tasks. Unresolved is the queue that carries the findings you must answer.
- Actions, then Upload file, tick the acknowledgement, submit the files.
- Add your written response in the Correspondence section.
- Actions, then Submit Task, and confirm.
Step 4 is the one that matters. On a calendar clock with no extensions, days lost to “we already submitted that” are days you cannot get back.
Email replies are not processed
Responses go through the portal, or through a Seller Central or Solution Provider Portal case. A reply sent from your mail client reaches nobody who can action it.
What “enforcement” actually means in the contract you signed
The assessment notices say Amazon may take enforcement actions affecting your SP-API access. That is vague, and the agreement behind it is not. The Solution Provider Portal Agreement is a published document you can read, and it sets out two removal paths with very different clocks.
The slow one is for Amazon’s convenience. Under clause D-4, “We may also remove, suspend, or modify any listing for your Application from the Amazon Appstore with 30 days’ advance notice.” Section 4.2 carries the same 30 days for terminating the agreement “for convenience”.
The fast one is the one an assessment puts you on. The next sentence of D-4: “We may remove, suspend, or modify any listing for your Application from the Amazon Appstore immediately in accordance with Section 4.”
So what is Section 4? It lists what lets Amazon “suspend or terminate your use of the Portal or any Solution and this Agreement immediately”. Sub-clause (e) is the one that matters here:
“(e) you fail to comply with any identification verification (“IDV”), permission vetting, data handling or data processing requirements”
🔴 Data handling is the Data Protection Policy. Non-compliance with it is named, in Amazon’s own agreement, in the list that permits immediate suspension. Not thirty days. Immediately.
There is a cure period, and it is seven days, and Amazon can waive it. Sub-clause (a) covers material breach: “you have materially breached the Agreement and failed to cure within 7 days of a cure notice unless your breach exposes us to liability towards a third party, in which case we are entitled to reduce, or waive, the aforementioned cure period at our reasonable discretion.”
Read those together and the real shape of the clock is sharper than the notice language suggests. The 21 and 60 day remediation windows are the deadlines the assessment gives you. The agreement is what sits behind them if you miss, and it does not promise you a month to sort it out.
Source: Amazon Solution Provider Portal Agreement, clauses D-4, S-4 and Section 4.2, read at sellercentral.amazon.com/solution-provider/agreement on 21 October 2026. We re-check this document automatically and the text above was verified unchanged on that date. Clause lettering is Amazon’s own.
You are finished when Amazon says so
The overall status moves from Draft to Signed Off and Approved, and only once the assessor has validated and approved all of your responses and evidence.
An empty task queue is not completion. Build the schedule around the assessor’s review time, not just your own remediation time, because the review sits between your last submission and the status that ends the process.
What this means for how you plan
Three practical consequences, in the order they bite.
The pentest is not the end of the work. Most providers budget for the test and nothing after it. The phase that carries the real deadline pressure is remediation and evidence, under a calendar clock, against a human reviewer who can ask for more. Budget attention for that phase specifically.
Retest timing matters more than it looks. If an assessment finding needs a fix validated, you want the retest when your fixes land rather than on a fixed schedule. Both our plans include a full retest triggered when your fixes are in, and no later than one month from the v1.0 report, closing with a v2.0 report that supersedes v1.0 with updated status per finding and fresh proof for each fix. That is the format an assessor can read.
The qualifying question answers itself here. We ask every buyer what date or gate makes this have to happen and what delay costs. Inside an assessment the answer is exact: a published report date, a fixed count of calendar days, no extensions, and SP-API access as the thing at risk.
If you are inside one of these now and the deadline is the problem rather than the testing, tell us the date and what is at risk and we will tell you honestly whether we can help inside your window.