What a general CRM misses for Amazon wholesale
A general CRM has no ASIN object, no Amazon fee model, no catalog row, no eligibility state and no reorder concept, which is what Amazon wholesale runs on.
Last reviewed 5 min readSupplyForge LLC
A general CRM is missing five primitives that Amazon wholesale runs on: an ASIN object, a fee model, a catalog row, an eligibility state, and a reorder concept. Every other symptom follows from those five.
The missing primitives are a data-model problem, not a feature gap, and a cheaper or newer CRM does not fix them. A review of ten general-purpose CRMs on 2026-08-03 found no supplier price-list ingestion and no Amazon SP-API integration in any, and nine prospecting platforms reviewed the same day had no product object.
The five missing primitives
Five primitives decide whether a CRM can answer the wholesale buyer's question: is this unit worth buying at this cost.
| Missing primitive | The question it answers | Nearest general-CRM substitute | Why the substitute fails |
|---|---|---|---|
| ASIN object | Which Amazon listing this line is | A text field | A blank cannot separate "not checked" from "checked and absent" |
| Fee model | What Amazon keeps from the sale | A formula field you maintain | Rates vary by category and size tier and change; the formula goes stale |
| Catalog row | What the supplier sells, at what cost, in what pack | A sell-side Products object | Built for quote lines, not a distributor price list |
| Eligibility state | Whether you may list the item | A picklist someone types | A typed value is a memory of a check, not the check |
| Reorder concept | What to buy again from an account that never closes | A deal that closes and archives | Closed-won hides the record when it starts mattering |
The pattern is structural, not one vendor's gap. Nine of the ten general CRMs reviewed on 2026-08-03 had no buy-side objects — no vendor, no purchase order, no supplier terms.
No fee model, so the CRM cannot tell you whether to buy
A general CRM cannot compute what Amazon keeps from a sale, and that single absence makes every other field decorative. An operator can put a referral percentage and an FBA fee into formula fields, but a CRM cannot keep them correct: referral rates differ by category, FBA fees are keyed to size tier and dimensional weight, and both change on Amazon's schedule.
The second problem is agreement between screens. Once fee math lives in a formula on a deal, a second copy appears on a report and a third in the purchase-order spreadsheet. Forge Command computes margin through one shared function, so the ROI on the wholesale tab, the products tab and a purchase order cannot disagree. Amazon FBA fees explained on a wholesale unit sets out what a fee model must contain.
No eligibility state, so the CRM cannot say what you may sell
Eligibility is a computed state, and a general CRM can only store a typed one. Whether a seller account can list an ASIN depends on brand gating, category approval, hazmat and other flags that live in Amazon's data and change without notice. In a general CRM that becomes a picklist: someone types "gated", and the field is now a record of what was true that day.
Forge Command derives one sellability status per catalog row from raw SP-API restriction fields rather than storing it, so it cannot drift. Four states exist: sellable, shown as Approved to Sell; approval_required, shown as Applied to Sell, gated but open to a request; restricted, shown as Restricted, a hard block covering firearms and FFL rows; and unknown, shown as Not Checked, when no ASIN has matched. How to check Amazon selling restrictions covers that check.
No reorder concept, because a deal is built to close
A general CRM's deal object is designed to end, and a supplier account is designed not to. Every deal object across the CRM and prospecting tools reviewed on 2026-08-03 assumes you are the seller, so the terminal state is closed-won and the record leaves the working view. In wholesale, a brand's approval is the moment the record starts needing weekly attention.
The reorder concept needs a standing link between an account, its price list and the ASINs you already sell, so the system can ask which approved-supplier SKUs you have never bought and which are running low. Forge Command models that as two of its four opportunity types — buy_new_sku and reorder — both filtered to at least 10% net ROI after Amazon fees and $1,000 a month of ASIN revenue. How to decide what to restock covers the decision.
No catalog row, and the Products object is the wrong shape
A CRM's Products object is a sell-side line-item list; a supplier catalog row is a buy-side cost record. A quote line needs a name, a price and a quantity. A wholesale catalog row needs supplier SKU, case pack, unit cost, cost breaks, MOQ, an effective date, a discontinued flag, and identifiers to match against Amazon. Volumes differ by orders of magnitude — Copper caps contacts at 2,500 on Basic and 15,000 on Professional (Copper pricing page, checked 2026-08-03), and one distributor list exceeds both.
Matching is a process, not a field. Forge Command matches on UPC, EAN, ISBN, GTIN, MPN or model number, brand plus title, and direct Amazon URLs, lets one wholesale row link to several ASINs, and enriches through SP-API in batches of 20 identifiers per request. Roughly 10 to 15% of a real catalog never matches, which is expected rather than a failure. See how to match a supplier catalog to Amazon ASINs.
What general CRMs genuinely do better
General CRMs beat Forge Command on several things that matter on day one. HubSpot's free tier runs at 2 users and 1,000 contacts at no cost (HubSpot pricing page, checked 2026-08-03), so evaluation is free, while Forge Command publishes no pricing and has no self-serve billing. Zoho CRM ships native Purchase Orders and Vendors modules from the Professional edition upward, which no other general CRM in the reviewed set does. Close has the deepest native calling stack, with a power dialer at Growth and a predictive dialer plus live call coaching at Scale (Close pricing page, checked 2026-08-03). Attio offers a genuine custom-object relational data model with a REST API and React App SDK. Forge Command is a small, young, wholesale-first product with no SOC 2, no formal SLA and no 24-hour support desk.
Frequently asked questions
Can I add custom objects to a general CRM to make it work
Yes, in the tools that support them — Salesforce and Attio both have real custom-object models. What you take on is ownership: the fee schedule, identifier matching, restriction checks and catalog refresh all become yours to maintain.
Does any general CRM connect to Amazon SP-API
No. None of the ten general-purpose CRMs reviewed on 2026-08-03 has a native Amazon SP-API or Seller Central integration, and none of the nine prospecting platforms reviewed the same day does either. Several publish REST APIs, so a connection is a build project.
Which general CRM comes closest for Amazon wholesale
Zoho CRM, the only one in the reviewed set with native buy-side objects — Purchase Orders and Vendors, Professional edition and above. It still has no supplier price-list ingestion and no margin math, so it cannot rank a catalog by profit.