Delivery — In-house & Geo-zones

What are the two kinds of delivery teams? Okommerce supports two kinds of delivery teams: in-house and external. How do admins draw geo-fenced delivery zones on a map? Admins define delivery zones on a map interface, drawing each zone as a polygon. How are delivery agents assigned to zones (one or many per zone)? Delivery agents (drivers) are assigned to zones, and the relationship is flexible — one driver can cover a zone, or many drivers can share a zone, and a driver can cover multiple zones. How are incoming orders automatically distributed to the covering zone? When an order is ready for delivery, the system matches its delivery address to the zone whose polygon covers it (using the bounding box for a fast first pass, then the polygon for precision)… How does assignment balance workload, working hours, and availability? Within a zone, assignment can be automatic or with a human touch, balancing factors like who has less work today, who is working more, and who is available. What does a driver profile hold that feeds assignment logic? A driver profile holds the data the assignment logic needs: working status (are they working today), working hours (until what time), their zone(s), their current workload (active… How does a delivery job auto-route to an available driver? A delivery job is created for a fulfilment, matched to its covering zone, and auto-routed to an available driver in that zone based on availability, working hours, and workload. How are real-time en-route status updates reflected to admin and customer? As the driver works a job in the PWA, their status updates — accepting the job, marking "On the way," delivering — are reflected in real time to the admin panel (and to customer tracking). How does a driver record comments, refund reasons, and issues? Through the delivery PWA a driver can add comments and record refund reasons or issues on a job — a note that the customer wasn't home, a reason for a refused or partial delivery, a problem… How is proof of delivery captured (photo, signature, both, or none) and enforced? At delivery the driver captures proof — a photo and/or a customer signature — and the requirement is configurable per case: signature required, photo required, both, or neither. What happens when proof is required but not captured? If proof is required but not captured, the system blocks the status from completing until the proof is provided (or an exception is explicitly logged).