An ecommerce quantity rules brief defines what one unit means, which quantities customers may buy and how those choices reach stock and packing records. A Kenyan store may sell individual pieces, sealed packs or measured goods. If the product page and warehouse interpret the same number differently, a correct-looking checkout can still produce the wrong order.
Discuss the sale unit with your ecommerce website developer in Kenya before importing the catalogue or adding minimum-order messages. Quantity controls should express the business's actual rules, and the server must enforce them through the entire purchase journey.
This guide focuses on quantity increments and sale-unit relationships. It is separate from assembling a bundle of different products. All numerical examples below are illustrative and do not prescribe prices or minimum quantities for your shop.
Define what the quantity field counts
Choose one representative product and finish this sentence: a quantity of one means the customer receives what? State the item, pack or measurement clearly. A photograph containing several pieces does not establish whether they are sold together or separately.
Use an illustrative sealed pack of six pens to expose the distinction. If the website sells packs, a basket quantity of two means two packs containing twelve pens. If it sells individual pens in multiples of six, the quantity field follows another model. Both can support the same physical supply, but their labels and records differ.
Record the chosen model in the approved catalogue. Sales, purchasing and fulfilment staff should be able to explain it consistently. Do not leave the developer to infer a unit from a supplier's filename or the first image in a shared folder.
Distinguish the sale unit from stock storage
Ask how the business counts inventory today. Stock may be recorded as individual pieces even when customers buy a sealed pack. The development scope needs an explicit conversion relationship where the sale unit and stock unit differ.
Review what happens when stock is adjusted manually or received from a supplier. Staff should know whether entering a number changes packs, pieces or another measure. A clear customer label cannot repair a backend adjustment performed in the wrong unit.
Use the product spreadsheet preparation guide to keep the identifiers and approved unit fields organised. The working catalogue and the eventual platform import file are different records; check that the intended unit survives the transformation between them.
Specify minimums, maximums and increments separately
A minimum quantity is not the same as a required multiple. An illustrative rule allowing any whole quantity from six upward differs from a rule allowing six, twelve or eighteen. Write examples of valid and invalid choices rather than relying on the phrase bulk quantities only.
WooCommerce's Min/Max Quantities documentation describes limits at several levels and purchases in predefined multiples. Treat it as one platform example. Ask the developer to show which rules your chosen setup supports and how product, variation, category and order-level constraints interact.
Identify the owner of each restriction and its reason. Packaging, fulfilment capacity and commercial conditions can create different rules. Keep approved limits separate from temporary availability so staff do not repeatedly rewrite a permanent minimum merely because current stock is low.
Decide how variants and mixed baskets interact
If a product has sizes or colours, specify whether the minimum applies to each variation or the combined product quantity. A customer buying several variants may reasonably interpret a general minimum in more than one way. Show the intended outcome with a mixed example.
Decide whether different products can contribute to an order-level threshold. If they can, explain the eligible group and whether each item still has its own increment. A basket can satisfy an overall minimum while containing an invalid quantity for one line.
Coordinate with the product bundle brief where a set contains components. Do not accidentally apply a component minimum twice or make the customer manipulate internal stock lines that are meant to belong to one fixed offer.
Write pricing labels around the actual unit
Record what the displayed price applies to. A price per pack and a price per piece should not be presented as the same offer. Have the commercial owner approve the actual amount and wording before the page is published.
If a comparison unit is shown for convenience, define how it is calculated and when it updates. Do not rely on a manually typed explanation that can become inconsistent after a price change. The developer should demonstrate the displayed amount and the saved order calculation using the agreed unit.
Keep quantity rules separate from discount rules. Buying a permitted larger quantity does not automatically imply a lower unit price. If a volume discount exists, specify it independently and review how it interacts with the coupon rules and other current offers.
Enforce the rule beyond the product page
Require the server to validate quantity, product identity, eligibility and current prices. A browser's plus and minus controls can make valid choices easier, but they cannot be the authority. Include a test where an invalid quantity is submitted without using the normal controls.
Recheck after basket changes and before payment preparation. Removing one product may invalidate an order-level minimum. Changing a variation may affect its permitted increment. The customer should receive a clear explanation and a chance to correct the basket rather than an unexplained payment failure.
Specify the handling of fractional quantities if measured goods are within scope. Decimal precision, rounding and fulfilment units need deliberate decisions. Do not assume a whole-number quantity component can safely represent every product simply because it is the store's default.
Make correction messages understandable
Prepare a message for each common invalid state. Explain the allowed next choice and the relevant unit. A customer entering three packs should not receive a message asking for six items when the system actually means six packs.
Review whether the store adjusts a number automatically or asks the shopper to confirm. An automatic change should never conceal a higher payable amount. Show the corrected quantity and total clearly before the customer proceeds with the purchase.
Check the phone layout and manual entry behaviour. Customers may type a value rather than use step buttons. Test clearing the field, entering a very large number and changing quantity quickly. The visible result should remain consistent with the server's approved rules and available stock.
Verify the packing record and handover
Show a representative sample order to the fulfilment team. Ask them to describe exactly what they would pick. The product reference, quantity, sale unit and any pack content should be understandable without reopening the original page or asking sales what the number means.
Review exports and connected systems as well as the storefront. If a downstream system expects pieces, document how pack quantities are represented. A correct screen does not prove that an export or inventory connector uses the same unit.
Test in a review environment with controlled accounts and supported payment testing. Cover valid boundaries, invalid increments, mixed variants, changing stock and repeated basket edits. Do not create fake live purchases or analytics events for these checks. Save the expected and actual outcomes with the operational handover.
Frequently asked questions
Is a pack the same as a product bundle?
Not necessarily. A pack may be one sale unit containing identical pieces. A bundle can combine different component products and needs its own relationship and stock rules.
Can a minimum apply across several colours?
That can be specified, subject to the implementation. Provide an example showing whether quantities combine across variations and ask the developer to demonstrate the result.
Should a quantity control round invalid values automatically?
Decide the intended behaviour and make any correction visible. The customer must understand the resulting quantity and payable amount before continuing.
What should accompany a development enquiry?
Send your sale-unit definitions, stock conversions, valid and invalid examples and packing expectations. Request an ecommerce quotation that includes server validation and downstream records as well as the quantity control.
