Release 2026.11-R6
Released November 12, 2026.
Feeds in the Dashboard
A feed is a scheduled file import or export. Until now, Carriyo set up each feed for you. Feeds are now set up and monitored under Settings > Integration > Feeds. The page is shown to the Admin and IT Manager roles.
- Feed types: inventory import, inventory export and product import. The feed code, type and merchant are fixed once the feed is created.
- Imports read files from an Amazon S3 bucket: one that Carriyo manages for you, or your own bucket through an IAM role that Carriyo assumes. The feed page shows the external ID to set on that role.
- Exports deliver to an Amazon S3 bucket or to your SFTP server. The SFTP server must be reachable on the public internet. The password is not shown again after it is saved, and it is asked for again when the host, port or username changes.
- Export mode and interval: an inventory export sends All stock or Changes only, every set number of minutes, from 5 minutes up.
- Health: the list shows each feed as Active, Overdue, Failing or Inactive.
- Failure alerts are switched on for each feed. An import feed raises an alert when no file has arrived for the number of minutes you set. Feed alerts are shown to users who can edit feeds. Before this release they were shown to users who can edit connectors.
- Activity tab: what the feed did in the last 7 days. It lists each check for new files, each import and each export, with the file, the row counts and the result. A summary shows the files handled in the last 24 hours and whether the feed is failing now. View on a feed alert opens this tab.
The emails that a feed sent when an import or export finished are no longer sent. Use the Activity tab and feed failure alerts instead.
Changes-only inventory exports
An inventory export feed set to Changes only sends only the stock positions that changed since its previous export.
- Each export covers the changes after the end of the previous export, up to 2 minutes before the export runs. The last 2 minutes are left for the next export.
- When nothing changed, no file is delivered. The Activity tab shows that the run had nothing to export. Before this release, a file with only a header row was delivered.
- When delivery fails, the next export includes the same changes again.
- The first export after a feed is set to Changes only sends nothing. It marks the starting point.
All stock exports are unchanged.
Create manifests from the shipment list
Create Manifest on the shipment list now opens a dialog on the list and works on a mixed selection. Before this release, the action was unavailable when one selected shipment could not be manifested.
- Eligible shipments are
bookedorready_to_ship, have a pickup location and are not on a manifest. Every other selected shipment is listed with the reason it is left out. - One manifest per group: eligible shipments are split into one manifest for each carrier account, pickup location and merchant. With multi-location manifests enabled, they are split into one manifest for each carrier account.
- Create and confirm: the dialog creates and confirms each manifest. Turn on Create as draft to leave them as drafts.
- Results: each manifest shows its status and a link to open it, or its error. A manifest that failed can be retried from the dialog. The others are kept.
Request a pickup from a manifest
A confirmed manifest has a Request Pickup action when its carrier supports pickup requests. You choose the collection window, and Carriyo requests a pickup for the manifest's shipments that have none booked or in progress. A manifest that covers several pickup locations sends one request for each location. The result is shown for each shipment. When earlier requests failed, the action reads Retry Pickup.
The shipments table on the manifest page has a Pickup column with each shipment's pickup state. A failed pickup shows the carrier's error.
Manifest list and manifest page
- The manifest list has a Confirmed Date column, and a Carrier Manifest ID column that is hidden by default. Booked Date is now hidden by default. Manifests confirmed before this release show their confirm time in Confirmed Date.
- The manifest page shows the carrier manifest ID when the carrier issues one.
- When Cancel, Confirm, Retry or Ship fails, the dialog closes and the error is shown in a notification. Before this release, the dialog stayed open with the action button, and pressing it sent the request again.
Manifests API
The Manifests section of the Shipping API reference now matches the API.
- Confirm manifest,
POST /manifests/{manifest-id}/confirm, is documented.POST /manifests/{manifest-id}/ready-to-shipis deprecated in favor of it. - Retry manifest takes no request body. A pickup window sent in the body is ignored.
- The pickup window fields,
pickup_idsandbooked_dateon a manifest are deprecated. Useconfirmed_datefor the confirm time. - A shipment belongs to one manifest. A draft does not reserve its shipments, so one shipment can be on several drafts. Confirm and retry now reject a shipment that is already linked to another manifest with
400and the messageShipments: [...] already belong to another manifest. Before this release, confirming the second draft moved the shipment to it, and the shipment appeared on both manifests. Canceling a manifest now releases only the shipments still linked to it.
Fixes
- Carrier cost and carrier auto-select when fulfilling an order: on the fulfillment screen, the Dashboard sent the customer as the pickup address and the fulfillment location as the delivery address. For orders with no address on the customer, no carrier was selected and no cost was shown, with the error
Pickup city must not be empty. For other orders the cost was calculated in the wrong direction. The pickup is now the fulfillment location and the delivery address is the order's shipping address. The cost is shown in the order's currency, and a carrier's error is shown on the screen. Carriers you pick by hand are priced, and the estimate runs again when the parcels change. - Shipping rules with an empty carrier account entry: a rule saved with an empty entry in its carrier account list made three operations fail with a server error. These were deleting any carrier account, changing a carrier account's merchants, and creating or updating a shipment that matched the rule without a carrier. The empty entry is now skipped. A rule that uses the account still blocks the delete or the merchant change.
- Deleting a carrier account twice no longer adds a second
- Deletedto its name. - Get carrier network with an ID that does not exist returns
404with the messageCarrier network ... doesn't exist. Before this release, it returned a server error. - Reordering service level rules with a rule ID that does not exist returns
Service Level Rule can't be found. Before this release, the message named an automation rule.