A retail / DC chargeback is the deduction a retailer or distribution center applies to your account when you miss compliance rules, OTIF (On Time In Full), labeling, appointments, shortages, or other dock conditions. As a cash key performance indicator (KPI) in the distribution hub it is expressed as MXN deducted ÷ sales or ÷ deliveries: pesos you no longer collect—not only an “almost” on the service scorecard.
In the distribution KPIs hub this metric closes the Cash group with complete trip files, pre-pay audit, detention, and accessorials. Without it, the board celebrates OTIF while finance absorbs debit notes.
- hub KPI group
- Cash
- sales or deliveries
- MXN÷
- retailer (not a viral table)
- Policy
- evidence = operable dispute
- 1 ID
Cluster: OTIF · POD · lumper / handling · accessorials.
What a retail / DC chargeback is
In Mexico the typical pattern is chain retail or DC: late to the appointment, wrong label, misaligned ASN, shortage at receiving, or documentation that fails the supplier manual. The buyer issues a debit note and deducts at reconciliation.
Do not confuse it with a government fine or a carrier accessorial. Here collection power sits with the receiving customer / retailer, per its policy — and that policy changes by chain. Calibrate; do not generalize amounts.
Cash KPI formula
The hub suggests measuring it as cash, not as “number of incidents.” Pick a denominator and do not change it every month.
Chargebacks % sales
Formula: MXN deducted ÷ period sales × 100
What it is for: Compare vs margin and other cash leaks
Chargebacks per delivery
Formula: MXN deducted ÷ deliveries (or orders) in the period
What it is for: See intensity per trip / order
Dispute win rate
Formula: MXN recovered ÷ MXN disputed
What it is for: File quality, not only dock performance
Debit aging
Formula: Days from debit note to close
What it is for: See if accounts payable fights on time
Separate accepted debits (operable fault) from debits in dispute. Mixing them hides whether the problem is the dock or the file.
Common families in Mexico retail
Families repeat; amounts and deadlines do not. The evidence column is what you can standardize without inventing the retailer’s rate card.
Appointment / window
Typical trigger: Arrival outside slot or no-show
Evidence to dispute: Confirmed appointment + GPS/geofence + dock record
Note: Align On Time with OTIF
Labeling / ASN
Typical trigger: Bad label, ASN ≠ order
Evidence to dispute: Label photo + ASN ↔ packing slip ↔ PO
Note: Typical perfect-order document zero
Shortage / In Full
Typical trigger: Short receive vs order
Evidence to dispute: POD with count + receiving WMS
Note: Usable POD
Damage / refusal
Typical trigger: Damaged or refused freight
Evidence to dispute: Photos + signed receiving note
Note: Do not fight without documented condition
Doc compliance
Typical trigger: Invoice/data/manual requirements
Evidence to dispute: File aligned to customer policy
Note: Per retailer policy — calibrate
Handling / yard
Typical trigger: Lumper, wait, dock rules
Evidence to dispute: Authorization + who pays by contract
Note: Lumper ≠ automatic chargeback
Evidence to dispute (no invented fines)
The dispute window is set by the retailer. What you control is having the file ready before it expires. Do not publish a “typical fine of $X” as universal truth.
- One ID joining order, trip, appointment, and debit note.
- Defensible timestamps (appointment, arrival, unload start).
- POD with receiver, quantity, and condition when the code requires it.
- Authorizations for handling or changes (email/portal, not only chat).
- Current customer policy on file (version and date).
Vs accessorials and lumper
Three money fronts get confused at the dock. Separate them on the board or you pay the same event twice without noticing.
Process: from alert to debit note
A short cycle keeps finance from discovering the deduction after month close. Tower and accounts payable share the same ID.
Defensible cash
Prevent, evidence, and dispute
Prevent
Appt and docs OK
Capture
POD and photos
Alert
Typed exception
Build
ID file
Dispute
Inside window
Errors that leave the deduction firm
These failures turn a disputable debit note into sunk cost.
| Error | Result |
|---|---|
| Loose or illegible POD | Cannot prove In Full or condition |
| Appointment in Excel, arrival only in WhatsApp | On Time undefendable |
| Dispute outside the window | Debit firm even if you were right |
| Mixing lumper with chargeback | You pay the yard and the debit note |
| No reconciliation owner | Finance accepts “to close the month” |
Anti-deduction checklist
Use it per strict customer, not as a generic brochure.
Elige un paso para ver el detalle
Detalle del paso · 01
Current retailer manual
What OCL executes
OCL Cargo concentrates exceptions, POD, and trip documents so the dispute file exists when the debit note arrives — not weeks later in an email thread. Agents type milestones; your team close exceptions and the commercial negotiation with the retailer.
We do not replace DC policy or promise to recover 100% of deductions. The useful pattern is the hub’s: fewer undefendable debits from missing trails, same ID for tower and accounts payable.
Key takeaways6 points
- DC chargeback = retailer/DC deduction for compliance, OTIF, label, appointment, or shortage — hub cash KPI.
- Typical formula: MXN deducted ÷ sales (or ÷ deliveries). Write the denominator down.
- Do not copy fine tables: amounts and windows are per retailer policy — calibrate.
- Dispute = evidence tied to the ID (POD, appointment, ASN, authorization), not a loose PDF weeks later.
- Distinguish chargeback (buyer deducts) from accessorial/lumper (carrier or yard bills).
- OCL builds the dispute file; it does not guarantee winning every debit note.
Does OTIF “look fine”… while finance still absorbs debit notes?
Related reading
Frequently asked questions
It is the deduction a retailer or distribution center (DC) applies to your invoice or account for compliance misses, OTIF (On Time In Full) failures, labeling, appointments, shortages, or other dock rules. As a cash key performance indicator (KPI) it is expressed as MXN deducted ÷ sales or ÷ deliveries in the period.
No. An accessorial is usually an extra carrier charge (detention, lumper, etc.). A DC chargeback is a buyer/retailer deduction against the shipper or supplier. Sometimes the same dock event triggers both — see who pays lumper.
We do not invent fine schedules. Each retailer publishes (or negotiates) its policy: amounts, dispute windows, and codes. Calibrate to the customer manual and your history; do not copy a viral schedule as law.
It depends on the family: kept appointment (GPS/geofence + record), usable POD, correct ASN/label, receiving count, lumper authorization. Without a tied trip ID, the dispute is opinion.
Many debits start as On Time / In Full or documentation fails. OTIF and perfect order explain service; the chargeback translates the penalty into pesos.
Commercial / key accounts often “feel” the deduction; operations and tower generate evidence; accounts payable reconciles the debit note. Without a shared owner of the file, you pay twice: the penalty and the internal fight.
It concentrates milestones, POD, and documents under the same ID so the dispute file exists before accounting close. It does not negotiate retailer policy or guarantee winning every chargeback; it reduces undefendable debits from missing trails.