Skip to content

Needs attention

Where the operation cards count what is waiting, Needs attention lists what is wrong. It is a ranked list, worst first, and every row ends somewhere you can act.

  • What shows up here
  • How each row reads
  • Failed actions
  • See also
  • Orders on hold, grouped by reason — waiting for payment, address problem, waiting for production, waiting for supplier stock, and the rest.
  • Orders short of stock — lines that could not be reserved, so nothing can pick them.
  • Delivery problems — shipments the carrier has flagged: failed attempts, exceptions, parcels returning to sender.
  • Stalled orders — orders that have not moved in days. Nothing is technically wrong with them, which is exactly why they get missed.
  • Failed actions — anything the app tried on your behalf and could not finish.

Each row shows the count, a few concrete examples, and a view all link into the filtered list. The examples matter: “14 orders on hold — waiting for payment” is a category, but seeing three order numbers tells you in a glance whether it is one customer’s bad card or a payment gateway outage.

Holds grouped by reason are the most-used block on the page. A hold is applied with a reason, a note and a reference to the document you are waiting on — a holdHoldA deliberate block on an order, recorded with a reason, a note and usually a reference to the document being waited on. A hold is a decision, not a failure. Read more → on production or supplier stock is not the warehouse being slow, and the list says so.

The last block is the one most systems hide. When the app tries something and it does not work — a label that would not print, a fulfillment Shopify rejected, a notification with no provider connected — it appears here rather than disappearing into a log.

Nothing self-heals silently and nothing is silently dropped: the item stays on the list until it either succeeds on retry or you resolve it.