14
Single API, multiple alternatives. A vision of how an API can change e-commerce logistics 04/25/2015 APIDays Berlin / APIStrat Europe 2015
| Date post: | 29-Jul-2015 |
| Category: |
Technology |
| Upload: | andre-cedik |
| View: | 43 times |
| Download: | 3 times |
Single API, multiple alternatives. A vision of how an API can change e-commerce logistics
04/25/2015 APIDays Berlin / APIStrat Europe 2015
André CedikCo-Founder & Growth Hacker shipcloud.io
@andrecedik
Problems
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?“
Stores
Developers
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
Solutions
Solutions
Solutions
Visions
Visions
Visions
![Outline Logistics Review Rule Evaluation Robust & Efficient Execution [paper 6.2] –Representing Local Completenes –Computing informational alternatives.](https://static.documents.pub/doc/80x56/56649f1f5503460f94c36c41/outline-logistics-review-rule-evaluation-robust-efficient-execution-paper.jpg)
