Some loops run on containers the customer owns. That changes who pays for replacements, who maintains them, who is responsible when one fails, and what happens at the end of the relationship. Where a fleet contains both owned and customer-owned containers, the two need to be distinguishable and the responsibilities need to be written down, because they are otherwise negotiated case by case.
What changes when the customer owns them
You do not buy them, so you do not have a replacement budget for them. You do not decide the specification, so you cannot improve them. You are responsible for handling them carefully, because they belong to somebody else, and you are usually responsible for returning them. And when one is damaged in your care, the question of who pays has to have an answer in advance.
Distinguishing them in service
Two similar container types in one loop get mixed, and then the ownership question becomes unanswerable. A clear, durable, visible mark of ownership solves it, and it has to survive the same handling the container does. Where mixed fleets run, this is the single most important thing to get right and it is a marking decision rather than a logistics one.
Damage responsibility
The usual arrangement is that the holder is responsible for damage occurring while the containers are in their care, with normal wear excluded. That distinction – damage versus wear – needs a definition, because every borderline case will otherwise be argued. A retirement criterion applied consistently, as described in writing a retirement criterion, gives a defensible line.
Loss responsibility
Containers lost while in your care are usually chargeable, and the rate at which they are charged should be in the agreement. Where it is not, the charge is negotiated after the fact and it is usually higher than an agreed rate would have been. Where a loop runs on customer-owned containers, the loss rate and the charge are worth agreeing early.
Who maintains them
Either the owner or the holder, and it needs saying. Where the holder maintains them, the repair cost is a chargeable item or an absorbed one, and that needs saying too. Where nobody is assigned, containers degrade in service and the argument starts when a load is damaged.
What happens at the end
Containers held at the end of a relationship have to be returned, and the count has to reconcile. Where a loop has been running for years without a reconciliation, the final count is often a surprise and the conversation is expensive. A periodic count, as described in counting a container fleet, prevents that.
Mixing specifications
Customer-owned containers may not match yours in footprint or stacking geometry, which means they may not interstack or may not run on your equipment. Where a loop uses both, checking compatibility before the containers arrive prevents a problem that otherwise persists for the life of the relationship.
What to do when the two fleets must interstack
Where owned and customer-owned containers have to stack together, the stacking geometry has to be checked with actual samples from both fleets before the arrangement starts. A difference of a few millimetres in a seating feature is enough to make a mixed stack unstable, and it is far easier to resolve with a sample on a bench than with a loaded stack that has just fallen over.
Where the geometries genuinely cannot be reconciled, segregating by lane is usually simpler than trying to make the two work together. Marking both fleets clearly, and keeping them on separate routes, costs less in the long run than a mixed fleet that stacks badly.
What to put in the agreement
Ownership, marking, damage responsibility with a definition, loss rate and charge, maintenance responsibility, and the return arrangement at the end. Six clauses, and every one of them is cheap to agree at the start and expensive to argue later.