I've been told writing down our use case for this helps with prioritization so here's why we need that field:

We have an SLA with our shipping providers and as well promise we try to keep to our customers that their orders will be delivered within N business days. Due to the volume of packages we ship, we can't check every single delivery every day.

We use the `shipment_status` value to check what's the current status of the package - together with the fulfillment date, we can calculate how long it's been in transit for, if there's an issue with the delivery, if our shipping partners are breaking the SLA, etc. We also use that field to check if a package has been marked as failed, in which case, we can reach out to our customers and let them know and/or try to remedy the failure by ourselves.

As you can see, the information in the shipment_status is vital for our operations and the customer experience we provide.

Hi team,

any progress on this?

Hi Milan - apologies for the slow response and thank you for the detailed use case information. These fields are clearly useful and should be easy to add. We are taking this up in one of our coming sprints. 

Hey Bjorn,

thanks for the reply. I'm glad it will finally be done. Can you please ping this thread once it's deployed?

Will the fields be backfilled? If so, does it affect the MAR (i.e. billing) count?

Hi, has any progress been made on this issue at all?