StoreFulfil™ Library

Operating journey / step 50

Security and recovery

How-to

Use this guide when work has reached this point. If the visible state does not match, stop and follow the named hand-off.

Triage the Needs Attention Queue

Separate connection, inventory, webhook, location, and shipment exceptions from routine fulfilment work.

Updated Aug 2026
Owner: Operations Admin
Area: Exceptions

Before you begin

Route each exception to the right owner by reading its type, age, evidence, and supported action before touching the queue.

Prerequisites

  • The Needs Attention list and detail state are available.
  • The user knows which actions are Admin-only.
  • The client, order, shipment, or inventory reference can be captured safely.

Stop and check

Do not repeat paid actions, hide a case, or declare success without a confirmed result.

Needs Attention collects operational exceptions such as synchronisation failures, connection health problems, unmapped locations, webhook retries, and shipment sync failures.

Triage in Order

  1. Read the exception type, client, current status, age, and action offered by StoreFulfil.
  2. Operators should leave admin-only actions unchanged and give the visible case information to an Admin.
  3. Admins may use the supported Sync now or Retry action when it matches the exception.
  4. Re-check the result and confirm the exception has cleared before returning to the order queue.

What this is and when to use it

Use Needs Attention when routine work stops because a connection, inventory, webhook, location, or shipment problem needs review.

Triage one case

  1. Read the exception type, client, age, current state, and offered action.
  2. As an Operator, leave Admin-only actions alone and hand over the visible details.
  3. As an Admin, use Sync now or Retry only when it matches the displayed case.
  4. 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.

Expected Outcome

Exceptions are assigned to the right role with a clear evidence trail and no unsupported workaround.

Runbook evidence

Use these signals to decide whether the work is ready to continue, complete, or needs an owner.

State checkpoints

New exception

StoreFulfil has recorded a case that may affect routine work.

Next: Read type, client, age, current state, and offered action.

Action available

A supported sync, retry, or recovery action matches the exception.

Next: Use it only if your role owns that action and review the result.

Escalation needed

The case is repeated, ambiguous, or outside the supported action.

Next: Hand off the recorded evidence without repeating a risky action.

Cleared

The exception no longer appears and the underlying record reports the expected state.

Next: Return to routine work after checking the affected record.

Completion evidence

  • The case is cleared or has an evidence-based owner and hand-off.

Escalation evidence

  • Record the client, exception type, age, reference, action, result, and time.

Work safely

Who may take this action

Warehouse Operator may assess and hand off; Warehouse Admin may use the supported Sync now or Retry action

What you should see

StoreFulfil has recorded a case that may affect routine work.

Safe next step

Read type, client, age, current state, and offered action.

What not to do

Do not repeat paid actions, hide a case, or declare success without a confirmed result.

How to tell it is complete

The case is cleared or has an evidence-based owner and hand-off.

© 2026 STOREFULFIL PTY LTD (ACN 701 718 649 · ABN 98 701 718 649), Queensland, Australia · StoreFulfil™ Operations Library.

Content Index