When Kuwait pickup must happen before the address

The job is a bag that has not left the kitchen. The rider already has the customer pin. Someone still argues that the order was “taken” when the food is still on the pass, or a stranger now has the drop address.

Teams ask for “driver tracking.” That is a map. This loop keeps the customer details closed until pickup is verified, then it opens the drop and stops.

What the automation actually does

It holds the stop in a picked-pending state. It asks for the kitchen code, barcode, or confirm the merchant already uses. It unlocks the customer address only after that check passes. It flags a skip instead of inventing a pickup.

Manzil is that gate: verify pickup, then cash when required, then the door. AI automation is the hold-and-unlock. We will not treat a thumbs-up in the restaurant chat as a scanned bag.

This is not a proof photo to close the drop. Close argues the door. Pickup argues the pass. It is also not reading an address off a parcel photo. That job checks where it should go. This job decides when the rider is allowed to see it.

When we leave the gate with a person

If the kitchen still hands bags to anyone in a branded jacket, software should not pretend a code exists. If two brands share a cloud kitchen and the code is on a WhatsApp image, write the code into the order first. If a manager can override every miss, log the override — do not hide it.

Kuwait drops often use Area/Block the map does not know. The customer pin is the argument after pickup, not a reason to skip the kitchen check.

Bring last week’s “picked up but still on the pass” tickets and the code or barcode you already print. Book thirty minutes or write hello@jamilglobal.com.