Workflow guide
Mapping a distributor's rep-to-order workflow: leads, samples, orders and reorders
Follow one account from sample to reorder. Name the owner, authoritative record and next action at each handoff, then use a worked fictional exception to test what happens when follow-up or order confirmation is missing.
Why "add a portal" undersells the problem
Map the work around your order system: account development, samples and repeat orders.
Test exceptions as well as ordinary orders. A missed follow-up, price request or stock change needs a next step. Check your existing tools first.
Use this worksheet to decide whether to build, extend your tools or keep the workflow as it stands.
One account. Every handoff.
Map your sample-to-order workflow
No email required. Entries stay in this page and are lost when you reload or leave. Print or save as PDF before closing. Do not enter personal member or customer records.
Choose “Load a fictional example,” then replace its assumptions. Print or save a PDF before closing; entries are lost on reload. The worksheet documents rules; it does not execute them.
The questions behind each handoff
Record the current answer, including “depends on the rep” or “nobody wrote it down.”
1. Lead: how a new account gets on the map
- Who records a new retailer or dealer today, and in what system, if any.
- What has to be true before a rep can start selling to it: a credit check, a territory assignment, a brand authorization.
- How stores or branches relate to a parent account.
2. Sample: what happens between "yes" and the first order
- How a sample gets requested, approved and shipped, and who does each step.
- Who is responsible for the follow-up, and by when. If the answer is "the rep remembers," write that down plainly.
- Where the review calendar or target reorder date is recorded.
3. Order: where pricing and inventory actually live
- Which system states list, contract, promotional and approved exception prices.
- What gets checked before an order is accepted: credit standing, live inventory, minimum order size.
- Whether totals and payment rules are enforced in one place, or calculated twice in two systems that can disagree.
4. Reorder: what a buyer can do without calling a rep
- Which order history, pricing and shipment details buyers can see themselves.
- What a rep still has to do by hand for a routine reorder that has no exceptions.
- Who approves backorders, price changes or split shipments, and how the order receives that decision.
Where the ERP boundary usually falls
Assume the ERP or order ledger owns inventory, accepted prices and invoicing. Identify which other systems may request changes.
| Usually stays in the ERP | Usually belongs in the CRM or portal |
|---|---|
| Inventory levels and availability | The relationship history: visits, samples, follow-ups |
| Standard pricing and invoicing | Account-specific exceptions and their approval trail |
| Purchase orders and shipment records | What the rep or buyer sees, and when they see it |
| Financial reconciliation | Territory and coverage: who owns which account |
Treat this as a starting point. The order system must accept an approved exception before release. Confirm boundaries with system owners. The distributor CRM evaluation guide turns them into demo questions.
Permissions and approvals
Record these before choosing a system:
- Which roles exist among your reps, order staff and finance team, in plain language, not as software permissions.
- Who can see or change a price, and who has to approve an exception before it reaches an order.
- Which records are restricted for a reason: a confidential contract price, a credit hold, a legal or compliance matter.
Name who may make each decision and how another person requests it.
A beLoved walkthrough with fictional records
David runs beLoved Health and built its distribution software. That work informs these questions. Synthetic demonstration: invented records. Harbor Market, staff and transactions are fictional; no real client is shown. No independent practitioner has reviewed this example. Its proposed rules still need implementation and testing.
Account and location
Harbor Market has two stores and a territory rep. Keep an account ID and distinct ship-to IDs that the order system can recognize.
Sample and the missed follow-up
A sample reaches the first store. In this proposed rule, the rep follows up five working days after delivery. A missed deadline routes to the sales manager for reassignment while preserving the original due date. This is a teaching rule, not verified beLoved automation.
Authorization before the order
Check permissions and payment standing. A requested discount stays pending until its authorized owner approves it. Keep the decision alongside the order.
Order history and the next order
Our 30 September 2026 source review of beLoved's wholesale order interface found account selection, payment restrictions and order history with calculated totals. That review did not exercise a customer's authenticated session. In this proposed workflow, a reorder rechecks current terms and availability; the prior order supplies history, not fresh authorization.
Worked exception: a sample has no order yet
The fictional sample was delivered to Harbor Market's first store. Its five-working-day follow-up is now overdue. No order exists. Delivery alone does not establish buyer acceptance or a sale. Keep the sample open with a named next action.
| Event in the fictional example | Owner and authoritative record | Next action and evidence to retain |
|---|---|---|
| Follow-up date passes with no response. | Sales manager; sample log S-104 linked to account H-10 and store H-10-A. | Assign a backup rep. Keep the original due date, reassignment time and reason visible. |
| Backup rep learns the buyer postponed the review. | Backup rep; sample log. | Set a new agreed follow-up date. Record the buyer's response source; keep “awaiting review” distinct from “declined.” |
| Buyer requests a first order with a price exception. | Sales operations; approval request A-22. Finance owns any credit hold. | Keep the order pending. Record requested terms, approving role and decision before submission. |
| Order is submitted but confirmation is missing. | Order desk; order system and submission reference Q-31. | Check whether Q-31 was accepted before retrying. Escalate an unresolved status to the system owner; do not create another order blindly. |
| Order system confirms order O-88. | Order desk; accepted order record. | Link O-88 to the account and sample history. Assign the rep's reorder-review action using current terms. |
Only the final row establishes an accepted order in this example. A link between sample and order records supports traceability; it does not prove the sample caused the purchase. Declines, missing responses and accepted orders need distinct dispositions if you want to review what happened later.
In the worksheet, put the overdue follow-up under Sample, the pending terms under Authorization, and the missing receipt under Order. Use the exception field for the owner, retained reference and recovery action. The printable map is a design record; these behaviors still need to be demonstrated in your chosen system.
What this example proves, and what it does not
The example assigns records and responsibilities. It does not establish measured improvements in rep time or order volume, or compatibility with your ERP. Demonstrate the relevant features against your own acceptance scenarios.
Common mistakes
- Buying a portal before mapping the pricing exceptions. A login screen does not resolve who is allowed to override a price.
- Assuming sample tracking is covered. Demonstrate delivery, follow-up, response and disposition in the system you use. The retail sample tracking worksheet helps define those records.
- Keeping account history only in a rep's inbox. Store the handoff and next owner where the authorized team can find them.
- Building reorder self-service before deciding who approves an exception. Include a changed price or unavailable item in the acceptance scenario.
- Treating a sent request as an accepted order. Reconcile the order system's result before retrying an uncertain submission.
Using this with us, or without us
Bring one unowned handoff, system names and a blank or sanitized map. We can work through it after a discovery call, and you keep the result. Keep customer records and confidential prices out of the initial inquiry.