What’s new?
We’re excited to introduce a new feature that gives you greater control over what happens when a customer is absent at the time of delivery.
With the new undeliverable_actions
object in the job creation payload, you can now decide, on a per order basis, whether a package should be returned or discarded if it is undeliverable.
What’s the impact?
This new feature gives you more granular control over the operational flow of each individual package by allowing you to tailor fallback actions per delivery.
- For example, if the end-customer is absent, you might choose to return a high-value package or discard a low-value one, depending on what makes the most sense for you.
How does it work?
When creating a job, you can now include the undeliverable_actions
object within the delivery_options
object, defining the fallback action and provide any necessary instructions.
The undeliverable_actions
object contains two mandatory fields:
- The
action_type
field (return
ordiscard
) indicates what should happen if the customer is absent. - The
instructions
field allows you to provide additional context or instructions to the courier.
Example usage:
"delivery_options": {
"undeliverable_actions": {
"action_type": "return",
"instructions": "Please return the package to its pickup location."
}
}
Or:
"delivery_options": {
"undeliverable_actions": {
"action_type": "discard",
"instructions": "Please discard the package in case of customer absence"
}
}
Example implementation:
We recommend automating the use of this field in your order management system. For example, you might configure it so that orders above a certain value or containing specific items are mapped to undeliverable_actions
of type return
, while lower-value or perishable orders default to discard
.
When will this change take place?
This feature is already live and available for use.
What’s next?
Subscribe to Announcement notifications to receive timely updates on new features and enhancements!