CPFR (Collaborative Planning, Forecasting and Replenishment) is a framework where manufacturer, distributor, and retailer share data and jointly decide demand and inventory. For a shipper or 3PL on the Mexico–US corridor, it only pays off if that agreement reaches the DC, the truck, and delivery evidence — not if it stops in a forecast file.
This guide covers what it is, what it is for, advantages and limits, how it differs from VMI and S&OP, four steps with Mexican examples (Buen Fin, CPG to retail, nearshoring), and where freight fits: a shared forecast fails if dock, proof of delivery (POD), and exceptions are invisible. OCL Cargo does not sell “CPFR software”: it executes the trip file and exceptions after the plan.
- plan · forecast · replenish · review
- 4 stages
- shipper · retail · 3PL / carrier
- 3 actors
- wedge: forecast, dock, and POD
- MX–US
- cited origin; org. no longer operates
- VICS 90s
Cluster: freight journey · supply chain examples · lean supply chain.
What CPFR is (definition + origin)
In the supply chain, CPFR connects sales, inventory, and orders across companies that would otherwise optimize in silos. The manufacturer sees retail promotions; retail sees supplier capacity and lead time; together they reduce the guessing that creates stockouts or overstock.
The concept was formalized in the late 1990s under the Voluntary Interindustry Commerce Standards Association (VICS), a nonprofit focused on intercompany commerce standards — especially CPG and retail. Industry literature often cites early retail–supplier pilots (e.g. the Walmart / Warner-Lambert thread). VICS as an organization no longer operates; the CPFR framework remains vocabulary and practice, not a live certification someone “sells” you.
In 2026, “doing CPFR” on Mexico–US lanes means less a standards logo and more an operable agreement: promo calendars, weekly forecast, exception thresholds, and handoff to transport. Corridor patterns: Mexico–US supply chain examples.
What it is for: forecast to freight
CPFR does not end when the case count closes. It aligns three layers that on the corridor usually live in different teams.
Chain
Three aligned layers
Forecast
Shared demand
Replenish
Orders / inventory
Run freight
Trip + evidence
- Collaborative forecast. An agreed demand view (baseline + promo + seasonality), with an exception owner when retail and supplier disagree.
- Replenishment. Orders, DC–store transfers, or plant–distributor moves synced to the plan — not last-minute surprises that blow capacity.
- Freight execution. Capacity, dock appointments, documents, and POD on the same trip ID. Without this, OTIF (On Time In Full) lies even if the forecast “closed.” Map: Mexico freight journey.
Trip traceability (who moved what, with what evidence): what traceability is. Lean on freight waste: lean supply chain.
Advantages and honest limits
CPFR improves coordination; it does not replace trust or clean data. Use it to decide whether the effort is worth it with a strategic partner — not to “certify” the whole network on day one.
Service
What you gain (if executed): Fewer promo/peak stockouts; better OTIF when the plan reaches the dock
What blocks it (if ignored): “Agreed” forecast with no freight capacity or appointments
Inventory
What you gain (if executed): Less mutual safety stock driven by distrust
What blocks it (if ignored): Late or incomplete POS/inventory data
Cost
What you gain (if executed): Fewer rush moves, false freight, and exception tolls
What blocks it (if ignored): Change culture: sales vs logistics vs accounts payable silos
Relationship
What you gain (if executed): Clear exception rules among shipper, retail, and 3PL
What blocks it (if ignored): Lack of trust: each side “protects” its spreadsheet
Limits no software negotiates away: master-data quality (SKU), exception discipline, and change management. Without an exception owner, CPFR becomes another weekly meeting.
CPFR vs VMI vs S&OP
Three names that get mixed in RFPs. The table helps you avoid buying the wrong module.
Scope
CPFR: Between companies (partners)
VMI: Between companies; supplier leads replenishment
S&OP: Inside one company
Focus
CPFR: Shared plan + forecast + replenishment
VMI: Inventory at the customer site / replenishment rules
S&OP: Align demand, supply, and internal finance
Who decides
CPFR: Both (with exceptions)
VMI: Mostly the supplier (under agreement)
S&OP: Sales, operations, finance, supply chain
Typical output
CPFR: Agreed forecast and orders
VMI: Automated or semi-automated replenishment orders
S&OP: Internal production / supply plan
Mexico–US fit
CPFR: Retail promo, CPG to DC, nearshoring
VMI: Stable high-volume SKUs
S&OP: Plant or 3PL aligning internal capacity
Common coexistence: internal S&OP produces a plan; CPFR confronts it with the customer or supplier; VMI can automate replenishment on stable SKUs. None replaces the trip file.
Four steps with Mexico examples
Operable version (not the nine sub-steps from a VICS manual). Each stage includes an illustrative corridor example — not invented brand metrics.
Cycle
Four CPFR stages
Agree
Joint plan
Forecast
Exceptions
Replenish
Orders / transfer
Execute
Freight + review
1. Joint agreement and business plan
Roles, horizon (weeks/months), which data is shared (POS, inventory, capacity), and exception thresholds. Example: retail and CPG lock a Buen Fin calendar — promo windows, priority SKUs, and who escalates if expected lift does not match DC capacity.
2. Collaborative forecast
Each side contributes a view; an agreed forecast is published with exception lists (promo not reflected, lead time, historical stockout). Example: weekly CPG to retail DC — a high-velocity SKU discrepancy is resolved before order cut-off, not Tuesday on WhatsApp.
3. Order / replenishment plan
The forecast becomes orders, transfers, or load builds. Example: nearshoring plant to border distributor: case plans must match dock slots and dry-van availability — not only MRP.
4. Execution and review
Trips, appointments, POD, and review of bias (forecast vs actual) and service (OTIF). Example: if the Buen Fin forecast “closed” but dock dwell exploded, the problem was not only demand — it was freight sync. Usable POD: POD guide for shippers. Honest OTIF: what OTIF is.
How to implement + KPIs
Start with one partner and one SKU family — not “CPFR across the whole network.” Define KPIs before the pilot; without a baseline, any % is marketing.
Forecast bias / error
Question it answers: Do we systematically over- or under-forecast?
Failure signal: Promo with no lift, or lift with no stock
Stockouts
Question it answers: Is product missing where the plan said it would be?
Failure signal: POS at zero with an “agreed” order
OTIF
Question it answers: On time and complete?
Failure signal: Missed window, shortage, wrong SKU pick
Dock dwell
Question it answers: How long does the trip wait at the DC?
Failure signal: Unrealistic appointments vs forecast volume
% complete trip file
Question it answers: Does the trip close with evidence before pay?
Failure signal: Sampling pay; POD/CFDI mismatches
- Pick a strategic partner and 1–2 categories (not 400 SKUs on day one).
- Write rules: data, frequency, exception owner, confidentiality.
- Publish an agreed forecast + exception list (tool can be a portal or a governed sheet).
- Connect replenishment to DC and freight capacity.
- Review weekly: bias, OTIF, dwell, trip file — act or escalate.
Optimize: ERP, WMS, and TMS
Honest stack: CPFR lives on data; systems execute different layers. Buying only a WMS does not fix the handoff to the truck.
ERP
Role in CPFR: Order, book inventory, masters
What it does not do alone: Real-time dock visibility or street POD
WMS
Role in CPFR: Picking, slots, DC inventory
What it does not do alone: Tendering, freight tower, or pre-pay audit
TMS
Role in CPFR: Trip, rate, status, transport documents
What it does not do alone: Replace the commercial CPFR agreement between partners
TMS depth: what a transportation management system (TMS) is. If the forecast is shared but the tower re-keys status across portals, you have fake digitization — not mature CPFR (fake freight digitization).
Common mistakes
The same failures show up in retail, CPG, and nearshoring when CPFR is sold as software instead of process.
- Confusing CPFR with buying a WMS or “forecast module” without a partner agreement.
- Sharing a spreadsheet with no exception owner or thresholds.
- Closing a Buen Fin forecast with no dock or van capacity.
- Measuring only “the truck arrived” instead of OTIF + trip file.
- Ignoring the 3PL: the retail–supplier plan breaks in the operator’s tower.
- Labeling VMI or S&OP as CPFR in the RFP (semantic scope creep).
Operable checklist
Use it before claiming you “already do CPFR” with a corridor partner.
Elige un paso para ver el detalle
Detalle del paso · 01
Partner and scope
What OCL executes after the CPFR plan
OCL Cargo is an autonomous TMS with agents that operate screens and portals. It does not invent a “CPFR” product: it assumes the collaborative plan already exists (or is maturing) and closes the execution layer — trip file, exceptions, and stamping when applicable.
- Pre-pay cross-check of rate + CFDI + Carta Porte + GPS + POD on the same trip — even if the forecast “balanced” in planning.
- OCL can stamp invoice and Carta Porte when fiscal scope applies.
- Your team on exceptions (dwell, shortage, incomplete docs); agents on repeatable tower work.
- Coexists with your ERP/TMS: typical pilot 6–8 weeks; when auditing 100% of the pilot flow, the published pattern is recovering 5–7% of freight spend.
After the plan
Execution layer
Assign
Measurable tender
Monitor
Exceptions
Tie POD
To trip ID
Audit
Before pay
Key takeaways5 points
- CPFR = Collaborative Planning, Forecasting and Replenishment: partners jointly plan, forecast, and replenish with shared data; the 1990s VICS framework is still cited even though the organization no longer operates.
- It aligns forecast, replenishment, and freight execution; without dock, POD, and visible exceptions, collaborative planning stays in a spreadsheet.
- Upside: fewer stockouts and less mutual safety stock; limits: trust, data quality, and change management — not magic software.
- Four steps + Mexico examples: Buen Fin, CPG to retail DC, nearshoring plant to distributor; measure OTIF, forecast bias, stockouts, and dwell.
- OCL closes the execution layer (trip file + exceptions + agents) after the CPFR plan — it does not invent a CPFR product; it coexists with your TMS/ERP.
Does your CPFR reach the dock — or stop at the forecast?
Related reading
Frequently asked questions
CPFR (Collaborative Planning, Forecasting and Replenishment) is a framework where manufacturer, distributor, and retailer jointly plan, forecast, and replenish with shared data — not each in a silo. On Mexico–US lanes the cycle only closes if the plan reaches the dock, the trip, and proof of delivery (POD).
The framework was formalized in the late 1990s under the Voluntary Interindustry Commerce Standards Association (VICS), after retail–supplier pilots (e.g. the Walmart / Warner-Lambert thread cited in industry literature). VICS as an organization no longer operates; CPFR remains a collaboration practice name, not a live “certification” someone sells you.
No. Vendor Managed Inventory (VMI) puts more replenishment responsibility on the supplier. Sales and Operations Planning (S&OP) aligns teams inside one company. CPFR is collaboration between trading partners. Many operations run internal S&OP and feed CPFR conversations with customers or suppliers.
In the operable four-stage version: (1) joint agreement and business plan, (2) collaborative forecast and exception resolution, (3) order / replenishment plan, (4) execution and performance review. Nine-step models exist; in Mexico freight the critical part is that steps 3–4 include capacity, dock appointments, and the trip file.
Forecast bias/error, stockouts, OTIF (On Time In Full), dock dwell time, and % of trips with a complete file (rate · CFDI · Carta Porte · GPS · POD). Calibrate thresholds with your operation; do not copy brochure percentages.
Not on day one. CPFR is process and data governance between partners. A warehouse management system (WMS) helps in the DC; a transportation management system (TMS) runs the trip. Without dock, POD, and exception visibility, the shared forecast breaks in freight — see the Mexico freight journey.
OCL does not sell a “CPFR software” module. It is an autonomous TMS: agents build the trip file, escalate exceptions to your team, and can stamp invoice and Carta Porte when fiscal scope applies. It closes the execution layer after the collaborative plan — coexisting with your system of record.