OEM returnable packaging: RPM circulation between plant, supplier, and dealer
Returnable packaging is the automotive industry’s most expensive invisible asset — a typical OEM carries tens of millions of dollars in bins, racks, dunnage, and pallets in perpetual circulation between Tier 1s, plants, and dealers. Shipsy’s RPM (Returnable Packaging Material) module tracks each loop, flags leakage, and orchestrates returns so the OEM isn’t continually paying to replenish what’s actually gone missing in its own network.
Why RPM is a P&L problem, not just an ops problem
Automotive OEMs deploy returnable containers to move parts and subassemblies between Tier 2, Tier 1, plants, and sometimes dealer networks. Specialized bins, tailored dunnage, metal stillages, and reusable pallets are engineered for specific parts. The financial reality:
- Fleet size is large. A single plant-to-Tier-1 corridor often carries thousands of specific container types in rotation.
- Replacement cost is meaningful. A custom engineered container can cost hundreds to thousands of dollars to replace.
- Leakage is invisible without tracking. Containers get lost, repurposed by Tier 1s, damaged, stuck at end-of-life vehicle scrap, or simply never circled back.
- Production depends on availability. If Tier 1 doesn’t have empty containers, it can’t ship next cycle — line feed risk.
Legacy approaches rely on supplier honesty, periodic audits, and quarterly reconciliation. The industry standard of ~10–30% annual leakage on un-tracked fleets reflects the cost of that approach.
How Shipsy’s RPM module closes the loop
Container-level identity. Each container carries a unique identifier (barcode, QR, or RFID where the economics justify). Identity persists for the life of the asset.
Event capture at every hop. Every move — plant outbound to Tier 1, Tier 1 intake, Tier 1 outbound loaded, plant intake, plant outbound empty to Tier 1, scrap/retire — generates an event. Events come from the Shipsy driver app, WMS scan, or integration with Tier 1 systems.
Loop-level dashboards. For each container type × corridor, a dashboard shows fleet size, current location distribution, transit time profile, and leakage rate. Outliers surface automatically.
Supplier RPM scorecards. Each Tier 1 has a scorecard showing returns on time, damage rate, and leakage. Nexa ties the scorecard into financial reconciliation — RPM deposit refunds, replacement charges, and any contractual incentives.
Inter-loop visibility for OEM planners. When container shortages threaten upstream plant feeds, Atlas alerts planners with current fleet status, positions of containers that could be expedited back, and recommended actions.
The operating stack: before and after
| RPM dimension | Untracked fleet | Shipsy RPM module |
|---|---|---|
| Container identity | None, type-only | Per-container unique ID |
| Movement events | Manual shipping/receiving records | Automated scan at each hop |
| Position visibility | Unknown between hops | Live location/state per container |
| Leakage detection | Annual physical audit | Continuous via dashboard |
| Supplier accountability | Quarterly meetings | Live scorecard with financial tie-in |
| Return sequencing | First-in-first-out by guess | Prioritized by plant demand |
| Financial settlement | Manual reconciliation | Nexa automated against RPM deposits |
| Plant line-feed risk alerts | Reactive | Predictive via Atlas |
The case study pattern: RPM in alco-bev extends directly
Shipsy’s RPM capabilities were proven at commercial scale in beverage distribution — a global alco-bev leader operating across 70+ countries uses Shipsy’s RPM automation for kegs and crates in primary and secondary distribution loops. The mechanism (container identity, event capture at every hop, loop dashboards, supplier accountability) maps directly onto automotive bins, racks, and dunnage. Automotive RPM loops are typically simpler in geographic scope (plant-to-Tier-1 corridors) but more complex in container type diversity.
Integration with inbound orchestration
RPM doesn’t live in isolation. It’s tightly coupled with inbound supplier-to-plant flows — the milk-run that delivers loaded containers to plant is the same milk-run (typically reverse leg) that returns empties to Tier 1. Shipsy’s TMS plans the round trip as a single economic unit, not as two separate flows, so empty-leg utilization goes up and inbound freight cost per loaded container comes down.
- Astra plans round-trip milk-runs with loaded-in/empty-out sequencing
- Atlas tracks both legs; alerts when empty return threatens Tier 1 next cycle
- Nexa settles freight AND RPM-deposit reconciliation on the same invoice flow
- Vera disputes carrier damage claims autonomously on categories with pre-approved playbooks
Commercial implications
Three things change when RPM runs on a live platform instead of on spreadsheets:
- Fleet size shrinks. Visibility lets OEMs run the loop on fewer containers because idle inventory in the network reduces.
- Capex spend drops. Fewer container replacements because leakage is identified and addressed.
- Supplier relationships improve. Scorecards turn a recurring friction into an objective conversation; the good suppliers perform visibly and benefit commercially.
See the automotive inbound supplier-to-plant guide for the connected inbound flow, the TMS product page for RPM capabilities, and a Heineken beverage distribution case study for the commercial-scale proof point of RPM loop automation on Shipsy.