I confess I don't totally understand shippo; in the event that you are a business of the size where multiple-carrier headaches are coming into play, aren't you also of the size where you need a proper order management, inventory management, and warehouse management system? And those systems tend to have address validation, shipping integration, label creation, etc. as built-in features. I don't know why I'd roll my own versions of that stuff on top of their API layer.<p>It's definitely a valuable API, but I'd be more likely to take advantage of it if I were a new SaaS company building logistics software -- Shippo would be a great shortcut to get to market with the aforementioned features. At that point I'd be capturing more value in the form of my LoB software than Shippo could ever capture in their (essentially) cost+ pricing model.<p>I don't get it -- but I feel like that's my fault and I'm missing the market, so maybe someone can enlighten me.<p>Edit: Also this was an interesting read and clever solution to a tricky migration problem!