Kivora Operations Team · Reviewed by KVRA

Order fulfilment workflow for a South African online store

Updated 2026-07-16 · 4 min read

Quick answer

A simple fulfilment workflow moves an order through clear states: received, payment confirmed, stock reserved, picking, packed, handed to collection or delivery, delivered, and closed. Exceptions such as failed payment, unavailable stock, address changes, failed delivery, cancellation, or return should leave the normal queue and receive an owner and next action.

The purpose of order states is to tell the team what is true and what happens next. A long status list is not useful if two people interpret it differently. Start with a small normal path, then manage unusual cases separately.

The exact payment and delivery providers may differ. The operating control is the same: do not promise, pick, refund, or close work from an assumption when a provider or customer confirmation is still outstanding.

1. Receive and review the order

Capture a stable order reference, customer contact details, delivery or collection choice, order lines, quantities, prices, and the expected total. Check for obvious address, contact, product, and quantity problems before the order enters fulfilment.

  • Keep the original order reference visible in customer and internal messages.
  • Separate customer notes from verified fulfilment instructions.
  • Flag unusual quantities, incompatible combinations, or missing delivery details.

2. Confirm payment state

Treat received, pending, paid, failed, cancelled, and refunded as different states. Use the payment provider's verified result or the approved internal process; do not use a screenshot or customer message as the only confirmation when a system result is expected.

Keep the store's customer payment separate from the business's platform subscription or other operating charges. This makes reconciliation and customer support clearer.

  • Release paid orders to fulfilment.
  • Hold pending payments with a clear review time.
  • Close failed or cancelled payments without reducing real stock permanently.
  • Record refund state separately from return receipt and order closure.

3. Reserve stock and prepare picking

Reserve stock when the business's payment and cancellation rules say the order is ready. The picking view should show the product reference, product name, variant, quantity, and any handling note needed to supply the correct item.

If stock is unavailable, stop the normal path. Decide whether the customer will wait, accept a substitute, receive a partial fulfilment, or cancel. Record the customer's decision before changing the order.

  • Reduce the risk of selling the same limited stock twice.
  • Use a second check for similar variants or high-value items.
  • Record substitutions and partial fulfilment explicitly.

4. Pack and hand over

Packing confirms that the physical contents match the order. Use packaging that protects the item through the chosen delivery method, and include only the customer information needed for the hand-off.

Record who packed the order, when it was packed, and the collection or courier reference when one exists. The hand-off state should mean the parcel actually left the business or entered the agreed collection process.

  • Check item, variant, quantity, condition, and required inserts.
  • Confirm the delivery label against the order before sealing.
  • Send the customer a useful update with the next expected step.
  • Store proof of hand-off where the support team can find it.

5. Manage delivery exceptions

Do not leave a failed attempt, delayed parcel, damaged parcel, or address problem in the normal delivered queue. Assign the exception to a person, record the next contact or provider action, and give the customer a clear update when the expected timing changes.

Repeated exceptions are process signals. Review whether the cause is poor address capture, unclear delivery areas, weak packaging, late hand-off, stock mismatch, or a provider problem.

  • Use one exception list across delivery and customer support.
  • Keep provider evidence and customer communication linked to the order.
  • Escalate by age and customer impact, not only by who notices first.

6. Close, return, or refund

Close an order when the fulfilment result and any required customer or provider confirmation support it. A return request starts a separate controlled path: request received, eligibility reviewed, return method agreed, item received where required, condition checked, resolution approved, and refund or replacement completed.

Keep the return, refund, and stock decision visible as separate facts. A refund can be pending after an item is received, and a returned item should not be placed back into sellable stock without a condition check.

  • Record the reason without forcing a misleading category.
  • Confirm the approved resolution and responsible person.
  • Reconcile the payment result and the stock result.
  • Use the reason to improve product information, packing, or delivery rules.

How this guide was prepared

Prepared from the payment-state, order, fulfilment, delivery, return, and exception workflows Kivora implements and maintains. It is operational guidance, not a claim about customer performance or legal advice.

Official South African sources