Goal
Clear everything waiting on a manager's decision, across all your locations, from one page.
Who
Field Manager or Org Admin.
Steps
From the Field home page, open Actions Needed. Four tabs, each with a count:
Bin requests: items Techs have asked to stock.
Transfers to acknowledge: incoming transfers nobody has confirmed yet (see 2.6).
Product adds needing review: photo or typed adds Sibi couldn't identify on its own.
Failed restocks: restock requests that never became orders.
On Bin requests, each card shows the requester, the product, and the minimum and maximum the Tech asked for, which is what the location would reorder. Approve or Deny right on the card.
On Product adds needing review, each card says specifically what's blocking identification and what would fix it, for example a clearer photo or the store's item number. Your options on each card:
Retry with a hint: add a brand, model number, or SKU and let Sibi try again.
Add as ad hoc: skip identification and stock it as-is. The Tech's photo and reported quantity carry over.
Dismiss: drop the add entirely.
Notes
Everything here also appears on the affected location's own Feed, so you can work location by location instead if you prefer.
Until a bin request is approved, the bin doesn't appear on restock orders. The Tech still sees it in their mobile Inventory tab with a Pending Approval indicator.
Denying a request doesn't delete the bin; it parks it. If you change your mind, the bin can be approved later.
If a resolved add was matched to the wrong product, open it in the location's Feed and use Not this? Replace to enter the correct model number or SKU.
Techs can retry, rescue, or dismiss their own location's stuck adds from the mobile app too (see 3.8), so simple fixes don't have to wait for a manager.