When a Kuwait delivery wallet should block the order

The job is a fee that already has a number. The kitchen is ready. The rider is online. The merchant wallet is short, and someone still creates the order in chat and chases payment after the bag has left.

Teams ask for “a delivery app.” That is a product. This loop will not release the order until the prepaid balance covers the fee, then it pings for a top-up and stops.

What the automation actually does

It reads the merchant wallet and the fee on that order. It blocks create or dispatch when the balance is short. It sends one top-up note with the amount due. It writes the deduction only after a successful pay.

Manzil is that ledger: prepaid KWD, MyFatoorah top-up, then a fee deduction before the shift owns the stop. AI automation is the block-and-ping. We will not treat a WhatsApp “we will settle tonight” as a funded order.

This is not auto-dispatch with a timeout. Dispatch hands the order to a rider. The wallet decides whether there is an order to hand. It is also not a proof photo to close. Close is the door. This job is the till.

When we leave the block with a person

If ops still ships house accounts with a verbal IOU, software should not invent a rule they will override on Friday. If two branches share one wallet and one does not, name the account before you block. If the useful balance lives in a spreadsheet next to MyFatoorah, pick one source of record.

Kuwait fees are in KWD. Do not convert a guest AED total and hope the deduction lands.

Bring last week’s unpaid delivery fees and the wallet export that should have stopped them. Book thirty minutes or write hello@jamilglobal.com.