Collection, delivery, tracking and POD

Use the permitted status controls when the real collection/delivery event has occurred, following the sequence offered by the platform. Status transitions can be restricted by the current state, assignment and proof requirements. Do not use a status change to conceal an exception.

Open the assigned active job and use the available tracking controls. Read and accept the applicable notice, grant the required device permission and check the tracking indicator. The reviewed Android service uses an ongoing notification during active tracking; stopping or ending the job must be handled correctly.

Check device location permission, location services, network connection and whether tracking is active for the assigned job. Read the app’s error indicator. A map or route preview is not proof that live location was successfully shared. Contact support if the issue persists during a job.

An authorised recipient with the provided tracking reference can use the public tracking route for the limited status information it exposes. Treat the reference as access information and share it only as intended. It is not permission to view account records or identity documents.

Follow the proof requirements shown for that job and the current platform configuration. Photo and signature can be required, and the form may offer further fields. Record accurate recipient/job information and upload only relevant proof. A delivery-status click alone may not complete the proof workflow.

Required proof fields are validated by the platform. If a photo, signature or another required element is unavailable, report the operational issue through support rather than uploading an unrelated file. Do not invent a recipient signature or reuse proof from another job.

Record the actual issue and use the available exception/support route. Follow the confirmed booking instructions and current policies for return, redelivery or storage. Do not assume an extra charge, disposal right or new delivery arrangement is automatically authorised.

Completed delivery does not itself create a bank payout. POD, earnings, finance reconciliation, release to the connected Stripe account and bank payout are separate steps. The new cash-out screen uses only funds already available in the carrier’s connected Stripe account; platform-to-carrier earnings transfers are not automated by this update.

Use Jobs or the relevant shipment/job detail screen in the account assigned to that job. Check the route, cargo, vehicle, schedule and current instructions. A notification or an offer alone is not a substitute for the live assigned-job record.

Check the assignment, vehicle suitability, collection location, goods description and site/handling instructions. Follow the current booking terms and report a mismatch, unsafe condition or access issue through the authorised operational process. Do not mark a stage complete before the underlying action has occurred.