Release 2026.11-R4
Released November 9, 2026.
Order list auto-refresh with a sound alert
Under Orders, the toolbar has an Auto Refresh button, as the shipment list already has. When it is on, the list reloads every minute with the filters, search and sort you have set. A message tells you how many new orders arrived. A second mode also plays a short sound when new orders arrive. A store can leave the list open and hear when there is work to do. Auto-refresh pauses while orders are selected and resumes when the selection is cleared.
Fulfillment Order Allocate webhook fires on every allocation
The FULFILLMENT_ORDER_ALLOCATE order webhook trigger now fires whenever a fulfillment order is allocated to a location, whatever caused it. That covers order creation, release from hold, a split, a location update and the allocate endpoint. Before, it fired only from POST /orders/{orderReference}/fulfillment-orders/{fulfillmentOrderReference}/allocate, so an order allocated at creation never sent it.
One webhook is sent per operation, after the operation's own webhook, with the same payload: newImage, oldImage, trigger and operation. The images show which fulfillment orders were allocated. A fulfillment order that auto-pick moved to processing in the same request counts as allocated. Auto-pick is the location setting that starts a pick as soon as a fulfillment order is allocated. The allocate endpoint now sends the trigger only when the call allocated something; before, it sent it on every call.
In the Dashboard: the Fulfillment Order Allocate trigger is available under Settings > Webhooks for order webhooks. See Order webhook events.
Peoplevox connector: orders shipped in parts
When a Peoplevox order is despatched in more than one part, each part now gets its own shipment. The warehouse receives only the labels and tracking numbers of the shipments booked in that despatch.
Before, a part despatched with the same carrier service as an earlier, already booked part was not booked at all. Peoplevox received the earlier shipment's label and tracking number again, and the carrier rejected the reused label. A part despatched with a different service was booked, but its label came back merged with the labels of the earlier parts.
Now a package that arrives after the shipment for its service is booked creates a new shipment. Its partner shipment reference carries a running suffix, <despatch number>-<service>-1, then -2, and so on; the partner order reference stays the order number on every part. Packages that arrive while the shipment is still a draft join it as before. A package that Peoplevox sends again for a shipment that is already booked gets that shipment's label and tracking number back. Carriyo creates no new shipment. A package that is already booked under one service cannot be moved to another. The print request fails with a message that names the shipment to cancel first.
This applies to every tenant on the Peoplevox connector.
Fulfillment App: customer collections while packing
In the Fulfillment App, a package for a customer collection picked up at the store (a local collection) now works on the pack screen the way a shipment package does, without booking a carrier. You create the collection for it, cancel it, and print its label. The collection label is available as PDF and ZPL, in the layout of the Carriyo shipment label without carrier details. Shipment and collection labels can still be printed after the pack is completed. The final button reads Complete Pack, and a pack can only be completed once every package has a shipment or a collection. Item images in the pick and pack dialogs are larger, and clicking one enlarges it in the app instead of opening a new tab.
Completing a pack keeps the collections created while packing and still creates one for every collection package that did not get one.
Via the API: POST /orders/packs/{packId}/create-collection with package_ids creates one collection for those packages and returns the pack. A pack package carries its collection_id, as it carries its shipment_id. Canceling a collection frees its packages, so they can get a new collection. A collection carries its PDF and ZPL labels in documents, and their links are signed again on every collection response.
Fixes
- Delivery address updates: saving the delivery address and the delivery schedule of a fulfillment order at the same time, as the Dashboard does, sometimes failed with
The conditional request failed. Carriyo now retries the update on the latest version of the order. - Working-hours and time-frame conditions for more countries: Carriyo could not evaluate a working-hours or time-frame condition for destinations in 56 countries, Benin among them. Those countries were missing from Carriyo's country time zone list. The condition counted as not met, so the delivery option, shipping rule, service level rule or allocation rule was skipped. The list now covers every inhabited ISO 3166-1 country.