Karrio

- (fix) DPDHL tracking response parsing caused by inconsistent `leitcode` with the schema type
- (improve) DPDHL error parser (368)
- (remove) deprecated field on custom carrier service admin form

What's new

- (add) `GEODIS` tracking carrier integration
- (add) `La Poste` tracking carrier integration
- (add) `Boxknight` carrier integration
- (add) `Roadie` carrier integration
- (add) `Nationex` carrier integration
- (introduce) carrier connection default configuration
- (improve) order `db` query adding a direct relationship with shipments
- (improve) migrations for large datasets
- (add) exception-related shipment status mapping between trackers and shipments.
- (introduce) label preview for ZPL using `labelary` API
- (improve) DHL Express support for EU


Bug Fixes

- (fix) tracking info property typo

Fixes

- (fix) DHL support for EU rating and label creation
- (fix) customs partial update mutation
- (add) support for HTML response parsing and update DPDHL error parsing to process HTML responses
- (fix) tracker info data merging

Fixes

- (fix) UPS ETD integration


Thanks, jacobshilitz for the patch

What's New

- (add) DPD carrier integration `carrier-integration`
- (enhance) static service level definition with support for zones
- (introduce) unified tracking statuses
- (enrich) tracking details with package and shipment info
- (add) `street_number` field to `Address` model
- (add) `carrier_tracking_link` to `shipment.meta`

"meta": {
"carrier_tracking_link": "https://www.fedex.com/fedextrack/?trknbr=794622728852",
"tracking_numbers": [
"794622728852"
],
"ext": "fedex",
"carrier": "fedex",
"service_name": "FEDEX INTERNATIONAL ECONOMY",
"rate_provider": "fedex"
},

- (enrich) tracker details with :

{
"tracking_number": "string",
"carrier_name": "amazon_mws",
"account_number": "string",
"reference": "string",
"info": {
"carrier_tracking_link": "string",
"customer_name": "string",
"expected_delivery": "string",
"note": "string",
"order_date": "string",
"order_id": "string",
"package_weight": "string",
"package_weight_unit": "string",
"shipment_package_count": "string",
"shipment_pickup_date": "string",
"shipment_delivery_date": "string",
"shipment_service": "string",
"shipment_origin_country": "string",
"shipment_origin_postal_code": "string",
"shipment_destication_country": "string",
"shipment_destination_postal_code": "string",
"shipping_date": "string",
"signed_by": "string",
"source": "string"
}
}

_Note that you can override all the info fields using `POST /v1/trackers` and `PUT /v1/trackers/{tracker_id}`_
- (add) `latitude` and `longitude` to the `TrackingEvent` model for future use with last-mile carriers and automatic background updates by Karrio.

Fixes

- (revert) to FedEx single call ETD implementation
- (invalid) mapping of the `Suburb` field on the `DHL Express Rate` request
- (fix) incoherent UPS service names

Changes

- (deprecating) `DELETE /v1/orders/{order_id}` in favor of `POST /v1/orders/{order_id}/cancel`
- (change) tracking request details at the SDK level.
- Introduce `account_number` and `reference`
- Remove `level_of_details` and `language`
- (renamed) UPS services to be region aware (`This will require draft shipments rates to be refreshed`)

Changes

- (fix) regression on one call label generation webhooks trigger
- (fix) background data archiving on multi-tenant deployments
- (fix) UPS rate fetch inconsistent transit details
- (improve) DPDHL requests mapping
- (update) DPDHL connection settings to correct the authentication problem
- (raise) error when creating trackers if tracking fails by default.
And create `tracker` despite errors when `pending_pickup` flag is specified
- (improvement) of Sendle tracking details


Special thanks to DanielOaks for the Sendle tracking API update.