Single API, multiple alternatives. A vision of how an API can change e-commerce logistics

In "Single API, multiple alternatives. A vision of how an API can change e-commerce logistics" I’m going to show you a little bit about the challenges, that customers, shop managers and developers are facing and how startups, especially their APIs are changing the way we’re approaching those problems.

Transcript

1. Single API, multiple alternatives. A vision of how an API can change e-commerce logistics 04/25/2015 APIDays Berlin / APIStrat Europe 2015
2. André Cedik Co-Founder & Growth Hacker shipcloud.io @andrecedik
3. Problems
4. Problems „The carriers tracking page says my package was delivered, but not who the signee was. Where is my order?” „More often than not, I only get a pickup note than receiving my package.“ „I don't have the choice which carrier will be used.“ „If I could tell the carrier when to bring me my package I'd order online more often.“ „<Carrier X> parcel shop is just around the corner. Why doesn't <online shop Y> send packages there?“
5. Stores
6. Developers
7. API-Documentation DHL (only express): 50 Pages DPD (only Paketschein): 101 Pages Fedex: 598 Pages GLS (UNI-Ship TechDocs): 21 Pages GLS (Web Service - Track&Trace): 15 Pages Hermes (ProPS_v1): 43 Pages UPS (WebServices): 483 Pages Developers
8. Solutions
9. Solutions
10. Solutions
11. Visions
12. Visions
13. Visions
14. André Cedik developers@shipcloud.io @shipcloud_devs Thank You!