Retail sales management means following a customer commitment through stock reservation, dispatch, customer acceptance and payment. An order is under control when the manager can see what was promised, what the customer has actually accepted, what money has been confirmed and who owns the remaining work.
Sales fulfills a customer’s order; purchasing obtains goods or services from a supplier. They share stock and demand information, but they are different workflows. An ERP connects these departmental records so that a salesperson’s promise can be checked against warehouse and accounting evidence.
Cover: a generated editorial illustration of retail order preparation and delivery handover. It is not a photograph of a customer deployment or a product screen.
Why “the order has shipped” does not close the sale
A store reports a sale, the warehouse reports a shipment and the delivery team is still waiting for customer confirmation. Accounting has received a deposit but cannot tell which order it belongs to. One green “complete” label hides several unfinished jobs.
Keep the confirmed order, stock reservation, dispatch records, customer acceptance evidence, invoices and payment allocations linked. Microsoft Learn’s quote, order and invoice overview describes these as successive commercial records. The operating review below adds an explicit customer-acceptance check rather than treating dispatch as proof of completion.
One order, two review points
Illustrative example, not customer results. A customer confirms ten units of one SKU at VND 2 million each, giving an order value of VND 20 million. The customer agrees to deliveries in batches, but all ten must be accepted by 17:00 on day 1, local time. A VND 6 million deposit has been confirmed and allocated to this order.
- Day 1, 17:00: eight units have been dispatched. The customer has accepted six, supported by verified delivery evidence. Two dispatched units remain in transit or without confirmed acceptance; two have not been dispatched. Confirmed receipts remain VND 6 million.
- Day 2, 11:00: the final two units have been dispatched, bringing cumulative dispatch to ten. The customer has accepted the remaining four, bringing cumulative acceptance to ten. An additional VND 8 million has been confirmed and allocated, bringing total receipts to VND 14 million.
The order quantity, price and original deadline stay fixed. VAT, fees, discounts, returns, refunds and order changes are outside this example. The figures describe fulfillment and collection; they do not determine revenue recognition or an overdue receivable.
| Measure | Day 1 | Day 2 |
|---|---|---|
| Accepted quantity | 60% | 100% |
| Dispatched, not accepted | 2 units | 0 units |
| Accepted on time | 60% | 60% |
| Confirmed collection | 30% | 70% |
Four measures that lead to different actions
1. Accepted quantity rate: how much of the promise has been fulfilled?
Formula: cumulative units accepted by the customer through the review point ÷ confirmed order quantity × 100. Unit: percent. Use the ten-unit order and verified acceptance records linked to its lines. Exclude reservations, picking records, dispatches and unconfirmed delivery claims from the numerator.
Day 1: 6 ÷ 10 × 100 = 60%. Day 2: 10 ÷ 10 × 100 = 100%. At the first review, four units remain unfulfilled: two dispatched but unconfirmed and two not dispatched. The delivery owner follows the former; the warehouse and salesperson resolve the latter.
The increase reflects four additional accepted units. Reducing the order from ten to six would change the scope instead. Review the customer-approved change and remaining need before calling that an improvement.
2. Dispatched but not accepted: which goods need delivery follow-up?
Formula: cumulative dispatched units minus cumulative customer-accepted units linked to those dispatches, at the same cutoff. Unit: units. Reconcile dispatch lines with acceptance lines, counting each quantity once. There are no returns or reversals in this example.
Day 1: 8 − 6 = 2 units. Day 2: 10 − 10 = 0 units. An unverified delivery message stays pending. Before assuming goods are still travelling, the delivery coordinator checks whether the issue is physical delivery, a missing signature or delayed document entry.
This measure excludes goods not yet dispatched. Day 1 therefore has two units in this follow-up queue and a separate two-unit warehouse backlog. Adding those distinct quantities explains the four-unit gap to the customer commitment.
3. On-time acceptance rate: did the original commitment hold?
Formula: units accepted by the customer by 17:00 on day 1 ÷ the ten units due by that deadline × 100. Unit: percent. Sources are the confirmed customer deadline and timestamped acceptance evidence. Goods accepted later do not enter the on-time numerator.
Both reviews remain 6 ÷ 10 × 100 = 60%. Current completion reaches 100% on day 2, while performance against the original deadline remains 60%. This is a quantity-based measure for one order, not an order-level on-time-in-full score or a chain-wide service result.
Record the acceptance event time separately from the time its evidence was verified. In this example, the remaining four units really are accepted on day 2. If late paperwork instead proves acceptance before the deadline, an authorized correction can change the result; retain the evidence, previous snapshot and correction history.
The sales lead checks reservation readiness, warehouse release, transport and the timing of customer confirmation before assigning responsibility. Retain the original promise alongside any approved revised date; changing the date retrospectively would hide the exception.
4. Confirmed collection rate: how much of the order value has arrived?
Formula: cumulative confirmed customer receipts allocated to this order ÷ the fixed VND 20 million order value × 100. Unit: percent. Sources are verified bank or cash receipts, the payment register and order-allocation detail. Exclude payment promises, transfer screenshots awaiting verification, money not yet assigned to this order and collections that an external courier has not yet remitted to the business.
Day 1: 6 ÷ 20 × 100 = 30%. Day 2: 14 ÷ 20 × 100 = 70%. The VND 14 million already includes the VND 6 million deposit plus the additional VND 8 million. Adding the deposit again would overstate receipts.
The difference from order value is VND 14 million on day 1 and VND 6 million on day 2. It is an amount to track against the agreement, not automatically overdue debt. Accounts receivable checks invoicing, payment terms, due dates and approved adjustments before deciding what to collect now. Applying payments to the correct transactions is a separate step, as Microsoft Learn’s settlement overview explains.
Make every handover carry evidence and an owner
- Sales and the authorized approver: confirm the SKU, unit, price, destination, deadline and payment terms. Resolve price exceptions or changed commitments before sending revised instructions.
- Warehouse: verify stock availability and existing reservations, reserve the right goods, then link each release to the order. A reservation is not a dispatch, and stock reserved for another order cannot support this promise.
- Delivery coordinator: retain dispatch references, quantities, recipient and acceptance evidence. Assign a next action and deadline to missing or disputed confirmations.
- Accounting and receivables: verify receipts, allocate them once, reconcile invoices and follow due amounts. A deposit, an invoice, a delivery and recognized revenue are separate facts.
- Finance: use confirmed collections and expected receipts in the cash forecast, keeping uncertain amounts visible. Forecasting money does not confirm its receipt.
If stock is short, check existing reservations and inbound commitments before requesting another purchase. Continue with the purchasing workflow. For recording and period-end reconciliation, use the accounting review.
Close delivery, collection and exceptions separately
Delivery is complete when accepted quantities and any customer-approved cancellation explain the full confirmed order, with no unresolved handover. Collection is complete when the amount due under the agreement has been settled or an authorized adjustment explains the balance, and the supporting records reconcile. At day 2, delivery is complete, but VND 6 million still needs tracking under the payment terms.
A later return needs its own reference to the original order, dispatch and accepted quantity. Sales or service records the reason; warehouse confirms the goods received and their condition; authorized staff approve the remedy. Accounting verifies any refund or account adjustment. Loyalty points and commission must be reviewed against the applicable policy, without assuming an automatic reversal. A customer request alone does not prove goods returned or money refunded.
Five questions for a sales ERP demonstration
Blackwind’s sales workflow and return controls provide a starting point. Test the actual handovers rather than assuming the four measures are ready-made dashboards:
- Can one order show ten promised, eight dispatched and six customer-accepted without being marked fully delivered?
- Can the two unconfirmed dispatch units be separated from the two units still at the warehouse?
- Can we open the records behind VND 14 million and prove the deposit was counted once?
- Does current completion remain separate from the original deadline result after a late delivery?
- Who approves a changed order or return, and which goods, payment, points and commission records must be checked?
Send Blackwind your sales requirements with the handover that currently breaks down, the roles involved and an anonymized example. The review should identify the source record, responsible person and condition that closes each outstanding job.
