Search for container M&R software and you will find workshop tools, estimate templates, and CMMS-style checklists. Depot operators need something narrower and harder: repair status that actually changes whether an empty can leave — on the same timeline as gate, yard holds, and billing.
If estimates live in email, approvals in WhatsApp, and “available” still shows damaged units in stock, you do not have M&R software. You have another inbox.
Who this is for
- Depot-linked M&R supervisors and ops managers at physical empty or mixed yards (~200–5,000 TEU)
- Independent empty depots whose repair shop sits next to the stack
- Multi-line programmes where customers need repair visibility without a phone tree
Less of a fit: pure third-party workshops with no yard inventory truth to protect — unless you still need unit-level holds and client visibility against a depot you serve.
Not freight TMS. Not a marine TOS. This is M&R as part of depot / yard ops, not a standalone factory CMMS story.
Operator pains
Estimates / approvals that don’t block dispatch
A unit can sit “in repair” on a whiteboard while the inventory tab still says Available. The truck gets staged; the line gets an apology; the hold existed only in someone’s head.
Photo / estimate threads outside the unit timeline
Damage photos in chat, estimate versions in email, approval buried in a CC chain — three weeks later you cannot reconstruct who agreed to what. Dispute-ready M&R needs evidence on the unit record, next to the digital EIR from gate management software for depots.
“Available” empties that are still in repair
Portal and booking teams sell fantasy stock when repair state does not update holds and availability. Yard picks then dig damaged neighbors. Positions and holds belong in container yard management software that reads M&R state.
Line / client asking for repair status the portal can’t show
Carriers and leasing customers call for estimate status, approval state, and ETA back to sellable empty. If the portal cannot answer, every repair becomes a desk ticket.
Billing repair vs storage vs handling from different truths
Repair invoices from one spreadsheet, storage clocks from another, handling from a third — finance and ops reconcile by argument. Event-tied billing needs M&R completion and gate events on one spine (container depot management software).
Soft check: if damaged empties still pollute “available” while estimate threads live in email, walk inspection → hold → M&R → release on containerhub.ai or see pricing.
What M&R software must include
Inspection → estimate → approval → work order → complete on one unit
- IICL-oriented coding where your process requires it
- Photos and estimate lines bound to the same container history as Gate In
- Clear approval state (pending / approved / rejected) visible to ops and, when enabled, the client
- Work order status that operators trust without a side spreadsheet
Holds / availability updates when repair state changes
- Damage or open repair places a hold that blocks Gate Out and “available” counts
- Completion / release returns the unit to sellable empty (or correct grade) without a manual inventory edit
- No path where the portal sells a unit the yard cannot pick
IICL-oriented coding where process requires it
Coding standards and criteria your lines expect — not a free-text damage novel that nobody can bill against.
Visibility in the client portal
- Estimate packs and repair status self-serve when you enable them
- Same truth as the workshop desk — not a nightly export
- Fewer “send me the estimate” loops
Hand-off to depot billing
- Repair charges traceable to the work order and unit
- Storage / handling still explainable from gate and dwell events
- One audit trail when a line disputes both repair and free days
How M&R fits the depot spine
Think flow, not a workshop silo:
Gate In → digital EIR / inspection → hold if damaged → estimate → approval → work order → complete → hold lift → available empty → Gate Out
M&R that does not sit on that spine creates night-shift reconciliation. Empty-depot context: empty container depot software. For the shop-floor side of the same flow, see container repair workflow best practices.
Vendor eval checklist
Bring the same script to every demo — including ContainerHub:
- Damage path: Photo → IICL-style code → hold → estimate — without leaving the unit record?
- Approval: Can a line approve in-portal (or via a controlled link) and does status update availability?
- Hold enforcement: While repair is open, can anyone still stage the unit for Gate Out?
- Portal: Can the client see repair status within minutes of an ops update?
- Billing: Trace a repair line item and a storage charge to the same unit timeline
- Category fit: Depot-linked M&R on a yard OS — not a generic CMMS or freight TMS bolted on
Score capability and fit, not feature lists. If a vendor's module depth is unclear, ask them to show it on one of your own units.
Where ContainerHub fits
ContainerHub includes M&R as part of depot/yard ops SaaS for physical empty-container facilities (~200–5,000 TEU): gate, digital EIR, IICL inspections, M&R, yard positions/holds, billing, client portal, and AI Jarvis — on one data model.
It is not freight TMS. It is not a marine TOS.
Jarvis can help operators query blocked / in-repair units and prepare supported actions — with human approval before live records change.
Soft next step
- Map your path: inspection → hold → estimate → approval → release → available empty
- Compare published plans on pricing
- Request a demo with a real damage → M&R → gate-out scenario from your site
Explore ContainerHub · Pricing
Related reading: Container depot management software · Container yard management software · Gate management software for depots · Container repair workflow best practices
