Parcel life cycle for cross-dock

What means parcel life cycle for cross-dock?

It is the parcel states flow when the selected shipping type has same day or next day modality.

This type of delivery process can follow several routes to reach the final destination (either the recipient or a return to the sender). One route involves transporting from the sender to the warehouse, another from the warehouse to the recipient, and a third from the warehouse back to the sender in the case of a return.

From sender to warehouse

In this slice of the flow the parcel is carried from the sender to the warehouse, and the states where the parcel goes through are:

• ready: Requester creates the parcel in or system.
• readytopickup: Requester request the deliver of parcel(s) selecting the shipping type with ame day or next day modality.
• receivedonfinalhub: The warehouse operations team receives the parcel in the warehouse.

From warehouse to recipient

In this slice of the flow the parcel is carried from the warehouse to the recipient.

The first part are the states involved in the sorting parcels and creating last mile delivery routes:

• readytodispatch: The warehouse operations team sorts the parcels and set them ready to be dispatched.
• qualifiedforpickup: The parcel has been assigned to a last mile delivery route.

When the driver has a route assigned and starts the last mile delivery:

• pickingup: The driver is picking up the parcel.
• intransit: The route of last mile delivery where the parcel is, is in progress.
• onroutetodelivery: The parcel is the next delivery in the last mile delivery route.
• delivering: The driver is in the drop-off location delivering the parcel.

At this point the parcel can be delivered to the recipient:

• delivered: The parcel has been delivered to the recipient.
  • This states has a proof of delivery based on requester configuration

Or for a set of reasons the parcel could not be delivered to the recipient:

• undelivered: The parcel could not be delivered to the recipient, this state has several substates with the reason:
  • recipient not found.
  • rejected by recipient.
  • wrong address.
  • unsafe delivery zone.
  • invalid proof.
  • other.

Afer a undelivered state can happens two scenarios

• The parcel is delivered to the recipient at the second attempt without retuning to warehouse.

  • intransit: The driver put the parcel in the route to deliver to the recipient.
  • onroutetodelivery: The parcel is the next delivery in the last mile delivery route.
  • delivering: The driver is in the drop-off location delivering the parcel.
  • delivered: The parcel has been delivered to the recipient.

Note that the delivery attempt could be repeated many times after returning to warehouse so the flow intransit -> onroutetodelivery -> delivering -> undelivered could be repeated many times.

• The parcel is returned to the warehouse.

  • onroutetoreturn: The driver is in the route to return the parcel to the warehouse.
  • returning: The driver is in the warehouse returning the parcel.
  • receivedonfinalhub: The warehouse operations team receives the parcel in the warehouse.

After returning to the warehouse the parcel can be delivered again in a new route so we start the process again from the readytodispatch state.

From warehouse to sender

If the parcel could not be delivered to the recipient the parcel is returned to the sender stating from the receivedonfinalhub state.

• onroutetoreturn: The driver is in the route to return the parcel to the sender.
• returning: The driver is in the parcel pick-up location returning the parcel to the sender.
• returned: The parcel has been returned to the sender.

Final states

• delivered: The parcel has been delivered to the recipient.
• returned: The parcel has been returned to the sender.
• incident: The parcel has been involved in an incident (this state has several substates with the reason).
  • payment_method_declined: There is a problem with your payment method, and the delivery has not been accepted. Check your payment methods in the business web
  • no_payment_methods: There is no payment method configured. Check your payment methods in the business web
    requester_no_found_or_unauthorized: The requester sent in this request is not valid.
  • invalid_pick_up_location: There is no fleet available for your delivery area, or it's not properly configured. Please get in touch with the Logistics Team to check if we can cover your delivery area.
  • delivery_already_exists: This parcel has been delivered already.
  • unknown: Something has happened but, unfortunately, we haven't detected the reason. If the problem persists, please get in touch with the Logistics Team.