Every lever is set and checked. None of them moves until someone decides it should.
Every wholesale team is being asked the same question this year: where do agents fit? The board has read about AI. A vendor has demoed a chatbot that “answers buyer questions”. Someone has suggested an agent that “closes reorders automatically”. The Head of Wholesale is left holding two bad options: ignore it and fall behind, or let software start committing units, prices and delivery windows nobody approved.
There’s a better line, and it’s the one this series has been drawing for four weeks. The season runs on one commercial object: the account’s sheet, the selection, the quote, the terms and the PO, carried as one record. Agents should do the work of preparing that object. People should decide when it commits the business.
This follow-up sits on the spine: showroom → account-aware line sheet → quote → size/assortment → approved PO → production. Day 11 said the rep shouldn’t re-enter what the buyer already marked. Day 15 said “looks good” in email is not approval. Day 28 said a CRM won’t hold the book. This one says where agents go on that spine, and where they stop.
The misuse
Most of what gets sold as “AI for wholesale” lands in one of three wrong places:
- The chatbot on the portal: a buyer asks about availability and gets an answer that doesn’t know her account, her terms or the units already allocated to her
- The silent approver: an agent “auto-confirms” reorders or “optimises” a size run, and the change reaches the PO without anyone signing it
- The email summariser: an agent reads the thread and writes a nice recap, while the quote, the exceptions and the dating terms stay where they were, in the thread
Each one puts the agent outside the commercial object. The chatbot talks about the season without holding it. The summariser describes the season without changing it. The silent approver changes the season without anyone owning the change.
The result is predictable. Either the agent saves nobody any time, because the real work still happens in spreadsheets, or it saves time by skipping the one step that mattered: a person deciding to commit.
Prepare vs commit
| Step on the spine | What an agent can prepare | What a person commits |
|---|---|---|
| Account sheet | Pull the account’s history, doors, terms and open budget into the season’s sheet | Which styles and prices go in front of this buyer |
| Selection to quote | Carry every mark, colourway and size run from the room into the draft quote | When the quote is ready to send |
| Size and assortment | Apply the door’s size curve and depth rules, flag lines that break them | Any override of the curve for this account |
| Availability | Check each line against ATP and flag what’s short before the quote goes out | What to offer instead, and to whom |
| Terms and exceptions | Surface dating, MOQ exceptions, exclusivity and credit status on the lines they touch | Every exception, by name, with a reason |
| Quote to PO | Assemble the PO from the approved quote, unit for unit, and show what changed since the last revision | Approval of the PO and release to production |
The agent’s column is all assembly, checking and flagging. The person’s column is all decisions that cost money if they’re wrong. That’s the boundary.
Why the boundary has to be on the record
Saying “humans stay in the loop” is easy. Making it true needs three things the email-and-spreadsheet season doesn’t have:
- One object to prepare. An agent can’t carry the buyer’s marks into the quote if the marks are on a photo and the quote is a new file. Agents only help when the sheet, selection, quote and PO are the same record.
- A visible diff. The approver has to see what the agent prepared and what changed: lines added, sizes adjusted, availability flags, terms applied. “The agent built it” is not something anyone can sign off.
- A named commit. The quote is sent, the exception is granted and the PO is released by a person whose name sits on the record, at a moment the record keeps. Not by a stage change, not by a reply-all, not by default.
Without these, an agent is just a faster way to make the same mistakes. With them, it’s the rep’s best assistant and finance’s best early warning.
Related: The Rep Shouldn’t Re-enter What the Buyer Already Marked. Why “Looks Good” in Email Is Not Approval. MOQ Exceptions Need a Gate, Not a Handshake. Why Another CRM Won’t Hold Your Wholesale Book. Full spine: The Wholesale Season Breaks When the Sheet Stops Being the System.
What it costs to get the line wrong
Put the agent on the wrong side of the boundary and the cost shows up quickly:
- The overcommit cost. An agent that confirms reorders on its own commits units production can’t cut, or allocates stock another account was promised.
- The terms cost. An agent that “helpfully” applies last season’s dating or MOQ exception to a new order recreates the exception nobody approved this time.
- The trust cost. One wrong auto-confirmed size run and the reps stop trusting anything the agent touches. They go back to rebuilding quotes by hand, and the time saving is gone.
- The audit cost. When finance asks who approved the exception, “the system did” is not an answer. Neither is a recap email the agent wrote.
- The idle-agent cost. Keep the agent away from the object entirely and it can only chat or summarise. The rep still re-enters the selection, finance still finds dating late, and the season breaks in the same places.
What agents on the spine look like
- The agent works on the account’s sheet, not in a separate chat window: it knows the doors, terms, budget and history because they’re on the same record
- The buyer’s marks become the draft quote automatically: every style, colourway and size run, with nothing re-typed
- Size curves, depth rules and availability checks run before the quote goes out, with every flag visible on the line it belongs to
- Exceptions are surfaced, never granted: the agent shows the MOQ break, the dating request or the credit hold, and routes it to the person who owns it
- Every revision shows a diff: what the agent changed, what the rep changed, what the buyer asked for
- Approval is a named step: the quote is sent, the terms are accepted and the PO is released by a person, and the record keeps who and when
- The approved quote becomes the PO: same lines, same units, same terms, into production
The agent makes the object complete. The person makes it binding.
ICP framing
For mid-market AFL brands selling to retailers (roughly $10M to $250M wholesale), where agents sit on the spine affects:
- how much rep time goes into re-entering, checking and chasing instead of selling
- how early size, availability and terms problems are caught: before the quote, or at the cut
- who can explain any unit, price or exception on the PO, and when it was approved
- whether leadership’s “AI plan” changes the season or just adds another tool
It isn’t an argument for autonomous ordering, replacing reps or putting a bot in front of buyers.
Heads of wholesale feel it when the agent demo looks great and nobody can say who would approve what it just did.
Product proof note: the Retail-OS wholesale path
MapleSage Retail-OS uses agents to prepare the wholesale order as one object: building the account’s sheet, carrying the buyer’s selection into the quote, applying size and availability checks, and surfacing terms and exceptions on the lines they touch. Sending the quote, granting exceptions and releasing the PO stay with named people, with every revision and approval kept on the record.
See the buyer path: b2b.maplesage.com. Wholesale surface: www.maplesage.com/retail/wholesale/. Talk: go.maplesage.net.
What we won’t pitch
- Agents that approve quotes, terms or POs on their own
- A chatbot as the wholesale strategy
- Robot mascots or product screenshots as the hero
Next step
Take last season’s ten largest orders. For each one, list the work that happened between the appointment and the PO: re-entering the selection, applying size runs, checking availability, finding terms. Mark each item as preparation or decision. The preparation column is where agents belong. The decision column is what your team should still sign, by name, on the record.
