To dispute a Myntra penalty charge, identify the deduction in your settlement report, compare it with the penalty terms in your seller agreement, collect order-level proof such as dispatch and return records, raise the dispute through your Myntra seller support or account manager within the allowed window, and track the claim until the amount is reversed or rejected.
What counts as a penalty charge in your Myntra payout
A penalty is any deduction that is not a commission, a fixed fee, shipping or a return adjustment, but is levied for a performance or compliance lapse. The names and categories vary by seller agreement and by period, so do not assume a standard list. Your own settlement report and the commercial annexure of your agreement are the source of truth.
Penalty-type deductions you may see, depending on your terms, relate to things like delayed dispatch, seller-side cancellations, quality or wrong-item issues, or non-compliance with packaging or labelling rules. Confirm which of these apply to you, and at what amounts, from your agreement and the latest rate card or policy communication from Myntra.
The first task is simply to isolate them. In a payout file, penalties are often mixed in with other adjustments, so filter by the deduction or remark column and separate them from commissions and return-related charges.
Before you dispute: check the charge against your terms
Not every penalty deserves a dispute, and a weak dispute wastes time. Run these checks first.
- Is the charge covered by your agreement? Find the clause or policy that permits it and note the stated amount or formula.
- Is the amount calculated correctly? Recompute it using the order value, quantity or slab the terms specify.
- Is it a duplicate? Check whether the same order or item was penalised twice across settlement cycles.
- Is the underlying event true? Compare the claimed lapse, such as late dispatch, with your own timestamps.
- Is it within the window? Check the dispute timeline in your agreement or with your account manager, and note the date you first saw the deduction.
If a charge fails any of these checks, you have a dispute. If it passes all of them, record it as a valid cost and focus on preventing it.
Build the evidence pack for each order
Marketplace support teams respond to specific, verifiable claims. A one-line complaint that penalties are too high rarely works. Prepare a compact pack per order or per batch:
- Order ID, style or SKU, settlement date and the exact deduction line from the settlement report.
- The clause or policy reference you are relying on.
- Your internal proof: warehouse pick and pack time, handover or manifest record, courier tracking events, and any communication with Myntra or the logistics partner.
- For return-linked penalties, the return receipt, QC images and notes, and the original dispatch images if you keep them.
- Your recalculation, showing what the charge should be versus what was deducted.
Keep one row per order in a simple sheet, so a batch of similar cases can be raised together with a consistent explanation.
Step-by-step: raising the dispute
- Export the settlement data. Download the relevant Myntra settlement reports and filter the penalty lines.
- Classify each line. Mark it as valid, incorrect amount, duplicate, factually wrong or unclear.
- Group similar cases. Batch by reason, such as incorrect dispatch delay, so the explanation is reusable.
- Raise the claim through the channel Myntra specifies. This could be the seller portal, a support ticket or your account manager. Confirm the current process with Myntra, as it can change.
- State the ask clearly. Mention the order ID, deduction amount, reason for dispute, the clause relied on and the reversal you expect.
- Record the reference number and date. Without a ticket reference, follow-ups become difficult.
- Escalate in sequence. If there is no response within the stated turnaround, follow up with the ticket reference, then escalate to your account manager.
Keep the tone factual. Attach evidence in a format that is easy to open, and avoid sending long email chains in place of a clean case sheet.
Track the claim until the money is back
A raised dispute is not a recovered one. Reversals may arrive in a later settlement cycle, partially, or as a net adjustment that is hard to spot. Maintain a recovery tracker with these columns:
| Field | Why it matters |
|---|---|
| Order ID and penalty line | Links the claim to the original deduction |
| Amount disputed | Sets the expected recovery |
| Ticket reference and date raised | Needed for follow-up and window checks |
| Status | Open, accepted, rejected or credited |
| Amount credited and settlement date | Confirms actual recovery |
| Reason for rejection | Shows patterns to fix or contest |
Reconcile every later settlement against this tracker. If a credit appears, tick the claim off; if a rejection arrives, decide whether to appeal with better evidence or write it off.
Make penalty checks a monthly routine
Penalty disputes work best when they are done every settlement cycle rather than once a quarter, when evidence is stale and windows may have closed. Assign one person on the finance or ecommerce team to review penalty lines after each payout and update the tracker.
Tools can help. MarketplaceMetrics by Fundle reconciles marketplace sales and settlements, checks commissions and fees against the terms you have agreed, and tracks returns and recovery cases. Myntra Excel reports are reviewed, and coverage of other marketplaces is a matter for discussion. Whether you use a tool or a spreadsheet, the discipline is the same: compare every deduction with the terms, keep evidence, and follow each claim to closure.
Also review penalty trends by reason. If dispatch-delay penalties keep recurring, the fix may lie in warehouse cut-off times, not in disputes.
Worked example
Illustrative example only; figures are not actual Myntra rates.
Suppose a settlement report shows three penalty lines in one cycle, and your agreement states a certain charge for delayed dispatch (confirm the real figure in your own terms).
| Order | Deducted (₹) | Check result | Action |
|---|---|---|---|
| A101 | 200 | Your manifest shows dispatch within the committed time | Dispute with manifest and courier scan |
| A102 | 200 | Same order penalised in the previous cycle | Dispute as duplicate |
| A103 | 200 | Dispatch was late and the clause applies | Accept and log as valid cost |
Disputed amount: ₹400 across two orders. Accepted cost: ₹200. Log the ₹400 in your recovery tracker with ticket references, then check the next settlement for the credit.
Questions and answers
How long do I have to dispute a Myntra penalty?
The window depends on your seller agreement and any current Myntra policy communication, so there is no universal number to quote. Check your agreement, ask your account manager to confirm in writing, and note the date each deduction first appeared in your settlement.
Where do I find Myntra penalty charges in my reports?
Look in your settlement or payout reports, in the deduction, adjustment or remarks columns. Filter by order ID and separate penalties from commissions, fees and return adjustments. If a line is unclear, ask Myntra support for the definition before deciding whether to dispute.
What evidence works best for a penalty dispute?
Order-level proof works best: dispatch or manifest timestamps, courier tracking events, return QC images, and the agreement clause you rely on. Add your recalculation of the correct amount. Specific, verifiable evidence is far more persuasive than a general complaint about charges.
Should I dispute every penalty I receive?
No. Dispute only charges that are duplicated, miscalculated, factually wrong or not supported by your terms. Valid penalties should be accepted and analysed for root causes. Disputing weak cases can slow down your stronger claims and strain the working relationship.