Even for shipments without carrier tracking, staff can now manually mark them as "Delivered." Merchants shipping with unsupported carriers can keep their orders' shipping status accurate.
For shipments with no linked carrier tracking, there was little way to reflect "Delivered" even after delivery completed, making it hard to keep an order's shipping status accurate.
Staff mark the shipment as "Delivered" in the admin. Even untracked shipments can have their shipping status closed out accurately.
The article lists two places where staff can mark an order as Delivered.
On the fulfillment card in an individual order, you can mark that shipment as Delivered. This is the place to use when you want to handle orders reliably one at a time.
On the orders list page, you can update multiple orders to Delivered at once. This lets you clear the follow-up work in one go after a batch of shipments is completed.
| Item | What the article says |
|---|---|
| Scope | Scope shipping fulfillments without carrier tracking (in the admin) |
| Intended users | Merchants shipping with unsupported carriers |
| Who performs it | Staff |
| Where it is performed | The order's Fulfilled card / the Orders page (bulk, multiple) |
| Category | Feature Admin |
| Customer notifications | Not stated |
| Whether it can be undone or changed again | Not stated |
| Handling in API / Webhook | Not stated |
| Supported plans and countries | Not stated |
| Permissions (which staff permission is required) | Not stated |
A feature for manually and correctly closing out shipments whose delivery status is not filled in automatically because they have no carrier tracking or use an unsupported carrier. It does not replace the automatic updates for shipments that do have tracking.
Both per-order (the Fulfilled card) and bulk updates from the orders list (the Orders page) are provided. From an operations design standpoint, it is a good idea to decide how to use each based on volume and who is responsible.
The article only describes manual operation in the admin. If you want to handle delivery status through automation or external system integration, you need to separately verify whether it is possible via the Admin API.
Delivered is entered manually by staff. Because gaps with the actual delivery can occur (marking too early or forgetting to mark), setting operational rules for who marks it and when keeps accuracy high.
Now that Delivered can be recorded correctly even for untracked shipments, the groundwork is set for reports and workflows triggered by delivery completion (see the use cases below).However, the article doesn't state whether notifications or automation are linked to this, so any integration design should assume hands-on verification first.