Skip to content
Resources WhatsApp Sales Control

Paid is not delivered: keep WhatsApp orders moving after the sale

From the right item on the shelf to a clear collection update, give every step after payment a person responsible.

Original IGFirstERP editorial illustration.

A paid WhatsApp order still needs the right goods picked, checked and handed over. Payment is a milestone. The customer’s order is finished only when the agreed fulfilment has been completed and any unresolved issue has been addressed.

The familiar failure happens after a successful sale. Sales says the customer has paid. The warehouse is waiting for a clear item list. A driver arrives before the package is ready. The customer calls, and three people offer three different answers.

You can improve this without more group messages. Give the team one agreed order, clear preparation stages and a visible next action when something stops the work.

Give the picking team an order they can use

Before releasing work under your payment policy, confirm the product, quantity, selling unit, variation and supplying location. Include the agreed delivery or collection details. A product photograph alone may not distinguish a size, shade or pack quantity.

The picker should work from the agreed order, not reconstruct it from the salesperson’s memory. If the customer has accepted a change, update that agreement before preparation continues. Keep old requests from being mistaken for the final instructions.

In IGFirstERP’s configured WhatsApp process, payment review can release eligible work into picking and confirmation. The connected record helps the next person find the order and its current position. Staff still need to check the physical goods and complete their part of the work.

Pick the exact goods and record a problem when you find it

Compare the item on the shelf with the ordered product and variation. Count in the selling unit. Six pieces and six packs can look like the same quantity on a hurried note, but they are very different orders.

If an item cannot be found, is damaged or does not match, record the issue instead of quietly substituting another product. The responsible person can check another location, discuss an alternative or arrange a different fulfilment decision with the customer. Keep that decision with the order.

A short pick should remain visible until it has been resolved. Clearing the issue to keep the queue looking tidy leaves another colleague to discover it later, often after the customer has travelled to collect.

After payment, the work continues
Dispatch and customer receipt are separate events.

Check the package before it leaves

Confirmation is the point to compare prepared goods against the accepted order. Check items, quantities and variations before sealing or handing over the package. Include any documents or agreed extras relevant to that order.

If confirmation finds a mismatch, return the work for correction and record what needs attention. The purpose is to fix the goods while they are still in your care. It is better to hold a package briefly than send the wrong variation and arrange a costly second journey.

Keep the roles clear even when the same person does both tasks. Picking finds the goods; confirmation checks that the prepared order matches the agreement. During a busy period, a deliberate check can prevent “I assumed it was right” from becoming the customer’s problem.

A worked example: one unavailable variation

This is a fictional training order for two medium black bags and one small brown bag. Payment has been reviewed. During picking, the small brown bag cannot be found at the supplying location.

The picker records the shortage. Sales checks the options and contacts the customer. The customer might accept a different colour, wait for the original item or agree another appropriate resolution. The team records that decision before completing the package.

The confirmation check uses the revised, accepted order. It does not use the original product list and hope the customer remembers the discussion. If the customer has not agreed to an alternative, the remaining item stays unresolved.

An item is missing. Keep the decision visible.
Fictional training example, not a recorded customer outcome.

Dispatch should say what actually happened

Record the package leaving, the carrier or collection arrangement and the details needed for customer follow-up. Use the actual dispatch event, rather than marking goods dispatched because a driver has merely been requested.

For customer collection, distinguish “ready for collection” from “collected”. For carrier delivery, distinguish “handed to carrier” from “received by customer”. A transport-park handoff is another stage to track; it is not evidence that the customer collected the parcel at the destination.

Where IGFirstERP customer tracking is available for the order, keep the recorded fulfilment information accurate. A carrier name or expected arrival should be shared only when the relevant information has been entered and is suitable for customer display. Do not fill a gap with a guessed delivery time.

Keep the customer update useful

Customers need to know the current position and what happens next. “Your order is being prepared; we are checking one item and will update you this afternoon” is more useful than “processing” when a specific issue remains.

Choose a person to send the next update. Warehouse staff may be resolving the shortage while sales keeps the customer informed. That division works only when sales can see the issue and knows when to check back.

Avoid promising dispatch before preparation is confirmed. If a delay changes an earlier commitment, explain it and give the next realistic update. Silence makes a manageable problem feel like a lost order.

What to do when fulfilment goes wrong

Keep the issue connected to the order: wrong item, missing quantity, damaged package, failed collection or delivery problem. Record what has been reported, who is checking it and which decision is still needed.

Do not mark the matter resolved merely because someone replied. The resolution should say what happened next—corrected preparation, an agreed replacement, a revised collection arrangement or another authorised outcome. Customer acceptance matters when the original agreement changes.

For carrier problems, preserve the available dispatch information and follow the carrier’s process. For return or refund requests, involve the person authorised by the business. The customer should have one clear update while the team investigates; they should not be sent around several private numbers.

Review waiting orders by the next action

At the end of the shift, separate paid orders awaiting picking, picking issues, packages awaiting confirmation, ready collections and dispatched orders with unresolved follow-up. Each group requires a different action.

Ask what is holding up the oldest relevant work and who can resolve it. An unavailable item needs a stock or customer decision; an unconfirmed package needs a check; an uncollected order needs a collection update. Treating them all as “pending” hides those differences.

That review also shows recurring causes. Incorrect product descriptions, unclear units or missing collection details may be creating avoidable work every day. Repair those instructions at the sales stage rather than blaming the last person to touch the package.

Make the next shift’s job clear

Leave the actual stage, the unresolved issue and the next customer update with the colleague taking over. A package on a table is not a complete handover. The incoming person needs to know if it is awaiting a check, ready for collection or held because the agreed goods are incomplete.

You’re done when…

  • The physical items match the customer’s accepted order.
  • Shortages and substitutions have recorded decisions.
  • The package has been checked before handover.
  • Dispatch, ready-for-collection and completed fulfilment remain distinct.
  • Any waiting customer update has an owner and a next step.

Put this into your next working day

Explore fulfilment and customer tracking. For the practical next step, use the fulfilment usage guide.

Useful to someone on your team?Share on WhatsApp →