Customer & Order Information
Select customer/outlet, route, salesperson, requested delivery date and order type.
End-to-end field-to-warehouse-to-delivery workflow for a modern beverage distribution system — from PJP outlet visit and pre-sales capture through stock allocation, delivery, POD, invoicing, collection and closure.
The salesperson captures the outlet order first. Warehouse fulfilment and physical delivery happen later, allowing the business to plan exact stock, route, vehicle, credit and delivery requirements before dispatch.
Visit the planned outlet and capture demand.
Products, pricing, promotion and credit are validated.
Allocate, pick, stage and load exact quantities.
Deliver, record actual quantities and capture proof.
Invoice, collect, update AR and close the order.
Each stage has a distinct business purpose, system status and control responsibility.
Select customer/outlet, route, salesperson, requested delivery date and order type.
Add SKUs, UOMs, quantities, pack sizes and customer-specific notes.
Check ATP, reservations, on-hold stock and possible shortages before pricing.
Apply effective price list, discounts, free goods, bundles and campaign rules.
Validate credit limit, aging, outstanding AR, payment method and payment term.
Review complete order and submit a controlled snapshot for approval.
Approve, reject or request changes based on commercial and credit authority rules.
Reserve approved stock by warehouse, batch and FEFO rule.
Consolidate route requirements by warehouse location and contributing orders.
Pick, scan, verify and stage goods by route, stop or order.
Load staged stock, verify quantity and sequence, confirm vehicle and driver.
Complete outbound checks, documents, route release and driver handover.
Deliver by stop, capture actual quantities, payment if required and exceptions.
Capture receiver, signature, time, GPS, photos and delivery condition.
Generate invoice, record cash/KPay/WavePay/bank/credit and update AR.
Verify delivery, POD, inventory, finance and accounting before final closure.
The order should move through controlled statuses rather than a single “open / closed” flag.
The system separates commercial, inventory, warehouse, delivery and financial responsibilities while maintaining one traceable order chain.
Captures customer demand, requested delivery and order lines.
Controls price, discount, exceptions and approval authority.
Maintains limits, aging, payment terms, AR and collections.
Allocates, picks, stages and verifies route stock.
Executes delivery, payment collection and POD.
Monitors status, resolves exceptions and closes orders.
One order should keep references to every operational and financial record created downstream.
Exceptions are part of real operations. eVolva should handle them explicitly instead of allowing users to bypass controls.
| Exception | Required Response |
|---|---|
| Insufficient stock | Reduce quantity, split delivery, later delivery or approved substitute. |
| Credit limit exceeded | Change to cash/COD, collect overdue balance or request override. |
| Promotion conflict | Apply approved priority/stacking rule or request supervisor review. |
| Pick / load variance | Recount, rescan, reallocate or approve partial delivery exception. |
| Customer unavailable | Record failed delivery, retain stock in transit and reschedule. |
| Customer rejects goods | Capture rejected quantity, reason, photo evidence and return disposition. |
| Payment not received | Do not mark paid; create AR or collection follow-up according to policy. |
| Missing POD | Keep delivery in exception status until required evidence is completed. |
Pre-sales creates a measurable conversion chain from planned field visit to cash collection.
Operational events should create controlled accounting events. Stock allocation itself is not revenue; revenue recognition and COGS should follow approved delivery/invoice policy.
Dr Accounts Receivable
Cr Sales Revenue
Cr Output TaxDr Cost of Goods Sold
Cr Finished Goods InventoryDr Cash / Bank / Mobile Money
Cr Accounts Receivable