Somewhere in your footer is a page nobody reads until they need it — and then it's the only thing standing between you and a refund fight. A real shipping policy page is thirty lines that define the deal: how fast, what COD costs, what happens when it fails.
What must be on it
Processing time (order to dispatch — often longer than transit), transit ETAs by region, COD availability and fees, free-shipping terms, the NDR/re-attempt reality, return/refund timeframes, and a contact. Each line is a dispute that ends in a link instead of an argument.
The ETA honesty rule
Promise the P75, deliver the P50 — quote the time you'll hit 75% of the time, and most orders beat the promise. '3–5 days' delivered in 3 is a delighted customer; '2–3 days' delivered in 4 is a complaint.
The COD section that saves margin
'COD available up to ₹X, orders may be phone-verified, repeated refusals remove COD eligibility' — three lines that establish your rights before you need them.
The festive clause
'During peak seasons, delivery may take 1–2 days longer' — the sentence that covers October honestly, written before October arrives.
Pakka Parcel automates exactly this — the pipeline from order to AWB without the manual steps.
See how →The playbook
Write processing + transit separately
'Ships in 1 day + 3–5 transit' is clearer than '4–6 days'.
Promise P75 not best-case
The ETA you beat is better than the one you miss.
COD terms in writing
Verification rights and refusal policy, stated upfront.
Add the seasonal buffer clause
October's delays are covered by a sentence written in March.
