Some shippers want their past shipments priced; others want a rate table. Here's how to tell the difference and answer each well.
Price my history vs give me a rate table
- Price my history: the shipper sends past shipments with origins, destinations, weights and pallets, and wants back what they would have paid you.
- Give me a rate table: the shipper sends lanes, sometimes only sales or case data, and wants back pallet or weight bracket tables they can use themselves.
The trouble is that many files sit in between: historical shipments with missing weights or pallets, or sales data that isn't shipment data at all.
Make your assumptions explicit
When data is missing, the best answer is a clear, stated assumption, such as "1,500 lb per pallet". It keeps your pricing honest and makes the proposal easy to defend.
How KnowRFP handles both
KnowRFP reads whatever the shipper sends, tells you what's missing, and lets you add assumptions in plain English. Then it either prices their shipments or builds bracket tables, priced against your contracts through your TMS API, and returns them in your format or theirs.
See how KnowRFP does it: KnowRFP
