Use Needs Attention when routine work stops because a connection, inventory, webhook, location, or shipment problem needs review.
Needs Attention collects operational exceptions such as synchronisation failures, connection health problems, unmapped locations, webhook retries, and shipment sync failures.
Triage in Order
- Read the exception type, client, current status, age, and action offered by StoreFulfil.
- Operators should leave admin-only actions unchanged and give the visible case information to an Admin.
- Admins may use the supported Sync now or Retry action when it matches the exception.
- Re-check the result and confirm the exception has cleared before returning to the order queue.
Triage one case
- Read the exception type, client, age, current state, and offered action.
- As an Operator, leave Admin-only actions alone and hand over the visible details.
- As an Admin, use Sync now or Retry only when it matches the displayed case.
- Read the result and return to routine work only after the exception clears.
Questions and hand-off
If The case is repeated, old, or unclear
Do not keep retrying. Give the client, exception type, time, and result to the Operations Admin.
If The case is a pending shipment or paid DHL label
Use the matching recovery guide and keep the original shipment.
What happens next
Each exception has the right owner, a visible result, and either a cleared queue item or a complete hand-off.