How Quiqup Handles the UAE Delivery That Misses the Door

Co-founder Bassel El Koussa built the Dubai-based logistics offer around the shopper’s experience. Quiqup’s public operating guides show what that means once the first delivery attempt fails.

A courier can leave a warehouse on time and still fail to deliver a parcel. The recipient may be at work, the address may lack the building name, or the order may have been cancelled while it was on the road. For the merchant, each case starts with a similar message from the shopper asking where the order is. The work of resolving it depends on whether the operator can tell those cases apart and give each one a next step.

Bassel El Koussa, Quiqup’s co-founder, described a gap in the UAE market in an interview published by Arageek. He saw independent merchants struggling to offer the delivery experience customers associated with larger platforms. Speed was one part of his answer. The other was to design around what the shopper sees after placing an order. In a separate published FWDstart interview, he described keeping the UAE last-mile operation as the place where Quiqup tests new features. He also explained that the company works with agencies that provide drivers while Quiqup designs their incentive scheme. The operational question is where Quiqup retains responsibility for the experience, even when more than one organisation takes part in delivering it. Arageek’s published interview with Bassel El Koussa, FWDstart’s interview with El Koussa

The promise starts before a courier is assigned

Quiqup offers delivery and fulfilment services to UAE merchants. Its public coverage guide distinguishes next-day, same-day and four-hour options and notes that coverage and collection depend on the service. A merchant needs to know which options apply to an address before showing a delivery promise at checkout. If a customer pays for a faster service and the address is outside its coverage, the first failure may already have happened before the parcel reaches a courier. Quiqup’s fulfilment service description, Quiqup’s delivery and coverage guide

A historical Careem UAE reel promoting Quik Electronics illustrates how a delivery promise can become part of the offer the customer sees.

That campaign came from a different operator. It makes a useful point about where the customer’s clock starts. A customer may count from the moment an order is confirmed. A warehouse may count from the moment the parcel is ready. A courier may count from collection. A merchant that wants to know whether the promise was met needs to keep those timestamps distinct. Otherwise, a logistics dashboard can show that the courier performed within its window while the customer still received the parcel later than expected.

The merchant also needs a plan for orders that cannot enter the normal flow. Quiqup’s public operating procedure describes checking address information for its four-hour service and holding a multi-parcel order if the number of packages received differs from the system record. Those examples show two different problems. One concerns whether the parcel can reach its destination. The other concerns whether the merchant has handed over the complete order. The action at the warehouse depends on which problem it sees. Quiqup’s published last-mile operating procedure

After the first miss, give the order a next step

Quiqup’s next-day and same-day workflow says that after a first failed attempt, the parcel goes back to the warehouse and can be sent out again if the address is correct and the customer has not requested cancellation. Office deliveries can depend on the next business day. After a second miss, the order can be put on hold while the operator contacts the customer or merchant and seeks a decision. A final attempt requires confirmation under the published workflow. If the process ends without delivery, the parcel is sent back to origin. Quiqup’s next-day and same-day workflow

The operator’s public guides give different timings for parts of the follow-up after a second miss. One describes a 72-hour window for the client to confirm a third attempt. The general procedure describes a customer contact step followed by a separate client response window. There are also different instructions for four-hour deliveries. The records establish the sequence of return, hold, contact and decision. A merchant needs the procedure and timing that apply to the particular service before telling a customer exactly when the next attempt or return will happen.

Those steps are more useful if the system preserves the reason for the miss. An incomplete address can call for an update to the delivery details. A recipient who cannot take the parcel today may need to select a later time. A cancellation needs to reach the people who would otherwise send the parcel out again. Treating all three cases as identical creates extra work and can lead to another avoidable attempt. Quiqup’s status guide distinguishes failed and on-hold orders and advises merchants to include the reference and latest status timestamp when escalating a case. Quiqup’s order states guide

A reliable handoff also gives staff a way to see which message the recipient already received. If a courier marks the parcel as failed while a customer has already asked to reschedule, both records matter. A support agent should be able to tell whether the new appointment was confirmed or merely requested. The customer needs a status that reflects that distinction. The merchant needs enough information to avoid promising a second attempt that has not been arranged.

Measure the orders that recover as well as the ones that arrive first time

A first-attempt delivery rate is useful if the report explains what enters the denominator. It may include every dispatched order or only orders on which a first attempt was logged. It may exclude cancellations, returned parcels or addresses outside service coverage. Quiqup’s delivery page publishes a first-attempt figure and a separate overall success figure, without a common cohort and calculation method on that page. Those headline figures do not establish the rate at which a failed first attempt recovers. The operator’s service page is evidence of what it reports, while its process documents describe how the work is intended to happen. Quiqup’s delivery service page

Consider an illustrative merchant that dispatches 1,000 eligible orders and completes 920 on the first attempt. Of the 80 remaining orders, 50 later reach the recipient and 30 return to origin. On that basis, first-attempt success is 92%, eventual delivery is 97% and recovery after the first miss is 62.5%. If the merchant instead excludes 20 of the returns from the original denominator without explanation, the reported eventual success rate rises even though the number of parcels delivered stays the same. This example uses hypothetical figures and says nothing about Quiqup’s actual rates.

A useful scorecard also compares outcomes by promise, delivery area and type of exception. A slower service can appear more dependable if the clock gives it more time. A single high-volume neighbourhood can dominate the aggregate. Split the data enough to see whether address problems, failed contact or late handover account for the gap. Then compare the cost and success of a second attempt with the outcome of asking the customer to confirm before dispatch. The aim is to find where a different decision can improve the result.

A missed promise can also be recorded even when the parcel eventually arrives. For example, if the first attempt took place after the promised window and the customer was unavailable, the failed attempt and the late arrival are both relevant. If the same order is delivered the next day, the eventual delivery figure improves, while the original promise remains missed. Track the three events separately. The operations team can then improve recovery without treating it as a substitute for getting the first window right.

Look at staff workload alongside those measures. A process that relies on one person making repeated calls may rescue a small batch of orders and still be hard to operate on a busy day. Record the number of manual contacts needed before an order recovers, and check who is asked to resolve information the merchant could have captured at checkout. A change that reduces a routine source of manual work can improve delivery without asking couriers to move faster.

Keep delivery failures separate from customer returns

A parcel returned because the operator could not deliver it is a different case from a parcel the customer received and later returned. The first raises questions about address quality, contact, availability or the original promise. The second can reflect fit, product condition or a customer choice unrelated to the delivery. The warehouse may handle both. A merchant needs the records separated so it can decide whether to change the product, the fulfilment workflow or the courier’s instructions. Quiqup publishes a separate guide for placing a customer return and distinguishes it from a failed delivery returned to origin. Quiqup’s customer return guide

There is also an inventory consequence. A parcel marked for return may still be on a vehicle or waiting for inspection. A merchant may be able to sell the item again once it is physically received and checked. Those milestones need separate timestamps. If the system treats the delivery failure as immediate stock availability, the next shopper may buy an item that cannot yet be shipped. This is where the link between last-mile delivery and fulfilment matters to an independent merchant. The service includes the return journey and the information required to reopen the stock.

For a merchant testing a new delivery workflow, follow a few orders through both paths before judging the aggregate. Check that a successful order can be tied to its confirmation and that a failed one can be tied to a final decision and an inventory event. Include an order with a corrected address and one with a cancellation. Each should leave enough evidence for someone outside the original shift to explain what happened. The exercise will show where a status needs more detail or where the merchant and operator interpret it differently.

El Koussa’s account explains why Quiqup placed the shopper’s experience at the centre of its UAE operation. The workflow documents show how that choice extends beyond the first attempt. The courier returns the parcel, the system distinguishes an order that can go out again from one that needs a decision, and someone confirms the outcome. To judge whether that design is working, a merchant needs a record that connects the promise at checkout with the last verified status. That is the evidence that shows what happened at the door and what the operator did next.