Release 2026.11-R2
Released November 5, 2026.
Locations: auto-ship on allocation and auto-close on fulfillment
A fulfillment location has two new settings. Both are off by default.
In the Dashboard: open Settings > Administration > Locations, open the location and go to the Fulfillment Settings tab. The two toggles appear under Fulfillment Location once that is on.
Via the API: the location has two new fields, auto_ship_on_allocation and auto_close_on_fulfillment. Set them on POST /locations, PUT /locations/{location-id} and PATCH /locations/{location-id}. Every location response returns them.
- Auto-ship on allocation: Carriyo creates and books a shipment for a fulfillment order's items as soon as it is allocated to the location. That happens when an order is created with the fulfillment order already allocated there. It also happens when the fulfillment order is allocated or re-allocated there, and when a held order or fulfillment order allocated there is released. Only fulfillment orders with delivery method
DELIVERYare booked, and items that already have a live shipment are skipped. If the shipment can't be created, allocation still succeeds. The fulfillment order recordsshipment_creation_failedin itserror_details; fix the cause and retry withPOST /orders/{orderReference}/fulfillment-orders/{fulfillmentOrderReference}/ship. - Auto-close on fulfillment: shipped items are closed as soon as they are fulfilled, instead of when their shipments are delivered. The fulfillment order and the order follow. Shopify orders are excluded, as they are from closing on delivery.
Two related changes apply to every location. Moving a fulfillment order to another location, or removing its location, cancels the shipments its pending items are booked on. When one can't be cancelled, the fulfillment order records shipment_cancellation_failed in its error_details; cancel that shipment by hand. Cancelling an order, or the items of a fulfillment order, cancels a shipment once every item on it is cancelled.
Shopify: Shopify orders are auto-shipped too. When Shopify later reports the fulfillment, Carriyo links it to the existing shipment instead of creating a second one. It then sends the shipment's tracking number and current status to Shopify. See Auto-ship on allocation.
Shopify connector activity shows what happened to queued webhooks
Shopify's order, fulfillment order and fulfillment webhooks are processed from a queue. The Activity tab of the connector, under Settings > Integration, used to record each of them as a success as soon as it was queued. What happened next was not recorded. The tab now records the outcome of each processing attempt as the request's response: succeeded, ignored with the reason, or failed. Each entry carries the number of retries so far. A failure counts toward the connector's failure alerts. Routine ignored webhooks, such as an update with nothing to change or one received during a reallocation, are not recorded. A Shopify order that Carriyo refuses because the order quota for the current cycle is used up is now recorded as failed. The order is missing in Carriyo, so it is a failure to the merchant.
Intelligence for users limited to merchants
A user whose grants name specific merchants now reads Intelligence reports one merchant at a time. The merchant picker lists their merchants only, without All merchants, and each report opens on the first of them. A shared link that names another merchant opens on their first merchant too. The channel, carrier and country selectors list values from their merchants only. Users whose grants cover every merchant see no change.
In the Dashboard: an admin whose own grants are limited to merchants can give Intelligence over those merchants only. A grant beyond them is refused with a message naming the merchants. An Intelligence grant covers every country and location of the merchants chosen; one limited to countries or locations is refused. With this release, Carriyo narrows the Intelligence access of existing users to the merchants their other grants reach.
Manifest document for UPS and Parcel Pro
Carriyo can print a manifest for UPS and Parcel Pro accounts laid out like the UPS end-of-day summary. Carriyo sets this up on request. The manifest shows:
- the shipper's address, the carrier account and its UPS account number, and the manifest number and dates,
- a summary by service with shipment and package counts,
- a signature block for the shipper and the driver, and
- one row per shipment with its order reference, shipment ID, tracking number, package count and weight.
In the Dashboard: a Parcel Pro account in Settings > Carriers has a new optional UPS Account Number field on its Account Setup tab. It is printed on the manifest only; bookings keep using the API user in the account's credentials. UPS accounts print their Shipper Number.
Unit system choice when fulfilling an order
In the Dashboard: open the order under Orders and choose Fulfill or Ship. You can switch the Unit System on the fulfillment screen between Metric and Imperial. It was locked to Metric. The screen opens on the unit system of the order's items, Metric when they have no weight. Switching it converts the parcel sizes and weights, and the parcel weight total converts the item weights to the chosen unit before adding them. Carriyo creates the shipment with its parcels and item weights in that unit. The order's line items keep their own weights.
Via the API: POST /orders/{orderReference}/fulfill, POST /orders/{orderReference}/fulfillment-orders/{fulfillmentOrderReference}/fulfill and POST /orders/{orderReference}/fulfillment-orders/{fulfillmentOrderReference}/ship accept parcels in either unit system: kg and cm are metric, lb and in are imperial. When the parcels' unit system differs from the items', Carriyo converts the item weights on the shipment to the parcels' unit. An item without a weight gets 0 in that unit instead of the weight from the product catalog. Before, such a request was refused with measurement_system_mixed. Parcels that match the order, or that carry no unit, behave as before.
Combined documents in the API reference
Combined documents shipped in release 2026.10-R7. The API reference now covers them, and the Manage shipping documents guide walks through every kind of document.
- Document settings:
POST /document-settingswithtypeset tocombinedcreates one. The reference lists the membersassigned_documentsaccepts, the rules a combined document must meet, and the errors that break them. A setting can't change to or fromcombined; delete it and create a new one. Deleting a setting through the API doesn't remove it from the document groups that list it, so update those groups yourself. - Shipments: the
Get shipmentreference describes thecombinedentry inpost_shipping_info.documents. Its link builds the PDF on demand. While a document is still being fetched from the carrier, the link answers503with aRetry-Afterdelay. When the document can no longer be produced, it answers422. Uploading a file to a combined document through/shipments/{shipment_id}/documentsis refused with400. - Webhooks:
notify_combined_document_updateis documented on the webhook configuration, andcombined_document_updatein Shipment webhook events, with what to read from the payload. - Deprecation: the
qr_codedocument type is deprecated. Carriers no longer return QR code documents, so don't use it for new settings.
Carrier updates
- Emirates Express: the Special Handling setting on the account, in Settings > Carriers, now also offers CIR (Customer Initiated Returns) and NST (Non-Stackable), besides SIG and RTS. Reverse shipments now mark the pickup, the customer, as residential and the drop-off, the merchant, as non-residential. Before, the pickup was always non-residential and the drop-off always residential, whatever the direction. This applies to bookings, pickup requests and cost estimates.
Fixes
- Order webhook triggers for ship and cancel: an order webhook created in Settings > Integration with the Fulfillment Order Ship or Fulfillment Order Cancel trigger was saved with a trigger name Carriyo never sends. It never fired. The Dashboard now saves the triggers Carriyo sends,
FULFILLMENT_ORDER_SHIP_LINE_ITEMSandFULFILLMENT_ORDER_CANCEL_LINE_ITEMS. - Shipment item values from order fulfillment: a shipment created by fulfilling an order carried each item's price and cost multiplied by its quantity. Carriyo multiplies by the quantity again when it works out the shipment value, so the value was inflated. The items now carry the unit price and cost. The same applies to carrier cost estimates for an order.
- Cancelled shipments clear their alerts: cancelling a shipment, or a cancellation by the carrier, now resolves the shipment's open alerts. Before, they stayed open.
- System log details that were never stored: when the details of a System Log entry could not be stored, the entry still linked to them and the link failed. The entry no longer links to details that don't exist, on shipments, orders and return requests.
- Shopify fulfillment orders with many line items: the Shopify connector read at most 25 line items of a fulfillment order, and 25 fulfillments. An order past that lost items when it was created or updated in Carriyo. The connector now reads every page.
- Shopify (older connector) cancelled shipments: when a shipment was cancelled before its order was fulfilled in Shopify, the older Shopify connector tried to fulfill it anyway. Shopify answered
409, which showed as a failure and raised an alert. The connector now ignores it. - Reusing a previous password: accepting an invitation or resetting a password with a password you used before is refused with
400and the message "This password has been used before". Before, it failed with a server error. - Fulfillment App password change: the Change Password section of your profile in the Fulfillment App now asks for your current password and the new one twice, as the Carriyo Dashboard does. Once the password is changed, you are signed out everywhere. The section is not shown to users who sign in with SSO.
- Store App scheduled delivery date: in the Store App, the scheduled delivery date is now saved when you create an order, and can be cleared. Changing it also resets the delivery window and time slot, which stayed from the previous date.
- Shipment activity without system logs: the Activity of a shipment with no system log entries now loads. Before, it failed.
- Long city or state text: a shipment whose city or state text is longer than 1,024 bytes no longer fails with a server error. The text is kept as sent, without a city match.
- Masked secrets in logs: the System Log, webhook events and carrier logs now mask secrets the same way. A long key keeps its last four characters, as
****6789, so you can tell which one was sent; a short value shows****. Any field, header or query parameter whose name contains a word such astoken,secret,password,signature,cookie,credentialorkeyis masked. That covers JSON, XML and form bodies. Before, system logs masked fewer names and hid the whole value.