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
  • On hold, one row per reason: waiting for payment, address problem, waiting for production, waiting for supplier stock, and the rest.
  • Not enough stock: orders whose lines could not be reserved, so nothing can pick them.
  • No product in Shopify: orders with an item that has no product in Shopify. Edit or cancel the item in Shopify.
  • Waiting for a plan: orders that can be picked once you confirm a plan in Shopify. Review plan opens the plan.
  • Reserving open orders: Floormode is still reserving stock, for example on the first day. It clears by itself.
  • Carrier problems: parcels the carrier could not move.
  • No progress for over a week: open orders with no change for over a week. Nothing is technically wrong with them, which is exactly why they get missed.
  • Did not go through, Held back and Dropped: updates the app could not send, is holding until a connection is back, or that expired. See Failed actions below.
  • Stores, with several stores: a store that joined and waits for Start, new products waiting for a link, a store whose plan ended, and a store that left.

For what to do about each order reason, see Why isn’t this order pickable?.

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 on your behalf and it does not work — a fulfillment Shopify rejected, a stock update Shopify refused, a refund that did not go through — it appears here, named in words such as Did not go through: marking an order fulfilled, rather than disappearing into a log.

Nothing self-heals silently and nothing is silently dropped: the item stays on the list until it succeeds on a retry or you resolve it. Most lead to where they are dealt with:

What did not go through Where it leads
A stock, tag, location, lot or Flow update Settings → Apps & API, its Shopify updates, to send it again
A hold, edit, payment, refund or cancellation of an order The Orders list filtered to Update did not go through; open each order to see what to do
An order’s parcel The same list; open the order’s parcel to send it again
A decision on a customer’s return request The return, to decide it again
A webhook or a message to a connected app Settings → Apps & API, which says why it failed and offers a retry where one can help (an alert, for example, is never sent again)

View all shows only for people who may open that list.