# Upcoming change to the remote\_shipment\_id format **URL:** \ **Category:** Changelog\ **Created:** [October 13, 2026, 2:20pm UTC](https://developer-forum.veeqo.com/t/upcoming-change-to-the-remote-shipment-id-format/1726 "2026-10-13T14:20:38Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Alex-Veeqo](https://yyz1.discourse-cdn.com/flex033/user_avatar/developer-forum.veeqo.com/alex-veeqo/32/416_2.png) [@Alex-Veeqo](https://developer-forum.veeqo.com/u/Alex-Veeqo)\ **Post date:** [October 13, 2026, 2:20pm UTC](https://developer-forum.veeqo.com/t/upcoming-change-to-the-remote-shipment-id-format/1726/1 "2026-10-13T14:20:38Z")
We are making a change to the format of `remote_shipment_id` returned by the Rate Shopping API and the Allocation Rates API. The identifier should be treated as a string of variable length. Values returned after this change may be longer than those previously issued. The example values in our specifications have been updated to reflect the new format: - [Rate Shopping API](https://developers.veeqo.com/rate-shopping-api/) - [Allocation Rates](https://developers.veeqo.com/api/operations/tags/allocation-rates/) Please review the following in your integration: - Any field or database column storing this value should accommodate a longer identifier. We recommend using an unbounded text type, or allowing generous headroom. - Any step that truncates the value will prevent bookings from succeeding, as the value is passed back to us when booking a shipment and must match exactly. - Any validation of the identifier’s prefix, or parsing of its contents, should be removed. This change will start to be rolled out gradually, so both formats may be returned during the transition period. Please ensure your integration accepts either rather than switching behaviour on a fixed date. If you are unsure whether this affects your integration, reply to this thread or reach out to Veeqo Support via the Support Messenger in the app or at [helpme@support.veeqo.com](mailto:helpme@support.veeqo.com).