A logistics SLA (Service Level Agreement) is the quantifiable agreement that sets minimum transport service levels —punctuality, completeness, detention times, document quality, and exception response— together with measurement windows, sources of truth, and consequences (penalties, credits, or volume loss).
You signed 96% OTIF with a Bajío retailer; the month closes at 91% and Legal wants evidence. GPS shows 09:58; the dock opened at 11:40. Did you miss? It depends on the clause — and whether your system measured the right event. Short guide: from PDF to auditable scorecard.
- typical retail/CPG OTIF in MX SLAs
- ≥95%
- delivery fill rate (National Study 2026)
- ~93%
- typical freight credit for misses
- 1–3%
- On Time inflation if gate ≠ dock event
- 8–12 pts
Cluster: distribution KPIs · OTIF · POD · detention · fill rate.
What a logistics SLA is (usable answer)
In Mexican operations, the SLA answers: what minimum service level did we agree, how do we measure it, and what happens on failure? It is not decorative legal prose. It is the bridge between the contract and the weekly scorecard by carrier, lane, and customer.
If your transportation management system (TMS) does not capture the event the contract defines, you cannot audit the SLA — and month-end fights consume traffic hours. In retail/CPG, the anchor is usually OTIF plus appointment windows; without geofence and proof of delivery (POD), the percentage is opinion.
Clauses your TMS must measure
Not every contract page is operable. The clauses that move money in Mexico are usually five: On Time, In Full / OTIF, detention (dwell), evidence (POD / Carta Porte), and exception response.
On Time
Measurable event: Geofence arrival / unload start
Typical MX threshold: Appt ±30–60 min
Source of truth: GPS + dock portal
OTIF / In Full
Measurable event: Complete order vs PO
Typical MX threshold: ≥95% retail; 90–95% B2B
Source of truth: POD + packing slip / WMS
Measurable event: Dock in − dock out
Typical MX threshold: 2–4 h free; then $/h
Source of truth: Geofence or ticket
Evidence
Measurable event: Digital POD + fiscal docs
Typical MX threshold: ≤24 h after delivery
Source of truth: Portal / ePOD
Exception
Measurable event: T−2 h alert or incident
Typical MX threshold: Response <60–120 min
Source of truth: 24/7 track and trace
The On Time window: gate vs dock
A large share of SLA disputes at Mexican DCs start here. If the contract says “arrival within appointment” and operations measures “unload start,” an On Time gate arrival can become Late due to receiver congestion — and On Time inflates ~8–12 points when you measure the wrong event.
Practical rule: name the event identically in the SLA and the TMS. For OTIF, align the On Time window with what the customer bills, not what GPS captures most easily.
Myths and mistakes drafting or measuring SLAs
Elige un paso para ver el detalle
Detalle del paso · 01
GPS without a dock geofence is not an SLA
How to operationalize the SLA in 5 steps
Move the PDF into TMS (or agent) configuration. Without event mapping, dashboards lie.
Elige un paso para ver el detalle
Detalle del paso · 01
Extract clauses
Step 1
Mexico service context: the 4th National Logistics Indicators Study 2026 (#SoyLogístico / LDM / EGADE) reports customer-delivery fill rate ~93% average in its sample — calibrate to your vertical and agreement; it does not replace your OTIF clause.
OCL and the trip file
OCL Cargo is an autonomous transportation management system (TMS) with agents: it joins windows, exceptions, proof of delivery (POD), and documents in a trip file so the SLA scorecard can be defended — not rebuilt in Excel at month-end. It coexists with your system of record; your team decides exceptions. When applicable, OCL can stamp invoices and Carta Porte. It does not guarantee OTIF or draft your contract.
Key takeaways6 points
- Logistics SLA = quantifiable service-level agreement (punctuality, completeness, detention, evidence, exceptions) with consequences.
- Without TMS timestamps, the SLA becomes WhatsApp negotiation.
- Typical Mexico clauses: OTIF ≥95%, exception alert <2 h, detention max 3–4 h, POD within 24 h, penalty 1–3% of freight.
- Measuring gate arrival when the contract bills unload start inflates On Time ~8–12 points.
- National Study 2026: delivery fill rate ~93% sample average — service context; calibrate your SLA/OTIF to your operation.
- Service sibling: OTIF. Hub: distribution KPIs.
Turn your SLA into an auditable scorecard
Related reading
Frequently asked questions
A measurable transport service agreement: what must be met (OTIF, detention, proof of delivery, exception response), in which window, with what evidence, and what consequences apply on failure.
At minimum: On Time with a defined event, OTIF/In Full, dwell/detention, evidence turnaround, and exception response time. Each needs a timestamp or document in the transportation management system (TMS).
Retail/CPG often requires 95–98%. Industrial B2B usually runs 90–95%. Below 90% on large accounts, credits or slot loss are common. The 4th National Study 2026 reports customer-delivery fill rate ~93% sample average — completeness context, not a substitute for your OTIF clause.
OTIF (On Time In Full) is usually the core service clause. The SLA defines the On Time window, In Full rule, and penalties; OTIF is the key performance indicator (KPI) that summarizes them in one AND percentage. See what is OTIF.
The contract definition wins. If it measures unload start, On Time gate GPS is not enough. Capture both timestamps for detention disputes.
Agents capture exceptions in minutes, consolidate proof of delivery (POD) and Carta Porte evidence, and audit 100% of trips against rate cards and windows. The scorecard stops being a month-end rebuild. When applicable, OCL can stamp invoices and Carta Porte.