|
|
|
|
|
by chrissnell
3626 days ago
|
|
What's the value proposition here, besides multiple carrier availability? I was able to create multi-piece shipment labels with the FedEx API in 1999. The API was stupid-simple and easily implemented in Perl back then. Are you offering volume discounts even when that volume is split amongst a host of carriers? I never saw the point in using multiple vendors as a small-/medium-sized shipper. It was easier to stick with one and have only one set of shipper-provided supplies to worry about. |
|
The developer documentation for UPS is thousands of pages long. The document explaining how to quote a domestic shipment is over 600. I don't have them in front of me right now, but FedEx is the same. You can't even integrate directly with USPS anymore. You have to go through someone like Stamps.com, Endicia (which are now one and the same), etc.
We only ship 200-300 packages daily, but there are benefits in using multiple carriers. For one, small lightweight and low-value packages always go USPS. Flat rate boxes are free and easy to use. Between the two big private guys, using multiple carriers gives you a negotiating advantage. Our reps probably visit us twice a month to try and keep on our good side.
Our ERP can calculate the best value and delivery time for a given order. For example, taking advantage of the FedEx Express OneRate program for a given package might a) reduce our net cost because the boxes are provided to us for free and b) get there 2-3 days faster for a buck more versus UPS Ground. And we can pack 50 pounds into that Express box under the OneRate program.
Stocking supplies isn't too terribly hard. We probably have 20 box sizes we use, plus FedEx and UPS small/medium/large vendor-supplied boxes and a few USPS sizes. Takes up a surprisingly small amount of space.