Let business buyers order through AI on their account terms.
A business buyer writes “same as last time” and gets an order they can approve: the right account, units, contract price and stock, with approval where your policy requires it.
“Same merino crews as last time.”
- Matched to
- ORD-8394, merino crew, case of 6
- Order
- 4 cases of 6 at $294 a case = $1,176
- Ships
- 3 cases now, 1 later
- Limit
- Self-approval to $1,000
- State
- Waiting for approval. The split doesn’t bypass it.
One reorder, ready for approval: the account, the units, the contract price and why it’s waiting.
Sound familiar?
- A retailer emails “same merino crews as last time”, and a rep rebuilds the order from memory and a spreadsheet.
- Case sizes, limits and approvals live in one rep’s head.
- Public shopping routes can’t see account catalogs, contract prices or credit.
A wrong unit, price or approval is a dispute with a customer who buys every month. A public assistant must never work out private terms from a public price.
What changes.
- Identity
- A name on an emailA verified buyer, account and ship-to
- The request
- Read by a repMatched to the last order, with case or unit confirmed
- Terms
- A retail price, or recalledThe contract price from the account system
- Approval
- Whoever noticesOver-limit orders wait for a person, split or not
How it works. 5 steps, 4 stages.
- AI1
- Rules and automation3
- Your team1
- Approval
1Verify
Rules and automation
Verify the buyer and account
Identity, account and ship-to come from your account system, never from the message.
- Shopify
- NetSuite
2Match
AI
Match the request to a prior order
Finds the last order and asks whether a number means cases or units when it isn’t clear.
- Outlook
3Price
Rules and automation
Price from the account
Contract price, case multiples, stock and credit status come from your ERP and commerce platform.
- NetSuite
- Shopify
4Approve
Your teamApproval
Approve over the limit
Orders over an account’s self-approval limit wait for your wholesale lead, even when they ship in parts.
Rules and automation
Place the order, or send a quote
Creates the order, or a quote that says what happens next.
Changed terms update the rules
What you get. Real work, every week.
- Alpine Supply4 cases · limit $1,000$1,176Needs approval
- Cascade Trading Co.2 cases · limit $1,000$588Placed
- Unknown senderNo matching account—Held
The queue your wholesale lead works from: each order with its account, its limit and its state.
- Switching accounts keeps private prices apart
- An expired contract is refused
- A number is confirmed as cases or units
- A credit hold stops the order
- Partial stock splits the shipment, not the approval
What we test before a buyer sees it: the cases a convenient message must still get right.
How you’ll know it’s working.
Elapsed time to a correct, executable order
From the buyer’s message to an order or quote that needs no rework.
Rep minutes per correct order
Freed capacity, counted honestly. It isn’t payroll savings unless spending falls.
Orders with a wrong unit, price or approval
Errors and returns, which decide whether buyers trust the route.
Baselines agreed before we build.
Works with what you have.
Commerce
- Shopify
- NetSuite
ERP, CRM & inbox
- Salesforce
- Outlook
- HubSpot
Wholesale commerce
- BigCommerce
- We configure first
- If you run Salesforce Commerce or Shopify B2B, their buyer-agent and company-account tools may already verify buyers and handle reorders, depending on your plan. We check and configure those first.
- We build when
- Your accounts span an ERP, a portal and a shared inbox that no single native agent covers.
What a first build includes.
Built in your accounts, around your team. Scope, fee and baseline agreed before we start.
- 1Design
- 2Build
- 3Run it, or hand it over
We build
- Buyer and account verification before anything else
- Reorder matching from emails and chat
- Pricing, units and stock from your account system
- An approval path for orders over the limit
We start from
- Account hierarchy, ship-tos and contract prices
- Order history and case sizes
- ERP, portal and inbox access
From your team
- Owner
- Head of wholesale, with finance
- Involves
- Wholesale
- Finance
- Operations
- IT
Questions teams ask.
Won’t our buyers keep using EDI or calling their rep?
Many will, and that’s fine. We start by replaying real reorder emails to see where reps lose time, and only build if buyers want a faster route.
Can an assistant see a customer’s contract price?
Only after the buyer is verified against their account, and only that account’s. It never works out private terms from a public price.
Who owns it once it’s running?
You do. It’s built in your accounts, documented, with training for the people who run it. Ownership usually sits with your head of wholesale, with finance. We can keep running it with you, or step back.
How do we start?
Usually with an AI shopping review: two to four weeks, a fixed fee credited to the build, and a plan that’s yours. If the job is already clear, we can scope the build directly.
Part of your AI shopping engine. One of 13 use cases, in 5 parts.
See the whole AI shopping engineIn buying on account
- B2B agent ordersYou’re here
Works with
See it at work
Let buyers reorder on their terms. Start with an AI shopping review.
We reply within one business day.