KENYA · GUIDE 0582 · EDITION 4.7
Restaurant ordering site setup in Kenya: Delivery Planning and Acceptance Checks
Editorial update: 28 October 2026 · Business planning reference · Review scope
Plan delivery around observable acceptance
Plan the handover and acceptance record for restaurant ordering site setup, using the specific checkpoints for the example offer.
This is a planning reference for restaurant ordering site setup. The order below is an invented teaching case. It is not a completed customer job, an operating approval or a prediction of demand or earnings.
The example offer and its boundary
Fictional ordering-site ORD-82 adds twelve café menu items to an existing WooCommerce staging site for collection-only requests. The customer chooses items, collection window and contact; the café confirms acceptance and pays/collects through its approved offline process. Fixture orderT01 contains two teas and one bean plate with clearly fictional test prices. Output is a menu master, staging order flow, staff acceptance script and owner-controlled handover. Delivery zones, card payments, allergen advice, automatic kitchen availability and guaranteed fulfilment are excluded.
This page is a work-control sheet. It does not teach a qualified trade, prescribe a food process, approve equipment or replace the appropriate technical procedure. Confirm who has the competence and authority for any specialist task.
Prepare the control record
| Stage to schedule | Checkpoint from the scoped example | Actual record to complete |
|---|---|---|
| Define order meaning | Success wording must not promise food is accepted when staff still need to check availability. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Configure staged menu | No live customer address/payment is collected unnecessarily; tax decisions remain with merchant/adviser. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Control side effects | Test orders are not assumed distinguishable from live orders by every extension. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Run four fixtures | Kitchen/owner receives correct items and quantities; rejection does not show a false paid/fulfilled state. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
| Train and release | Owner can pause ordering and edit availability; publish only after authorised acceptance and a rollback plan. | Responsible person; evidence/reference; measured result; pass/hold decision; correction owner |
Keep accepted and unresolved work separate
| Issue to watch for | Evidence question |
|---|---|
| Kitchen gets fake test order | Check staging email/webhook destinations. |
| Customer sees paid before collection | Inspect offline payment/order-status mapping. |
| Unavailable item still orderable | Check item status/cache and staff update process. |
The issues above are prompts to investigate, not a diagnosis of a real defect. Record what was observed, isolate the affected output where appropriate, and refer the technical decision to the competent person or approved process. Do not copy a hypothetical response into a real incident without assessment.
Reconcile the handover
Use the agreed charging basis: ordering implementation. Record ordered, completed, accepted, held and rejected output separately. Track rework time, changed scope, credits and collection dates against the same order reference. Owner can pause ordering and edit availability; publish only after authorised acceptance and a rollback plan.
Proceed within a defined trial limit only after the buyer's acceptance, actual full costs and collections are recorded, and the guide's unresolved checks are addressed. The final business-specific checkpoint is: Owner can pause ordering and edit availability; publish only after authorised acceptance and a rollback plan. Otherwise record a hold, revision or stop decision in file 10.
References and their limits
Testing orders — WooCommerce
Test orders can trigger email/integrations and analytics; use staging and control side effects. Reference check recorded 2026-10-26.
Cash on Delivery — WooCommerce
COD order state is not proof of collected payment; merchant confirms settlement. Reference check recorded 2026-10-26.
WooCommerce Product Editor settings
Product identifiers and inventory fields; tax decisions remain with the merchant/adviser. Reference check recorded 2026-10-26.
Rights Of A Data Subject
Kenyan privacy principles and data minimisation; not a complete compliance assessment. Reference check recorded 2026-10-26.
Recorded references support only the scope stated beside them. They do not prove current supplier stock, a local quotation, actual buyer demand, operator competence or the feasibility of this particular business. Later editorial changes do not refresh earlier source-check dates.
Prepared by Business Starter Guides using AI-assisted drafting and desk editorial checks. Independent operator trials and specialist certification are not claimed. See the editorial method for the review scope.
Editorial method and evidence limits