When a Diwali Gift Does Not Reach the Employee: A Bangalore Fix List

A Diwali gift that never reached the employee is almost never a courier accident. It is an address list that shipped with gaps, a pincode nobody checked, or a proof of delivery that came back marked undelivered in the one week of the year when there is no slack left for a second attempt. The fix sits in the three days before dispatch, not the three days after. Here is what to settle before anything leaves the warehouse, how to catch a miss while the calendar still allows a re-dispatch, and what to actually do with the parcels that come back.

Why does a Diwali gift fail to arrive at all?

In a Bengaluru gifting run there are four causes, and three of them are yours rather than the courier's. The first is a home address that was true when someone joined and is not true now; a hybrid roster goes stale faster than an HR system gets updated. The second is a missing phone number, which is how a delivery fails silently rather than loudly. The third is a pincode that was mistyped or is not serviceable, which turns into a parcel idling at a hub. The fourth is the only genuinely seasonal one: during Diwali week a large share of the city has travelled, so an address that works in August has nobody behind the door in late October.

What has to be in the address list before anything ships?

For individual dispatch OfficeSmart works from a CSV with employee name, city, pincode and phone for every recipient. Treat that as the minimum, not the target, and add the fields that decide what happens when one line fails.

• Name, city, pincode and phone for every recipient, with the phone treated as mandatory rather than nice to have.
• A column saying whether this person is getting the gift at the office or at home, because the two groups have different dispatch dates.
• One named owner for the file. A list maintained by three people is a list nobody reconciles.
• A reconciliation against the current HR roster rather than last year's file, done the week before dispatch.
• A flag for anyone on long leave, on notice, or newly joined after the headcount was locked.
• A named person on every office consignment, never a department.

Which pincodes decide your dispatch date?

Not the average one. The furthest one. The published Bangalore timelines are same-day across the city for orders placed before 11 AM, and for individual dispatch pan-India, 2 days to metros such as Mumbai, Delhi, Chennai, Hyderabad, Pune and Kolkata, 3 to 4 days to Tier-2 cities, and 5 to 7 days to remote pincodes, shipped via Blue Dart, Delhivery or DTDC. International addresses run 5 to 10 days via DHL, FedEx or Aramex. If half your roster is in Koramangala and HSR and the other half is spread across Tier-2 and remote pincodes, the second half sets the date the whole order has to leave, unless you deliberately split the run into two dispatches.

Serviceability is the one check you can finish before dispatch rather than discover after it. OfficeSmart covers 99% of Indian pincodes and flags a pincode that is not serviceable proactively, before dispatch, so an unserviceable address becomes a question you answer in advance instead of a parcel you chase later. Send the pincode list early for exactly that reason.

How do you know a delivery failed before the employee tells you?

The data is already there. Individual dispatch comes with a tracking link per shipment and a POD per shipment. What is usually missing is a person whose job is to read it. A parcel resting at a courier hub does not raise an alert; it simply stops moving, and the absence of an event is easy to miss in a sheet with two hundred rows.

Give the tracking sheet a status column and one owner, and have that person look at it twice: once two days after dispatch, when metro deliveries should have landed, and again at the point your furthest pincode was due. Anything without a POD by the second check is a miss that still has days left to fix.

How much slack does the Diwali calendar actually give you?

Less than the dates suggest, because a re-dispatch is a second delivery that has to fit inside the same window. The published booking guidance for Bengaluru is 15 days before Diwali for standard delivery, with rush orders handled in 7 days at a small surcharge, and deliveries timed to reach before the first day of Diwali week. A custom kit is 8 days. A brief with headcount, theme and budget comes back with 2 to 3 options within 24 hours, so the proposal stage is not where schedules are lost.

Pan-India is tighter. The published guidance is to book by mid-September for guaranteed Diwali-week delivery nationally; late-September bookings remain workable for metros with a small rush premium, while Tier-2 and Tier-3 deliveries need the earlier booking to stay safe. Work it backwards and the shape is clear. A Bengaluru-only run booked at 15 days leaves a few genuine days for a second attempt. A run going to remote pincodes leaves almost none, which means the plan for a failed delivery has to exist before the first consignment goes out, not after the first POD comes back empty.

Should you order spares, and how many?

Yes, and the number is a decision to make in the original purchase order rather than as a second order three weeks later. A top-up run is quoted on its own terms, so a handful of units added at PO stage is a different conversation from a small order placed in peak season against a design that has already closed. Settle three things in writing while the PO is open: how many spare units the order carries, where they sit until they are needed, and who in your company is allowed to release one.

What do you do with a hamper that has come back?

There are only three moves: re-dispatch to a corrected address, redirect it to the office for a hand-over, or replace the gift with a voucher and keep the parcel for a spare. Which one is available depends on what is inside. A hamper with food in it has a shelf life, and the return leg has already spent part of it.

The terms around a return are not published anywhere, which makes them exactly the questions to put to your supplier in the quote rather than in the week you need the answer. Ask whether a returned consignment comes back to the warehouse or to your office, how long it is held before something happens to it, whether a re-dispatch is charged and at what, and what happens to anything perishable that has made a round trip. An answer in the quote is worth more than the same answer offered sympathetically on the Monday of Diwali week.

When is a voucher the better instrument?

When delivery is the risk you are trying to remove. A digital voucher has no address collection, no courier, no per-shipment tracking and no undelivered parcels coming back, and a recipient in Indiranagar and a recipient in a Tier-3 town receive on the same schedule. Bulk corporate gift vouchers are issued within 24 hours of a payment being confirmed, with no minimum order and no cap on quantity or value. Physical cards are couriered from the Hulimavu warehouse instead, so transit time applies on top of that issue window.

That is why a split run is common for Bengaluru teams with distributed staff: hampers for the office and the city, where a same-day dispatch and a hand-over are straightforward, and vouchers for the tail — the remote pincodes, the people whose current address you do not have, and the three parcels that came back. The tail is small, it is where every failed delivery lives, and it is the part of the roster where the instrument that cannot fail on delivery is worth more than the one that looks better on a desk.

What should you write down before you close the file?

Three numbers, and they take ten minutes. Which addresses failed and why. How many days before the first day of Diwali week your last consignment actually landed. How many spares you used. Next year that file is the difference between reconciling a roster and rebuilding one, and it is the only part of this that gets easier by being written down.