KENYA · GUIDE 0539 · EDITION 4.2
Online store product listing in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Prepare listings from verified SKU information, specifying product variants, image rights, stock status, delivery details, return-policy references, and who approves changes before products become visible online.
The operating sequence for this offer is:
- Obtain an approved source sheet covering products, variants, prices and delivery information, then confirm platform access and image-use permissions.
- Enter a small sample, check variant and stock behaviour with the owner and only then complete the agreed listing batch.
- Compare live listings with approved data, test display and enquiry paths and record errors or missing information rather than guessing.
Put acceptance into the job record
Variants, prices and delivery information match the actual offer.
Ask the merchant to place a test enquiry or order for similar variants, checking titles, images, options, quantities, and whether the selected item matches the actual inventory.
Inspect at the point where a correction is still possible, then again at handover. Record rejected or incomplete output separately from accepted output. A completed task is not automatically an accepted task, and an invoice does not establish that the customer received the right result.
Measure real capacity
Time preparation, the main operation, transport, cleaning, approvals and correction as applicable. The slowest stage determines how much you can promise. Where two orders need the same person, space or equipment at the same time, resolve the conflict before confirming both deadlines. An additional enquiry should not erase a commitment already made.
| Operating checkpoint | Evidence for this business |
|---|---|
| Before starting | Prepare listings from verified SKU information, specifying product variants, image rights, stock status, delivery details, return-policy references, and who approves changes before products become visible online. |
| During delivery | Enter a small sample, check variant and stock behaviour with the owner and only then complete the agreed listing batch. |
| At acceptance | Ask the merchant to place a test enquiry or order for similar variants, checking titles, images, options, quantities, and whether the selected item matches the actual inventory. |
| At the pilot review | Maintain SKU mappings, missing specifications, variant relationships, image sources, merchant approvals, test transaction results, listing corrections, and unresolved product questions that block accurate publication until verified. |
Keep a correction and escalation rule
When inputs, access, specifications or customer instructions change, pause the affected work and confirm the effect on time and cost. Do not quietly lower the acceptance standard to avoid a delayed delivery. Keep rework caused by your error distinct from a customer-requested change of scope and agree the remedy clearly.
A listing can attract clicks yet create costly returns when a generic photograph disguises a different pack size or variant selection sends the wrong item to fulfilment.
Retain the minimum records needed to investigate a complaint without disclosing unrelated personal information. Use measured delivery and actual acceptance as the basis for expanding capacity, rather than the maximum theoretical output of a tool or production line.
Operating control points for this exact offer
| Sequence | Work method | Release checkpoint |
|---|---|---|
| 1 | Record ten unique SKUs with dimensions, pages, material description, stock instruction and image ID. | Check whether '80 pages' means 40 leaves or 80 leaves in the merchant's specification and publish the correct wording. |
| 2 | Confirm access, product editor version and whether stock is tracked; ask merchant to identify the responsible tax/shipping administrator. | Do not change store-wide rules to make a single product appear purchasable. |
| 3 | Create NB01 as a simple physical product using approved fields and category. | Merchant validates display, currency, unit and image before the remaining nine are entered. |
| 4 | Enter the other nine from the master and inspect each product page for mismatched photo, duplicate SKU and missing price. | Do not select virtual for a shipped notebook merely to hide an unresolved shipping problem. |
| 5 | Publish only after approval and inspect ten public pages and one non-payment test cart. | Cart identifies the correct SKU/quantity; any live checkout test requires a separate authorised procedure. |
Do not substitute a tick for an observation: record the count, measurement, approved sample or evidence reference used at each checkpoint. Mark unresolved work as held and identify who can approve the recheck.
Diagnose a failure before repeating it
| Observed symptom to investigate | Check the cause | Proposed response |
|---|---|---|
| Product cannot be bought | Check price, stock status and the store's existing shipping rules. | Fix scoped data errors; refer store-wide configuration faults to its responsible administrator. |
| SKU rejected as duplicate | Search existing products and archived variants. | Ask merchant whether to update an existing item rather than inventing another code. |
| Page count disputed | Compare source specification and page/leaf wording. | Correct approved description consistently and flag affected listings. |
These are diagnostic prompts, not proof of the cause in a real incident. Separate suspect output, record any correction and repeat the relevant acceptance check. Link rejected units, rework time, replacement materials, customer credits and collection delays to the actual job result.