Wholesale ecommerce in Kenya: packs, bulk prices and repeat ordering

List whether each product sells as a pair, piece, carton, bale or mixed pack. State the number of units in a pack and how variations such as size or colour are selected. A retailer must be able to understand the payable total without multiplying figures mentally or asking your team to clarify every item.

Consider an illustrative shoe carton containing 12 pairs. If the catalogue displays a per-pair price, the cart must still calculate and explain the carton total. A price of KES 800 per pair would make that example carton KES 9,600 before any separately stated charges. These numbers illustrate arithmetic, not an actual supplier or Ken Designers price. Decide whether mixed sizes consume one pack or create separate stock items.

A minimum order value, minimum units and pack increment solve different problems. A store might require at least two cartons, but also allow only complete cartons. An order can meet the money threshold while still containing an invalid quantity. Give the developer examples of valid and invalid baskets, including returns and repeat orders.

Document whether the rule applies per product, category, buyer group or whole basket. Choose how the customer sees the explanation before checkout. Avoid a generic payment failure when the actual problem is an invalid pack size. A useful message tells the buyer which requirement is unmet and how to adjust the order.

Public wholesale prices can reduce repetitive questions; approved accounts can support negotiated price lists and restricted catalogues. Approval adds work: someone must review requests, assign prices and maintain access when staff change. Decide whether new customers can enquire before approval, and who is responsible for responding.

WooCommerce's wholesale extension documentation describes role-based pricing and minimum quantities for that particular product. It does not mean every WooCommerce installation includes those rules. Ask the developer whether the proposal uses an extension, custom logic or a separate portal, and how its licence, support and future migration are handled. Test the price shown to a guest, approved retailer and staff user.

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

An enquiry-based catalogue may be a sensible first phase when stock and delivery need manual confirmation. A transactional store suits orders the business can price, accept and fulfil consistently. Do not label a WhatsApp basket as a paid order or imply an M-Pesa integration is live before it is configured and tested.

Define when stock is reserved, when the reservation expires and whether your team can replace an unavailable variation. If stock is shared with a shop, use the POS and ecommerce integration guide to scope the update rules. Delivery quotations and credit arrangements should follow approved business terms rather than being invented by a developer.

Build a clean spreadsheet with stable product codes, selling units, pack quantities, prices, variation rules and images. Agree who maintains each field after launch. A large catalogue of inconsistent rows can cost more to clean than the storefront itself. Start with a representative category and validate it before importing everything.

Our Jinsoko portfolio page provides relevant wholesale context, not a claim that every project needs identical features. Use the ecommerce cost guide and send the ecommerce team a sample catalogue and five common order scenarios. Judge the result by correctly specified orders, response effort and suitable repeat buyers, not catalogue visits alone.