...
ediStatus | Comment |
---|---|
ATTEMPTING_EXPORT | We are attempting to forward the bookingdata/edi to the carrier/company responsible to perform the delivery. For the majority this will take seconds, but can take up to 2 hours (depending on carrier, availability and so on) Action: None, everything is normal with this status. |
EXPORT_OK | The bookingdata/edi is registered with the carrier/company responsible to perform the delivery, and the registration was successful. Action: None, everything is normal with this status. |
EXPORT_FAILED_WILL_RETRY | We have attempted to forward the bookingdata/edi to the carrier/company responsible to perform the delivery, but the carrier was not able to receive it at the time. The bookingdata/edi will receive this status when the service the carrier have is unavailable. Most likely the unavailability is short, and the bookingdata/edi will be registered shortly. Action: No action needed yet. The system will automatically retry registration of the bookingdata/edi. This can take up to 5 hours. |
EXPORT_FAILED_PERMANENTLY | We have attempted to forward the bookingdata/edi to the carrier/company responsible to perform the delivery, but the carrier was not able to receive it. The bookingdata/edi will receive this status when the service the carrier have is unavailable over a long periode of time or the request in invalid (missing mandatory data, invalid values and so on) Action: With no action this bookingdata/edi will not be registered with the carrier. Based on the type of booking we suggest the following actions
|
CANCELLED (WIP) | The shipment has been cancelled and will not be picked up |
PASSIVE_RETURN (WIP) | The shipment has been registered, but not yet activated. Use the Parcel Activate Order API to set a date for the pickup. |
...