Rate Card Pricing: From Cost Pools to Per-Unit Rates

The rate card is the commercial face of your warehouse cost model. It's what the customer sees, what they compare against competitors, and what they'll hold you to for the life of the contract. This guide explains how per-unit rates are derived from underlying cost pools.

What a Rate Card Actually Is

A warehouse rate card is a schedule of per-unit prices for every billable activity the 3PL performs. Receiving a pallet, picking a carton, packing an order, loading a container — each activity has a rate expressed as dollars per unit.

The customer uses the rate card to forecast their logistics spend. If they expect to ship 245,000 cartons next year and the pick rate is $1.40, they know the picking line will cost them $343,000. The rate card makes warehouse costs predictable and comparable.

But the rate itself isn't plucked from thin air or benchmarked from a competitor's proposal. It's the end result of a calculation chain that starts with volumes and works through FTE modelling, cost allocation, and margin application.

Rate Types

Not every rate card line works the same way. There are three common rate types in Australian 3PL contracts, each with a different relationship to the underlying cost pools.

Activity rates are the most common and the most complex. They absorb a proportional share of every cost pool based on how much labour the activity consumes. Storage rates are typically simpler because they're driven by space costs rather than labour. Management fees cover the salaried workforce and are often expressed as a flat monthly charge rather than a per-unit rate.

The Rate Calculation Chain

Each activity-type rate card line goes through a specific calculation sequence. Understanding this sequence is key to understanding why your rates are what they are.

The critical input is the FTE calculation from step 1. The FTE percentage determines how much of the Activity cost pool (which is typically 60-70% of total warehouse cost) gets allocated to each rate card line. A small error in FTE calculation ripples through every rate.

Worked Example: Building a Complete Rate Card

Let's build a simplified rate card for a warehouse with five billable activities. We'll start with the cost pools and work through to final rates.

Notice how the overhead allocation creates a floor under every rate. Even if an activity uses minimal labour (like putaway at 10% FTE), it still absorbs one-fifth of the fixed overhead, salary overhead, and IT pools. This means low-volume activities tend to have higher per-unit rates because the overhead is spread across fewer units.

Volume Sensitivity

Rate card rates are inversely related to volume for the overhead components. The Activity cost component scales with volume (more volume means more FTEs means more cost), but the overhead components are fixed. Double the volume and the overhead-per-unit halves.

This is why 3PL contracts often include volume bands or minimum volume guarantees. The rate card rate is valid within a specified volume range. Below the minimum, a different (higher) rate applies, or a fixed fee kicks in to protect overhead recovery.

Margin Application

The rates calculated above are cost rates. They cover expenses but include no profit. Corporate overhead and margin are applied on top of the total cost base before dividing by volume to get the final customer-facing rate.

With 3% corporate overhead and 12% margin, the markup factor is 1.15. A cost rate of $1.40 becomes a customer rate of $1.61. This markup is typically applied uniformly across all rate card lines so that every activity carries the same margin percentage.

Annual Cost Verification

Once rates are set, you can verify the total annual revenue by multiplying each rate by its volume and summing across all lines. This total should reconcile back to the total warehouse budget (base cost + overhead + margin).

If they don't match, there's a calculation error somewhere in the chain. This reconciliation is the single most important quality check in warehouse cost modelling. In a spreadsheet, it's often the check that catches broken formulas before a tender goes out.

Rate Card Presentation

The customer-facing rate card strips away the allocation detail and presents clean per-unit rates. But the underlying model should be available for audit. A good rate card presentation includes the rate, the unit of measure, the annual volume assumption, and the annual cost at that volume.

Common Pricing Pitfalls

Overhead dilution on high-volume lines. A carton pick line with 245,000 units absorbs the same overhead as a container load line with 7,800 units. The overhead per carton is trivial ($0.61), but per container it's significant ($19.14). Customers often compare your pick rate without realising that low-volume activities subsidise high-volume ones.

Rate card lines that don't reconcile. If the sum of (rate x volume) across all lines doesn't match the total warehouse budget, something is broken. This should be checked every time any input changes.

Stale rates after volume changes. When a customer updates their volume forecast mid-contract, the rate card should be recalculated. New volumes change FTE requirements, which change FTE percentages, which change ABC allocations, which change rates. Leaving old rates in place while volumes have changed guarantees either over-recovery or under-recovery.

No volume bands. A single rate with no volume protection means you absorb all the risk if volumes drop. Include minimum volume thresholds or tiered rate structures in the contract terms alongside the rate card.

The Full Picture

The rate card is the last step in a chain that starts with customer volumes. Every article in this series covers a piece of that chain: FTE calculation translates volumes into labour requirements, ABC allocation distributes costs into pools, and this article shows how pools become rates. For multi-site contracts, the same chain runs independently at each site with consolidated reporting at the contract level.

When all of these steps are connected and automated, changing a single volume input recalculates the entire model in seconds. That's the difference between spending three weeks on a tender response and spending three days.