Storefront customer manual

Workflow ID: ECOM-CUS-001
Approval: Approved baseline

Access

Anyone may browse an enabled public store. Checkout, order history, and payment-proof replacement require mobile OTP verification through the party identity. A customer may view only their own orders and private proofs.

Workflow

1. Open route store.index, select a product, and add the required quantity to the cart.
2. Review quantities at store.cart; unavailable or inactive products cannot be purchased.
3. At store.checkout, choose delivery or pickup, provide required contact/fulfilment fields, and verify mobile OTP.
4. Submit the order with the required prepaid payment proof.
5. Track review and fulfilment through store.orders.index.
6. If staff reject a proof, replace it from the order page and wait for another review.

Displayed prices are provisional until confirmation. Staff confirmation revalidates price, payment, serial requirements, and stock.

Errors and recovery

• Expired OTP: request a new code.
• Changed price or insufficient stock: review the updated order outcome; do not repeatedly submit.
• Rejected proof: upload a clear replacement against the same order.
• Never send payment proof through a public URL or another customer's order link.

Result and next step

Submitting creates a pending order and private proof without accounting or stock effects. Staff verification and confirmation create exactly one invoice, receipt, payment relation, and FIFO stock-out. Validate with EcommerceModuleTest and mobile storefront UAT.