Reducing parcel refusals in Tunisia: diagnose causes before changing the process

Reducing parcel refusals starts with understanding the reason, not simply making more calls. A parcel rejected because the total was unexpected requires a different response from one that cannot reach an incomplete address. Give every case a documented cause and an appropriate action, then compare similar shipment groups. No success percentage applies to every product, destination or season, and a returned parcel does not by itself prove bad customer intent.

Define the outcomes before calculating a rate

Separate cancellation before dispatch, refusal at the door, an unreachable customer, an address error, damage and a return after delivery. Combining everything into one box hides the operational issue. Record who supplied the reason and whether it is confirmed or still needs clarification. No answer and rejected the price are different findings.

Measure a group defined by dispatch date and display open shipments alongside the result. Otherwise a delay can be mislabelled as either success or failure. Retain the product, destination and carrier too: a problem may belong to one segment rather than the entire store.

Review the promise the customer actually received

Read the advertisement, product page and conversation preceding the order. Is the total including delivery clear? Are dimensions, quantity and size understandable? Is a pictured accessory included or just shown for context? A short confirmation call cannot compensate for a page that promises something missing from the parcel.

Consult the Tunisian Ministry of Commerce consumer information when preparing clear commercial terms. Avoid artificial pressure and changing the deal during confirmation. Ask someone who did not build the page to describe what they expect to receive. A gap between that description and the actual contents is a practical clue.

Confirm the points most likely to cause mistakes

Review order reference, product, colour or size, quantity, total and address. Ask only for missing information, then save the result. If a customer changes an option, update the order before creating the shipment. A correction left in a separate chat may never reach the person packing it.

This diagram summarises the core confirmation checks. Refusal diagnosis adds the reason actually observed after dispatch and the follow-up action described below.

A worked example: eight returns do not share one cause

A fictional store dispatches fifty parcels: forty are delivered, eight return and two remain open. Returns among closed cases are 8 ÷ 48, approximately 16.7%. Returns among all dispatches are 8 ÷ 50 = 16%. Either definition can be useful, but switching denominators silently from week to week makes the comparison unreliable.

Documented cause	Cases	First action
Unexpected delivery charge	4	Show the total before ordering
Delay beyond the promise	2	Review the promise and notify
Unsuitable size	1	Provide clearer actual measurements
Changed mind	1	Record without assumptions

At an illustrative 7 TND cost per return, eight cases cost 56 TND. The four price-related cases represent 28 TND potentially avoidable in a scenario, not savings already achieved. A new shipment group must be measured after the page is corrected.

Respond to a failed attempt according to its cause

Before calling, check the latest status and its timestamp. Ask the carrier what is needed: a corrected phone number, a location detail or a suitable time confirmed with the customer. The Navex tracking and support information provides examples of channels to locate with your actual provider. Do not promise parcel opening or a free additional attempt unless that service is confirmed.

Make contact useful and specific: “An attempt was not completed; is this address still correct?” Avoid blame. If the customer cancels, record the request and pass it through the carrier’s procedure rather than continuing dispatch as if nothing has changed.

Test one identifiable improvement

Choose a frequent cause your store can influence. Matjri product and order tools can help keep descriptions, choices and references organised. Technical tools do not replace accurate promises or a human review of what happened.

1. Describe the issue in a verifiable sentence.
2. Assign one correction and a responsible person.
3. Record when it began and which orders received it.
4. Wait for enough closed outcomes, then compare the same definition.
5. Keep what you learned even if the rate does not improve.

Do not post customer phone numbers or accusatory lists in public groups. Retain necessary order facts under appropriate access controls, and check for mistakes before penalising someone because of an unconfirmed reason or a status attached to the wrong order.

Questions that help choose the next step

Does confirmation prevent every refusal?

No. A customer’s circumstances, product condition or transport timing can change after the call. Confirmation removes misunderstandings you can identify at that point; the remaining workflow still needs attention.

Should I change couriers when returns increase?

Check causes and destinations first. If unclear totals explain most cases, another carrier will not fix your product page. Test a different provider when evidence points to the service itself.

What should I do this week?

Review ten unsuccessful closed cases and classify the reasons. Correct the clearest store-controlled issue, then monitor a new group without changing several unrelated processes at once.