The card drawer was built for names. The book was never going to fit.
The season goes badly in a familiar way. Quotes arrive late, a big account’s delivery window slips without anyone noticing, and finance finds out about a dating exception after the goods ship. In the review, someone says the problem is visibility: leadership can’t see the book. The fix everyone agrees on is a better CRM.
Six months later the CRM is live. Every account has a record, every rep logs meetings, and the pipeline report looks clean. The book is still in spreadsheets. The quote is still a file attached to an opportunity. The size runs, the exclusivity notes, the delivery windows and the credit holds are still somewhere else, and the next season breaks in the same places.
Nothing was wrong with the CRM. It holds what it was built to hold. The wholesale book isn’t that.
This follow-up sits on the spine: showroom → account-aware line sheet → quote → size/assortment → approved PO → production. Day 7 argued for one season book. Day 14 said B2B portals don’t fix fragmented quotes. This one is about the tool brands reach for most often when the book breaks: a CRM tracks the relationship. The book is the commercial object. Buying another CRM moves the relationship and leaves the book where it was.
The misuse
For a Head of Wholesale, “the book” means something specific: which accounts are buying which styles, in which colourways and size runs, at what price and terms, for which doors and delivery windows, and how much of it is confirmed. It changes every day of the selling season, and every change has to reach the quote, the PO and production.
A CRM is built around a different shape:
- Contacts and accounts: who the buyer is, who her boss is, when you last spoke
- Activities: meetings, calls and emails, logged against the account
- Opportunities: a deal with a stage and a single value, moving left to right
- Reports: how many deals are in each stage, and what they add up to
So the book gets squeezed into that shape:
- The season becomes an opportunity: a buyer’s order, with forty styles and six doors, turns into one line called “Fall 26” with a dollar figure
- The quote becomes an attachment: the real lines live in a spreadsheet or PDF hanging off the record, and the CRM can’t read them
- Terms become a notes field: dating, MOQ exceptions and exclusivity are typed in free text where no quote or PO will ever check them
- Stages replace status: “Proposal sent” says nothing about which units are confirmed, which are on credit hold and which are waiting on availability
- Reps log twice: once in the CRM so management sees activity, once in the spreadsheet so the order actually happens
Each of these is a workaround. Together they mean the system leadership looks at isn’t the system the season runs on.
Relationship record vs commercial object
| Question | CRM holding the book | System built for the book |
|---|---|---|
| What is one account’s season? | One opportunity with a value and a stage | Every style, colourway, size run, door and delivery window the buyer chose |
| Where does the quote live? | As an attachment the CRM can’t read | On the same record, line for line, with its revisions |
| Where do terms live? | In a notes field nobody checks | On the quote, carried to the PO, checked before the cut |
| What does “confirmed” mean? | Someone moved the stage | The approved quote became the PO, unit for unit |
| What does management see? | Pipeline value by stage | Units, terms and windows by account, and what changed this week |
| How often does the rep re-enter it? | Twice, once for the CRM and once for the order | Once, because the order is the record |
The CRM model asks: how is the relationship going? The book model asks: what exactly has this account committed to, on what terms, and is it still true?
Both are fair questions. Only one of them ships product.
Why “another CRM” costs more than the licence
The CRM project itself is rarely the expensive part. What it leaves untouched is:
- The parallel-system cost. The spreadsheet book keeps running beside the CRM, so every change has to be made in two places, and the two drift apart within weeks.
- The false-confidence cost. Pipeline reports look precise, so leadership plans buys and production from stage values that don’t know a single size run or delivery window.
- The rep-time cost. Logging activity for the CRM and building orders in spreadsheets takes hours out of every selling week, in the weeks when reps have the least time.
- The terms cost. Dating, MOQ exceptions, exclusivity and credit holds stay in notes and heads, so they’re discovered late, at the cut or at invoice.
- The next-project cost. When the season breaks again, the CRM gets blamed, and the brand starts shopping for the next one. The book never moves.
Related: One Season Book Beats Five Spreadsheets. B2B Portals Don’t Fix Fragmented Quotes. Door Terms Belong on the Sheet, Not in a Side Slack. Delivery Windows Are Commercial Terms Too. From Selection to Quote Without Losing Units. Full spine: The Wholesale Season Breaks When the Sheet Stops Being the System.
What a system that holds the book looks like
You can keep the CRM for what it’s good at. The book needs its own home, built around the order rather than the conversation:
- The account’s season is a set of lines: styles, colourways, quantities, size runs, doors and delivery windows, not a single value in a pipeline stage
- The line sheet, the selection and the quote are one record: what the buyer saw, what she chose and what was offered stay connected, with every revision kept
- Terms sit on the lines they apply to: dating, MOQ exceptions, exclusivity and credit status are fields the quote and PO check, not notes someone has to remember
- The approved quote becomes the PO: the same lines carry forward to production, so “confirmed” means units, not a stage change
- Management reads the book directly: units, terms and windows by account, and what moved since last week, without a separate report built from a separate system
- The CRM can link to it: the relationship record points at the book instead of pretending to be it
When the book has its own system, the CRM gets simpler, because it no longer has to fake an order. When it doesn’t, every new CRM inherits the same spreadsheet.
ICP framing
For mid-market AFL brands selling to retailers (roughly $10M to $250M wholesale), where the book lives is an input to:
- how many systems a rep updates for one order
- how far leadership’s pipeline view is from the units actually confirmed
- how late terms like dating, exclusivity and credit holds are discovered
- how often the brand runs a systems project that doesn’t change the season
It isn’t an argument against CRMs, a CRM replacement or a reason to stop tracking relationships.
Heads of wholesale feel it when the CRM dashboard says the season is on track and the production team is still waiting for the spreadsheet.
Product proof note: the Retail-OS wholesale path
MapleSage Retail-OS holds the wholesale order as one object from the account’s line sheet through selection and quote revisions to the approved PO, with terms, size runs and delivery windows on the lines they belong to. It sits beside your CRM rather than inside it, so the relationship stays where it is and the book finally has a system of its own.
See the buyer path: b2b.maplesage.com. Wholesale surface: www.maplesage.com/retail/wholesale/. Talk: go.maplesage.net.
What we won’t pitch
- Ripping out the CRM your sales team already uses
- AI that writes the book for the rep
- CRM or spreadsheet screenshots as the hero
Next step
Pick three accounts from last season. For each one, open the CRM record and the spreadsheet or file the order was actually built in. Count the styles, size runs, terms and delivery windows that exist only in the spreadsheet, and the times a change was made in one and not the other. That gap is the part of the book your CRM was never going to hold.
