Availability Checks
Transporter availability in more detail
Through our transporter integrations, we can verify which transport methods can deliver to the desired destination address. Depending on the transporter, this may also include an indication of the delivery time.
Supported Transporters
| Transporter | Service availability | Time interval | Supported countries |
|---|---|---|---|
instabox | ✓ | ✓ | SE, DK, FI |
postnord | ✓ | ✓ | SE |
budbee | ✓ | ✓ | SE, DK, FI |
Early Bird | ✓ | ✓ | SE |
airmee | ✓ | ✓ | SE |
bring | ✓ | ✓ | SE, NO |
DB Schenker | ✓ | ✓ | SE |
posti | ✓ | SE, FI | |
DHL | ✓ | ✓ | SE |
RetailerTransporter | configured | configured | Worldwide |
Are you using your own stores as pick-up points? Please see Click & Collect to see how we handle it!
Using Fallback Delivery Times
Skrym applies fallback values for delivery time if:
- You configure a preference to use fallback values instead of the transporter's estimation. See preferences.
- The transporter does not return a delivery time but confirms the address is valid.
In the case of using fallback delivery times, Skrym returns:
- No delivery times: if both fallback times are missing or invalid.
- Single delivery time: if only one fallback time is valid.
- Both delivery times: if both fallback times are valid.
InfoIf Skrym is unable to validate the delivery address, the transport method will not be shown at all unless specifically configured to disregard the availability check. This is to prevent showing methods that are actually unavailable.
Data Requirements
To use the availability function successfully, the following data is required:
| Data | Explanation |
|---|---|
Credentials | Almost all transporters require some form of authentication for us to call their availability API. This can be set up on the transporter page in Scope |
Enabled | For Skrym to run any checks at all, the methods need to be enabled in Scope |