Operations
Automate approval for orders under $500 from accounts older than 90 days paying by card. Flag everything else for manual review until you have data on what breaks.
Most brands start by approving every wholesale order manually because they want control. They end up with a backlog of routine orders waiting for someone to click approve while high-risk orders sail through because the person reviewing is tired. A documented approval workflow fixes this by making the low-risk decisions automatic and surfacing the orders that actually need judgment.
Order approval risk comes from three inputs: order value, account age, and payment method. Each one changes the consequence of a bad approval.
Order value sets the dollar exposure. A $200 order from a new account is a small test. A $5,000 order is a cash flow event if the payment fails or the buyer disputes the charge after delivery.
Account age tells you whether the relationship has a track record. An account that placed three orders in the past six months and paid on time is lower risk than a brand-new account with no history. Age provides data on buyer behavior.
Payment method determines when you get paid and what recourse you have. Credit card payments clear before fulfillment. Net terms mean you ship first and collect later, which introduces credit risk. ACH sits in between: faster than a check, slower than a card, and harder to dispute than either.
These three factors combine to create a risk profile. A $300 order from a six-month-old account paying by card is low risk. A $4,000 order from a new account requesting net 30 is high risk. The workflow should treat them differently.
Start with payment method because it determines whether you have the money before you ship.
If the order is paid by credit card and the charge cleared, approve automatically for any account older than 90 days with an order value under $500. These orders carry almost no risk. The payment already happened, the account has a history, and the dollar amount is small enough that a dispute or return does not threaten cash flow.
If the order is paid by credit card but the value exceeds $500, flag it for manual review regardless of account age. The approval decision is about inventory allocation and whether you want to fulfill a large order before confirming the buyer's intent. Some buyers place large orders by mistake. A quick confirmation call or email prevents a costly return.
If the order requests net terms, check account age and order history first. For accounts older than six months with at least two prior orders that paid on time, approve automatically up to $1,000. For newer accounts or accounts with no payment history, run a credit check before approving any net terms order, regardless of size.
If the order is from a brand-new account (less than 30 days old), flag it for manual review regardless of payment method or order size. New accounts need a human decision until you have enough data to know whether they behave like your other buyers.
This decision tree is a starting point. Adjust the thresholds based on your average order value, your margin, and how much manual review capacity you have. A brand with $200 average orders and tight margins might set the auto-approve threshold at $300. A brand with $2,000 average orders and strong margins might set it at $1,500.
Most B2B commerce platforms and wholesale portals let you configure approval rules by account, payment method, and order value. The settings vary by platform, but the logic is the same.
In the payment settings, enable automatic approval for credit card orders under your threshold (for example, $500) from accounts older than your age cutoff (for example, 90 days). This rule should apply only to accounts in good standing, meaning no chargebacks, no disputed orders, and no outstanding balances.
In the account settings, tag accounts by risk tier. Low-risk accounts get higher auto-approve thresholds. High-risk accounts get manual review on every order. Risk tier is a judgment call based on payment history, order frequency, and any red flags like frequent returns or late payments. Most brands start with two tiers (trusted and everyone else) and add a third tier (restricted) only when they have accounts that need extra scrutiny.
In the net terms settings, set a credit limit for each account approved for net terms. Orders that exceed the credit limit trigger manual review even if the account is old and trusted. Credit limits prevent a single large order from creating unsustainable exposure. For example, if an account has a $2,000 credit limit and $800 in outstanding invoices, an order for $1,500 should be flagged because it would push the total exposure to $2,300.
In the notification settings, configure email or dashboard alerts for flagged orders. The alert should include the reason for the flag (new account, high value, credit limit exceeded) and a link to approve or decline. Alerts should go to the person responsible for order review, not to a general inbox where they get lost.
When an order is flagged for manual review, send an automated email to the internal reviewer with the order details and the reason for the flag. The email should include the buyer name, account age, order value, payment method, and any notes from prior orders.
For high-value orders from trusted accounts, the email should prompt a quick confirmation with the buyer before approval. The confirmation can be a two-line email: "We received your order for $3,200. Can you confirm this is correct and you are ready for us to fulfill it?" This step catches ordering mistakes and ensures the buyer is committed before you allocate inventory.
For new accounts requesting net terms, the email should prompt a credit check or a request for references. Do not approve net terms for a new account without some form of credit verification. The cost of a bad net terms approval is the full order value plus the cost of goods, and you have no payment to offset it.
For orders that exceed a credit limit, the email should show the current outstanding balance and the proposed new order value. The reviewer can then decide whether to approve the order, ask the buyer to pay down the balance first, or decline the order until the account is current.
This workflow is based on the approval logic GWO has seen work across consumer product brands using B2B commerce platforms. The thresholds (90 days, $500, $1,000) are examples. Adjust them to your business. The decision tree prioritizes payment method because it determines cash flow risk, then uses account age and order value to separate routine orders from outliers.
Some orders will not fit the decision tree cleanly. A trusted account might suddenly place an order ten times their normal size. A new account might have strong references but no credit history. A card payment might fail after the order is placed.
For outlier orders, the workflow should escalate to a person with authority to make exceptions. That person needs context: what is normal for this account, what is the margin on this order, what is the lead time to fulfill it, and what is the cost if the order goes bad. Document the decision and the reasoning so the next outlier has a precedent.
For failed payments, the workflow should pause fulfillment and send an automated email to the buyer asking them to update their payment method. Do not approve the order until the payment clears. If the buyer does not respond within 48 hours, cancel the order and notify them. Cancellation policies should be clear and applied consistently.
Review your approval workflow every quarter or whenever you see a pattern of bad approvals. If you are manually reviewing 80 percent of orders, your thresholds are too conservative. If you are seeing chargebacks or unpaid invoices from auto-approved orders, your thresholds are too loose.
Track two metrics: the percentage of orders that auto-approve and the percentage of auto-approved orders that result in a problem (chargeback, return, unpaid invoice, fulfillment error). If auto-approval is under 40 percent, raise your thresholds. If problem orders from auto-approval exceed 2 percent, lower your thresholds or add a new risk factor to the decision tree.
As your business grows, order frequency will increase and the manual review burden will become unsustainable. The approval workflow should scale with you by automating more decisions as you gather data on what low-risk looks like for your buyers.
Build the decision tree, configure the portal settings, and set up the email triggers. Start with conservative thresholds: 90 days, $500, card-only auto-approval. Track how many orders auto-approve and how many cause problems. Adjust the thresholds every quarter based on what you learn. The goal is to approve routine orders instantly and spend your review time on the orders that actually carry risk.
Tell us about your product and where you want to sell. We'll help you take the first step.