Selling Wholesale Buying Wholesale
MapleSage
Wholesale

Your Quote Isn’t a Thread. That’s Why the PO Dies in Email.

Four tests every wholesale quote must pass — units, terms, revision history, and an approval gate — and why email, WhatsApp, and spreadsheet forks kill the PO before production sees it.

Parvind Dutta ·29 September 2026 ·4 min read

Wholesale desk — the quote as one commercial object

Wholesale desk — the quote as one commercial object

Heads of wholesale don’t lose seasons in the showroom. They lose them when the quote fragments across inboxes and the PO never matches what the buyer thought they approved.

This piece deepens one break in the commercial spine — showroom → account-aware line sheet → quote → size/assortment → approved PO. The flagship covers the full chain. Here we stay on the quote.


The break after the sheet

You fixed the sheet — or you think you did. Showroom went well. Buyer marked units. Then the “quote” becomes:

  • a reply-all with a spreadsheet attached
  • a portal line that doesn’t carry terms
  • a side WhatsApp: “can we do 2/10 net 30 on doors 4–7?”

Ops rekeys. Finance never saw the exception. Leadership asks why production is waiting. The PO that finally lands isn’t the deal anyone remembers.

Same failure mode as the line sheet problem: the artifact isn’t the system. A quote thread is not a quote. (Your Line Sheet Isn’t a System makes that case for the sheet; this one makes it for the commercial object that follows.)


Four tests every wholesale quote must pass

Not another CRM activity. Not a longer email. For each account and season, ask:

  1. Units tied to the live sheet — not a snapshot from Tuesday’s PDF. If availability or assortment changed since the room, the quote has to know.
  2. Terms on the same object — discounts, dating, freight, exclusivity notes. If terms live in a separate thread, finance will discover them late.
  3. Revision history that doesn’t fork — one quote, not Fall2026_Quote_FINAL_v3_REVISED2.xlsx. Three people with three files is archaeology, not control.
  4. A gate into PO — the order only becomes a PO when the right person approves. “Looks good” in email is not a gate.

If any of those four are missing, you’re negotiating folklore. Run the tests on last season’s largest account. Most mid-market desks fail at least two.

A familiar sequence: buyer marks units in the room; rep emails a sheet; buyer replies with a dating ask; ops builds a PO from the original attachment; finance invoices the dating that never made the PO. Nobody is wrong in their own inbox. The commercial object was never one object.


Why email, WhatsApp, and spreadsheets fail the same way

The tools aren’t evil. They’re the wrong container for a commercial object that must survive handoffs.

Email forks on every reply. Attachments diverge. The buyer’s “approved” sits three messages above a later change nobody re-confirmed.

WhatsApp is fast for exceptions and terrible for audit. A dating request that never reaches finance still becomes a production problem when the invoice doesn’t match.

Spreadsheets look like systems because they have rows. They aren’t. Version names grow. Formulas break. Nobody owns the canonical file when the buyer shifts two doors.

Together they produce the pattern every Head of Wholesale knows: the desk works harder as the season progresses, and the PO still doesn’t match the room.


Who this is for

Mid-market apparel, fashion, and luxury brands that sell to retailers:

  • Wholesale roughly $10M–$250M
  • 1–3 seasons in market
  • 5–50 serious doors
  • Already on a B2B portal, BigCommerce, or sheets + email

If you’re pure D2C with no wholesale book, this isn’t your post. If you need SAP-grade OMS on day one, talk to enterprise OMS — not us.


How MapleSage holds the quote

MapleSage is the showroom-to-shelf system for wholesale retail — line sheet to approved PO. The quote sits on the account-aware sheet, not in a parallel inbox.

  • Showroom and line sheet stay account-aware
  • Quote carries units, terms, and revision history as one object
  • Approval-gated PO closes the path — humans commit; the system doesn’t invent authority from a reply-all

See the buyer path live: b2b.maplesage.com. Product surface: Wholesale fashion solutions.

For the full spine — why the sheet must stay the system through showroom, quote, and size — read the flagship: The Wholesale Season Breaks When the Sheet Stops Being the System.


What we won’t pitch you

  • Another CRM “for wholesale”
  • Insurance / claims stacks
  • TikTok-to-checkout calendars for a wholesale book

Next step

If your “quote” is still a thread, fix the system of record for wholesale — not your posting cadence.

Talk wholesale: go.maplesage.net

Parvind Dutta

Founder of MapleSage. Twenty years in insurance technology — AIG, Prudential, MetLife, Duck Creek — now building the systems he used to sell.

Keep reading