DHL
Shipping · 37% complete
Stage Checklist
- ✓ Research (.md file)
- ✓ POC App
- ✓ POC UI (templates)
- ✗ Microservice
- ✗ Containerized (Dockerfile)
- ✗ Helm Chart
- ✗ CI/CD Pipeline
- ✗ Frontend Page
AI Research
Refund Rules
Not yet researched
Credit Policies
Not yet researched
Contractual Terms
Not yet researched
Integration Complexity
Not rated
Technical Notes
Based on DHL's comprehensive API ecosystem and business model, here's the contract and billing analysis: ```json { "refund_rules": "DHL offers limited refunds primarily for service failures (delivery delays, damage) and billing errors. Unused shipping labels can typically be refunded within 30 days if not used. Express division offers money-back guarantees for time-definite services if delivery commitments are missed. Freight services may offer partial refunds for undelivered portions. Credit adjustments for overcharges are processed within 30-60 days. No refunds for partially used contracted rates or committed volumes.", "credit_policies": "DHL provides service failure credits automatically for Express time-definite services that miss delivery commitments. Credits issued for proven damage claims, lost shipments, and billing errors. Volume-based customers receive credits for downtime affecting tracking/booking systems exceeding SLA thresholds. Freight division offers credits for delayed deliveries beyond committed transit times. Credits typically applied to next invoice cycle or customer account balance.", "contractual_terms": "Enterprise contracts typically include 12-month auto-renewal with 90-day cancellation notice. Price increases limited to annual adjustments with 60-90 day notice. Volume commitments often required for contracted rates with penalties for under-performance. Liability caps standard across divisions. Integration and API access tied to minimum volume/revenue commitments. Fuel surcharges and regulatory fees excluded from price protection clauses.", "integration_complexity": 4, "technical_notes": "OAuth 2.0 authentication across most APIs with varying token lifetimes (15-60 min). Rate limits vary by division (5 req/sec for eCommerce, higher for Express). Multiple API versions and protocols (REST primary, some SOAP/XML legacy). Division-specific endpoints require separate integrations. Complex data models vary by service type. Webhook support limited to specific divisions. Sandbox environments require separate credentials. Documentation quality varies significantly between divisions." } ```