Ecommerce and online orders

OSERP separates product/catalogue work, storefront presentation, and order fulfilment. A published-looking product card does not by itself prove that checkout, stock, payment, and posting are correctly configured.

Prepare the shop

Review stores, products, categories, storefront sections, menus, templates, checkout, and payment configuration in their respective screens. Ecommerce and storefront areas have separate permission families. Use the screen directory to find the exact page.

Check product identity, public descriptions, images, price/tax basis, stock eligibility, and delivery information. Keep confidential notes and employee/customer data out of public product content. Confirm the result in the actual storefront after publishing.

Follow an order

The existing order documentation explains an order as the operational record driving a sales document. Accounting comes through that related document and its configured posting stages. An order-status label alone does not prove that its accounting completed.

Review customer, payment method, courier where relevant, line quantities, and fulfilment state. Follow the configured stages through picking, dispatch, and delivery. For partial fulfilment, check which quantities were dispatched and which remain open.

Stage configuration

Administration's Order Stages configuration associates operational stages with posting behavior. The existing default narrative associates dispatch with goods-out/invoicing and delivered COD activity with collection. Your configured stage mapping is the authority for the actual workflow; do not assume all companies use identical stage names or timing.

A highlighted timeline message can expose a posting failure even when operational movement proceeded. Correct the underlying cause and use the supported retry path. Check for the original posting before repeating a general write operation.

Cash on delivery

Record whether collection is by the business's own driver or a courier. A courier collection can represent money still held by the carrier, rather than money already received in the company's bank. Retain courier identity and remittance references so reconciliation can connect collections to later payouts.

When a payout covers several orders, compare covered collections, actual cash received, fees, and remaining differences. Escalate unexplained short payments instead of silently treating them as settled.

Returns and cancellation requests

Use /ecommerce/returns to review customer requests. The existing workflow documentation distinguishes approve, decline, and hold. A request is not itself a refund. Inspect the original order, actual returned quantity, reason, and evidence before deciding.

Keep the customer-visible decision note factual. Verify physical stock return, credit-document result, and payment refund independently. Approving a return should not be assumed to prove an external payment provider completed a refund.

Operational checks

Review orders waiting at each stage, posting exceptions, unpaid/COD balances, unresolved return requests, and checkout/payment failures. Compare the same order references across operational and accounting views before reporting a discrepancy.