Release 2026.11-R8
Released November 19, 2026.
Mispicks follow the location's Mispick Handling setting
Completing a pick now handles mispicked items by the location's Mispick Handling setting in the Fulfillment App (mispick_handling_strategy). Before this release, the setting was saved but not applied. This affects every location that uses picks.
- Cancel the items (
cancel, the default). The mispicked quantity becomes acancelledline item with a cancellation reason. Before, a pick with every item mispicked returned its items toallocated, and the mispicked part of a partly picked line was dropped without a record. - Move to a new Order (
new_fulfillment_order). The mispicked quantity moves to a new fulfillment order with no location, so it can be allocated again. When every item of a fulfillment order is mispicked, the same fulfillment order is kept and its location is removed.
In both cases the reservation for the mispicked quantity is released. A shipment that already exists for the pick's items is cancelled when the mispick leaves it with no item to ship. See Picks.
Via the API: this is the behavior of POST /orders/picks/{pickId}/complete.
Order and Fulfillment API changes
These changes can affect an integration that calls the Order or Fulfillment API.
- Cancel an order returns 400 when the order cannot be cancelled.
POST /orders/{orderReference}/cancelfor an order that isprocessing,fulfilledorclosednow returns 400 and sends no webhook. Before, it returned 200, changed nothing and still sent the order cancel webhook. The Shopify connector treats this response as final and does not retry. - Unknown IDs return 404. A pick, pack, package or collection ID in the URL that does not exist returns 404. Before, it returned 400.
- Missing required fields return 400. A pick or pack item request without its ID or
quantityreturns 400 naming the field. Before, it returned 500. Aquantitybelow 1 also returns 400. Before, it was accepted. - Merge, split, location change and line item cancel act only on open or allocated items. A request for an item that is in a pick, picked or in a pack returns 400. A location change returns 400 while any item of the fulfillment order is in one of those states.
- Merge needs line items. Merging fulfillment orders without
source.line_itemsreturns 400. Before, it returned 500. - Complete a pack rejects an unknown
ship_zone. Before, the value was accepted and then dropped. Completing a pack now fulfills the items first, so a pack that fails to complete can be completed again. selection_methodis accepted when picking items and is kept when a later call leaves it out.- Collection responses have four fewer fields.
pk,sk,expire_schedule_idandcancel_schedule_idare no longer returned. They were internal values. - A collection can be handed over without a code. Verify and collect with
override: trueworks when no code was sent, and the collection'sverification.methodis thenNONE. This lets staff hand over to a customer who has no email. See Customer collection. - Hold rules are validated. A hold rule with a blank name, a value without an operator, an order value without a currency, a negative or inverted range, a negative sequence, or a sequence another rule already uses is rejected with 400. Updating a hold rule without
sequencekeeps its position. Before, it moved to the front. - Order settings are validated. Duplicate allocation priorities and collection day counts below 1 are rejected with 400.
- Changing a fulfillment order's collection location re-checks the location. The new location is checked as it is when an order is created, and the location errors in the order's
error_detailsare replaced with the result. Before, an error from the earlier location stayed on the order. The stored collection address is now filled from the location, as on order create. Delivery fulfillment orders are unchanged.
Shipping API changes
- The collection time slot is
scheduled_time_slot_id. Thecollectionobject on a shipment now usesscheduled_time_slot_id, the name thedeliveryobject already uses. This applies to create and update shipment, to shipment responses and to webhooks. The earlier name,schedule_time_slot_id, is no longer read or returned on any endpoint, the schedule endpoints included. A request that sends it is not rejected: the time slot is ignored and the collection is scheduled for the whole day. - Incoterms are validated the same way on create and update.
customs.incotermsaccepts the listed values in any letter case. Any other value returns 400. - Manifest responses no longer include
retry_info. It was internal state. The create manifest request no longer listsmanifest_idorship_manifest_date. Both were ignored, and a request that still sends them is not rejected. - Pounds and kilograms convert at 1 lb = 0.45359237 kg. Before, the API used 0.454, so a weight sent in pounds converted about 0.09% high. For example, 50 lb is now 22.68 kg and was 22.70 kg, and 1 kg is now 2.205 lb and was 2.203 lb. The Dashboard now uses the same factor, so it and the API give the same converted weight.
Shipment permissions
Several shipment endpoints now need a different permission. This matters for custom roles and for API clients with a permission list. The built-in Dashboard roles keep the same access.
| Endpoint | Needed before | Needed now |
|---|---|---|
| Schedule delivery, update delivery schedule, update collection schedule | shipment:process | shipment:update |
| Add and remove child shipments | shipment:process | shipment:update |
| Validate a bulk shipment import | shipment:process | shipment:import |
| Get a shipment's status events | status-event:read | shipment:read |
| Refresh a shipment's status from the carrier | status-event:process | shipment:process |
The status-event permissions are removed from every role, user and API client. A role or client that had status-event:read without shipment:read can no longer read status events until shipment:read is added. In the same way, one that had status-event:process without shipment:process can no longer refresh a status.
In the Dashboard, the scheduled deliveries chart in Control Tower now needs report:list, as the other Control Tower charts do. Before, it needed shipment:list.
The deprecated PATCH /shipments/{shipmentId}/cancel works again with shipment:cancel. It had returned 403 since October 19, 2026. Use POST /shipments/{shipmentId}/cancel in new integrations.
MCP
cancel_orderreports an error for an order that can no longer be cancelled. Before, it reported success although nothing changed.schedule_deliveryandschedule_collectionneedshipment:update. Before, they neededshipment:process.- Shipment items in
create_shipment,edit_draft_shipment,confirm_shipmentandget_shipping_ratesno longer listproduct_item_code. Carriyo never stored it. Useproduct_ref.
Dashboard
- Fulfillment Location column on the order list. Under Orders, Fulfillment Location is available as a column. An order with more than one location shows Multiple, and hovering over it lists them. Cancelled fulfillment orders are not counted.
- Line item fields in the order export. In the order list Export dialog, Select attributes now offers the line item fields, such as SKU, description, quantity, unit price and weight. Line item custom attributes are not offered. When a line item field is selected, the export has one row for each line item, as All order attributes has.
- Amounts show a thousands separator in the order total on the order list and on the order page.
- Parcel weight when fulfilling an order. A parcel weight equal to the box weight plus the item weights is accepted. Before, some values were rejected with "Parcel weight should not be less than the weight of the items assigned". Switching the unit system clears a packing template that does not match the new units, and the parcel weight is now recalculated without that template's box weight. A weight you typed in is converted as before.
- Update Delivery Address and Change Collection Location no longer add a schedule. Before, saving either dialog on a fulfillment order without a schedule saved a one-hour window starting when the dialog was opened.
- Date range fields accept day 10. Before, the 10th of a month showed in red and a date typed with day 10 was not saved. This affected date range filters, blackout dates and the manifest pickup time slot.
Connectors
- Shopify: orders that can no longer be cancelled. When Shopify cancels an order that Carriyo is already processing or has fulfilled, the connector marks the cancel as ignored and does not retry it. Before this release, the cancel was reported as successful although nothing changed.
- Shipa: accounts still on API version V1. Shipa accounts no longer have an API version, because Carriyo calls the Shipa V2 API for every account. Under Settings > Carrier Accounts, a Shipa account no longer shows Shipa API Version, and Order Category is always shown. An active account that was still set to V1 is made inactive, because Shipa rejects a V1 API key on the V2 API. To use it again, enter a V2 API key and activate it.
Fixes
- Order cancel without a request body:
POST /orders/{orderReference}/cancelsent without a body now cancels the order. Before, it returned 500. - Stock events for shipments without an order: a shipped shipment that has no order no longer sends a stock reduction event. Before, the event was rejected and showed as a rejected event in the event history.