A customer’s successful payment does not automatically mean the supplier has been paid. If your supplier uses a prepaid wallet, orders can stop before fulfilment when its usable balance is too low. First confirm the supplier’s payment status, then fund the authorised account and resume only the orders that still need payment.
The immediate problem is not necessarily stock or shipping. There may be enough inventory and a valid delivery address, while the supplier is waiting for money that has not yet reached its order system.
- Keep customer payment, supplier payment and dispatch as separate states.
- Check available balance, pending top-ups and the cost of unpaid orders.
- Do not submit the same order again merely because payment is delayed.
- Use a funding alert before the balance reaches zero.
Why can an order say “paid” in the store but remain unpaid with the supplier?
The customer pays your store through a payment provider. Your business then pays the supplier under its own payment arrangement. A store payment, a payout to your bank and a wallet top-up are three different movements of money.
CJdropshipping, for example, supports supplier-order payments and a CJ Wallet. Its help materials distinguish wallet balance from other payment methods. The exact options depend on the supplier, so do not assume a connected store gives permission to charge every order automatically.
Check which operation failed. Did the store order import successfully? Was a supplier order created? Did payment fail? Is payment processing? Has the supplier already accepted it? Each answer requires a different next step.
If the money has not reached your business because of a processor restriction, investigate Shopify Payments payout holds after scaling separately. A delayed payout can explain the funding gap, but it does not change what the supplier currently sees.
What should you do when the wallet alert appears?
- Open the supplier account directly through your usual trusted route.
- Check the currency, available balance and pending transactions.
- List affected order IDs with their current supplier payment states.
- Confirm whether an automatic funding attempt is already in progress.
- Use the supplier’s authorised payment method if additional funding is needed.
- Wait for confirmed usable funds before resuming payment attempts.
Do not follow replacement bank details from an unexpected email without verification. A funding interruption is exactly the moment when rushed account changes are easy to overlook.
If some payments are uncertain, keep them in a review queue. Paying again before resolving the first attempt can create a duplicate charge or order. A useful queue should distinguish unpaid, payment pending, paid and payment failed, rather than grouping them all as “not shipped”.
How can you calculate a practical replenishment alert?
Base the alert on supplier costs, not your retail revenue. A planning model is:
Funding target = unpaid committed supplier costs + expected new supplier costs during replenishment lead time + a contingency allowance.
This is an operating calculation, not a required deposit or a forecast guarantee. Use observed order costs and the actual time it takes for your payment method to become usable.
| Illustrative input | Amount |
|---|---|
| Unpaid accepted orders | $420 |
| Expected new orders while funding clears | 30 orders |
| Average supplier cost including shipping | $18 per order |
| Contingency allowance | $140 |
| Total funding target | $420 + $540 + $140 = $1,100 |
| Currently usable wallet balance | $300 |
| Additional funds needed to reach that target | $800 |
Do not subtract a pending top-up as though it were already available. Record it separately to avoid both underfunding and accidental double funding. If demand changes sharply, recalculate rather than relying on last month’s average.
Which controls prevent the same interruption next week?
Assign one person responsibility for funding exceptions and another way to cover absence. An alert with no owner is only a notification.
Use both a low-balance alert and an order-age alert. A wallet may appear adequately funded while a particular order remains stuck because its payment failed for another reason. A fulfilment exception queue for ageing orders catches that second problem.
Set limits on automatic replenishment where the supplier supports them. Consider maximum top-up size, frequency and who can change payment details. Keeping large sums prepaid with a supplier also creates exposure to that supplier, so an unlimited balance is not the only way to prevent interruptions.
How do you restart fulfilment without creating duplicates?
Resume from the supplier’s current order record. Confirm the existing supplier order ID, check whether it has already been paid, and retry only the failed step. Do not re-import the entire day’s orders as a shortcut.
If your integration retries automatically, ensure it recognises an existing order and checks its state before creating another. The principles behind preventing duplicate supplier orders after webhook retries apply here too.
After recovery, reconcile three totals: orders awaiting supplier payment, successful supplier payments and accepted orders awaiting dispatch. A zero wallet-error count is not enough if several customers are still missing from the fulfilment queue.
What should the customer be told?
Check whether the interruption changes the delivery promise. If it does, send a factual update with the order’s status and the options actually available. Do not mark an unpaid supplier order as dispatched or create a tracking number to make the delay look resolved.
You do not need to describe an internal wallet balance to explain that dispatch is delayed. The customer needs accurate expectations and a clear route to assistance.
Frequently asked questions
Does topping up automatically release every order?
Not necessarily. That depends on the supplier’s workflow. Check whether failed payments retry automatically or require a manual action on existing orders.
Should I stop advertising when the wallet is low?
Assess whether you can fund and fulfil additional demand within the promised schedule. If you cannot, limit further sales while resolving the backlog rather than allowing it to grow unchecked.
Can I use retail sales revenue as the alert threshold?
Supplier costs are the more direct input. Product cost, shipping and supplier charges determine what must be paid to release orders.
What if the top-up succeeded but orders remain blocked?
Check whether the funds are usable in the correct account and currency, then inspect each order’s payment error. Escalate with transaction references rather than repeatedly submitting payments.
admin
Author of practical guides to dropshipping, ecommerce, automation, and growing an online business.