---
title: "Supplier pipeline stages for Amazon wholesale"
description: "An Amazon wholesale supplier pipeline needs six states: prospect, contacted, applied, approved, active and rejected, each with one observable entry criterion."
question: "What stages should my supplier pipeline have?"
cluster: crm-for-sellers
published: 2026-08-08
updated: 2026-08-08
tags: [pipeline, supplier-management, account-status]
related: [get-approved-for-wholesale-account, onboard-a-new-wholesale-supplier, evaluate-wholesale-opportunity, structure-supplier-contact-data]
---

A supplier pipeline for Amazon wholesale needs six states — prospect, contacted, applied, approved, active and rejected — and each state needs exactly one entry criterion that is an observable event.

A supplier pipeline is not a sales pipeline with the labels changed. A sales pipeline ends when a deal closes; a supplier pipeline's most valuable state is the one that never ends.

## The six states and what puts a supplier in each

Six states cover the whole relationship, and each is entered by a specific event, not a feeling about how things are going. The stall clock is a policy you set, not a benchmark; the numbers below are a starting point for a small team.

**Table: Six supplier account states, entry criteria and stall clocks**

| State | Entry criterion (observable event) | What moves it forward | Stall clock |
|---|---|---|---|
| Prospect | Brand clears your buy criteria, no outreach sent | Find a named buyer or application route | 14 days |
| Contacted | A first email or call sent | Get a reply or escalate to a second channel | 21 days |
| Applied | An application or credit sheet submitted | Chase a decision by phone, not by email | 30 days |
| Approved | Written confirmation of an account, plus a price list | Place and receive a first order | 30 days |
| Active | A purchase order received and paid | Reorder before FBA cover runs out | Per-SKU reorder point |
| Rejected | An explicit no, or a ban on third-party Amazon sales | Record the reason, set a re-entry date | Review at 6 to 12 months |

Six is close to the practical maximum. Every extra stage adds a judgment call about where a supplier belongs, and judgment calls make a shared board unusable for two people.

## Entry criteria have to be events, not intentions

An entry criterion is a thing that happened on a date, which is what makes a pipeline survive being shared. "Warm", "interested" and "in discussion" are intentions, and two people will sort the same supplier differently every time. "Application submitted on 12 June" is an event, and it sorts identically for everyone.

The test to apply: could an assistant who has never spoken to this brand read the record and say which state it belongs in? If not, the criterion is an intention. This rule also fixes the most common pipeline bug, the supplier stuck in contacted for four months because someone once left a voicemail. Under an event rule, a voicemail with no reply and no follow-up is a stalled contacted, and the clock says so. [How to structure supplier contact data](/docs/structure-supplier-contact-data) covers where those events get recorded.

## Why a supplier pipeline is not a sales pipeline

The two pipelines differ in their terminal state, and everything else follows from that. In a sales pipeline the last stage is closed-won: the deal is archived and the record leaves the working view. Every deal object across the CRM and prospecting tools reviewed on 2026-08-03 assumes you are the seller and the counterparty is the buyer, which is the wrong direction for wholesale.

In a supplier pipeline the last stage, active, is the one that needs permanent attention — reorders, price changes, stock coverage, the buyer relationship. The metric is not conversion to close. It is the share of approved accounts that reorder, and the interval between reorders. A board built for closing shows a healthy conversion rate while every account it converted sits idle.

## Stall clocks, and why the approved clock matters most

Every stage needs a deadline and an owner, or the board becomes a list of things somebody once did. The rule: the clock resets on an outbound action you control, not an inbound response you are hoping for. Waiting is not an action, and a supplier who has not replied in three weeks is a stalled record, not a pending one.

The approved clock is worth enforcing hardest, because approved looks like a win and produces no revenue. An approval that never converts to a first order leaves no purchase history and no reason for the buyer who granted it to remember you. Set the entry criterion for active as a received purchase order rather than an approval email, and the board stops flattering you. [What to do after a wholesale account gets approved](/docs/onboard-a-new-wholesale-supplier) covers that 30-day window.

## What should never become a stage

Four things get promoted to stages and should not be: sample requested, waiting on a resale certificate, negotiating MOQ, and researching. Each is a task with a due date or a field on the organization, not a position in the relationship. The test is exclusivity — if a supplier can honestly sit in two of your stages at once, at least one of them is not a stage.

Minimum order quantity is the clearest case. A supplier negotiating a MOQ is in applied or approved, and the MOQ itself is a number on the account that outlives the negotiation, as covered in [how to negotiate MOQs with wholesale suppliers](/docs/supplier-moq-negotiation). Rejected needs its own rule: a rejected supplier gets a reason and a re-entry date, not deletion.

## Controlling what enters the pipeline at all

A pipeline is only as useful as its entry gate, and most supplier boards fail by being too easy to enter. A prospect that would not survive the first margin check consumes the same board space, stall clock and attention as a real one, and forty of them make the board unreadable.

Forge Command gates entry with the same hard filters it uses for sourcing: at least 10% net ROI after Amazon fees, at least $1,000 a month of ASIN revenue, and — for opening a new account — at least three ASINs on that brand at 10% ROI or better, because a one-SKU brand is not worth the application effort. Multipack listings and generic or empty brands are excluded before anything surfaces. Forge Command also grades company maturity as SMALL/PROMISING, NEWLY EMERGING, LARGE/CHALLENGING or UNKNOWN, since [smaller brands approve wholesale accounts more often](/docs/company-size-predicts-approval). The supplier's standing then lives on the organization record as its account status.

## Frequently asked questions

### How many stages should a supplier pipeline have

Six. Prospect, contacted, applied, approved, active and rejected cover the whole relationship, and each is entered by an event anyone can verify. Stages for samples, documents or negotiations create records belonging in two places at once.

### What is the entry criterion for the active stage

A received and paid purchase order. Not an approval email, not a price list, not a verbal yes. Using the order as the criterion exposes approved accounts that never became revenue, the most expensive gap in a wholesale pipeline.

### Should a rejected supplier be deleted

No. Keep the record with the rejection reason and a re-entry date. A no caused by missing trade references is worth revisiting once you have three, and a brand that forbids third-party Amazon sales should stay visible so nobody rediscovers it.

### Can a supplier move backwards through the stages

Yes, and the board has to allow it. An active account whose supplier discontinues your SKUs drops back to approved, and one that later enforces a no-Amazon policy moves to rejected. A pipeline that only moves one way is a sales pipeline wearing supplier labels.