Ecommerce delivery in Kenya: quote fees, manage pickup and handle returns

Ask the fulfilment team to list routinely served locations, excluded areas, pickup points and items needing special handling. County alone may be too broad to determine an actual delivery cost. A Nairobi county address can still have different route, timing or access requirements. Choose the level of detail your business can maintain without confusing shoppers.

For an illustrative store, central Nairobi could have an approved local-delivery option while another town needs a courier quotation. The precise fee and promise must come from the business or courier agreement. Do not publish invented nationwide rates to make checkout appear complete. If a fee needs confirmation, state that clearly before the buyer commits to payment.

In WooCommerce, customers match a configured shipping zone and see its available methods. Zone order matters when areas overlap. This is a platform mechanism, not a complete Kenyan logistics policy. Your developer still needs the intended matching rules, fallback behaviour and how unusual addresses are clarified.

Test supported and unsupported addresses, pickup and special product combinations. An undefined destination should not silently receive free shipping. Avoid requiring a postal code when your actual delivery team uses a different address workflow unless the service needs it. Ask for a usable location description, contact number and landmark where operationally appropriate, collecting only what fulfilment requires.

Describe whether an estimate starts after payment, stock confirmation or dispatch. Explain weekends, preorder items, remote routes and bulky goods where relevant. If some items ship separately, decide whether the customer sees one charge or multiple charges and what happens when only part of the basket is available.

A checkout total should make product price, delivery and any other applicable approved charges understandable. Be explicit about pickup location and hours. If pickup stock differs from dispatch stock, do not offer collection simply because a product exists in the main warehouse. Link the rules to actual inventory and staff responsibilities.

Use these checks to compare proposals against your real workflow. Mark each requirement as included, optional or excluded, and record the person responsible.

An order can be paid and still waiting for stock or packing. A dispatched parcel is not necessarily delivered. Use distinct states and a staff checklist so customer messages reflect the actual event. If tracking is manual, identify the person entering reference numbers and explain what the customer can see.

Handle payment confirmation through the agreed gateway and server workflow, rather than assuming a screenshot is final proof. See our M-Pesa explanation for the basic distinction. Limit order detail access to authorised staff and customers. Do not send private addresses or payment information into public tracking pages.

Write customer-facing terms with the responsible business team and obtain suitable legal review where required. This guide covers implementation questions, not Kenyan consumer-law advice. Specify how a customer requests help, what evidence staff need, who approves a return and how updates are communicated. A policy copied from another store might not match your products or obligations.

Returned stock may need inspection before becoming sellable. Record the reason, item condition, stock outcome and any separately approved refund or replacement. Give developers those steps and test them with a labelled scenario. Bring your current courier arrangements and basket examples to our ecommerce team, using the store cost guide to identify delivery work in the quote.