Private fleet on Freight: when standard certification isn't the right path.

Shipper certification

Private fleet on Freight: when standard certification isn't the right path.

Not every shipper relationship fits the standard four-packet, four-gate intake. Private-fleet, dedicated-capacity, and capacity-partner relationships are structurally different — and Freight separates them out instead of papering over the difference.

48BY40 Freight Editorial3 min

Not every shipper relationship fits one mold. Standard shipper certification on Freight — relationship, four document packets, quote-approved, execution-approved — is built around the shape of tendered freight: per-load decisions, lane-by-lane matching, transaction-level commercial structure. That shape works for most shipper teams. It doesn't work for all of them.

Private-fleet operations, dedicated capacity, and capacity-partner relationships are structurally different. Treating them as standard intake either flattens what makes them distinct or papers over commercial structure the standard path doesn't carry. Freight separates them out instead.

What makes private-fleet relationships distinct

A standard shipper tenders loads into a network and lets the system route them. A private-fleet operator runs their own equipment, drivers, and routes — often integrated with their own facilities and inventory flow. The commercial logic is different. The operating logic is different. The accountability surface is different.

Dedicated capacity is the same problem in a different shape: a carrier commits specific equipment and drivers to a specific shipper for an extended period, often on specific lanes. The relationship isn't per-load; it's per-arrangement. Capacity-partner relationships go further — long-term commitments, often with shared operations, sometimes with joint accountability.

In every case, the commercial structure that makes the relationship work is not the standard per-load framework. The Operations packet that captures lane portfolio assumes lanes get tendered; private-fleet lanes are operated, not tendered. The Commercial packet that captures trade terms assumes transactional pricing; dedicated capacity is committed capacity. The Treasury-Billing packet that captures per-load invoicing assumes per-load invoices; capacity-partner economics often run on different cadences entirely.

Pushing these relationships through the standard four-packet review doesn't fit. The shapes don't match.

The structured-capacity path

Freight's response is a separate intake: the structured-capacity path. It is not standard certification with private-fleet exceptions bolted on. It is a different conversation, with its own contract framework, its own review logic, and its own commercial structure.

What that means in practice: a shipper or carrier entering with a private-fleet, dedicated-capacity, or capacity-partner posture doesn't run through the standard relationship → certification → quote-approved → execution-approved gates. They start with a structured-capacity conversation that establishes the commercial framework first — what capacity is committed, on what lanes, on what cadence, under what shared operating posture, with what governance.

The review work still happens. The discipline that standard certification carries — explicit agreements, documented expectations, governance baked in — applies to structured capacity too. But the shape is different, and Freight builds the intake around the shape, not the other way around.

When a shipper should use the structured-capacity branch

If your loads come out of a tendering process and move through a network, standard certification is the right path. The four packets are built for you.

If you operate your own fleet — your own trucks, drivers, routes — and want Freight to integrate with that operation rather than replace it, the structured-capacity branch is the right path.

If you're committing dedicated capacity to a specific shipper or relationship, the structured-capacity branch is the right path.

If you and a counterparty are building a capacity-partner arrangement that runs on its own commercial logic — committed volume, committed capacity, shared operating posture — the structured-capacity branch is the right path.

The standard path isn't being protected from these relationships. The structured-capacity path is being protected for them. Different commercial structures need different intake structures. Forcing them into one shape is exactly the kind of compression that produces the wrong-shape relationships freight networks routinely live with.

What this changes commercially

For shipper teams whose freight runs through tendered relationships, nothing changes — the standard path is intact and built for that work.

For shipper teams whose freight runs through private-fleet or dedicated-capacity arrangements, the structured-capacity branch means the commercial framework gets established once, explicitly, before execution rather than improvised on top of an intake form that wasn't designed for the relationship. The agreements are clearer. The expectations are documented. The operating posture is mutually known.

Different paths. Same discipline. The right intake for the relationship being built.

What's next

Two paths. Pick yours.

Tell us how you move freight. We route you to the right intake.

For shippers

I'm a shipper.

You move freight and want it under certified conditions. Start the relationship — Legal, Commercial, Treasury-Billing, Operations packets reviewed before quoting and execution rely on it.

For carriers

I'm a carrier.

You move freight for shippers. Qualification runs on 48BY40.io. Get qualified there; your standing then governs every tender that reaches you. Freight does not accept direct carrier signup.