top of page

Common mistakes Amazon suppliers make when pursuing ISO certification

  • Writer: Scott Naisbett
    Scott Naisbett
  • 6 hours ago
  • 2 min read

Suppliers working with Amazon are often under pressure to respond quickly to requests for ISO certification. In that situation, it’s easy to make decisions that seem sensible at the time but create delays, extra cost, or problems later in the process.


This article highlights the most common mistakes Amazon suppliers make when pursuing ISO certification - and how to avoid them.


1. Assuming ISO certification is required without confirmation

Not every Amazon supplier needs ISO certification, and not every request applies universally.


A common mistake is:


  • assuming certification is mandatory,

  • starting work without confirming applicability,

  • or pursuing a standard that isn’t actually required.


The first step should always be to understand what Amazon is asking for and why, before committing time or money.


2. Choosing the wrong ISO standard

Another frequent issue is pursuing a standard that doesn’t align with the business’s actual activities.


Examples include:

  • pursuing ISO/IEC 27001 where no meaningful information security risk exists,

  • overlooking ISO 14001 where environmental impacts are present,

  • or defaulting to ISO 9001 without considering whether additional standards apply.


Selecting the wrong standard can result in rework or additional certification later.


3. Buying non-accredited certification

Under time pressure, some suppliers purchase ISO certificates without checking whether they are accredited.


Where Amazon specifies accredited certification:


  • non-accredited certificates may not be accepted,

  • suppliers may be asked to re-certify,

  • time and cost are effectively wasted.


Understanding the difference between accredited and non-accredited certification before starting is critical.


4. Treating ISO as a paperwork exercise

ISO certification is not about producing documents for an auditor. A common mistake is building systems that:


  • don’t reflect how the business actually operates,

  • exist only on paper,

  • or are ignored once certification is achieved.


This often leads to issues during audits and difficulties maintaining certification over time.


5. Over-scoping the management system

Over-scoping is one of the most damaging mistakes we see.


This includes:

  • certifying activities that don’t need to be included,

  • including multiple sites unnecessarily,

  • or applying controls that are disproportionate to the business.


A poorly defined scope increases audit time, cost, and complexity without adding value.


6. Rushing the certification timeline

Trying to compress certification into unrealistic timeframes often results in:


  • avoidable nonconformities,

  • delays between audit stages,

  • increased stress for staff,

  • and, in some cases, failed certification attempts.


A proportionate, structured approach is usually faster overall than trying to shortcut the process.


7. Confusing consultancy with certification

Some suppliers are unclear about the roles of:


  • ISO consultants, and

  • certification bodies.


Certification decisions must remain independent. Where these roles are blurred, impartiality and credibility can be compromised, and certificates may be questioned.


Taking a better approach

The most effective way to avoid these mistakes is to:


  • confirm whether certification is required,

  • identify the correct standard(s),

  • define a sensible scope,

  • implement systems aligned to real business processes,

  • and plan certification audits realistically.


This approach reduces risk, rework, and unnecessary cost.


Support for Amazon suppliers

We support Amazon sellers through the full ISO implementation process, helping them avoid common pitfalls and prepare for accredited certification, supporting the journey through the whole certification process.


Further details are available on our Amazon Supplier ISO Support page:



 
 
 

Comments


bottom of page