StoreFulfil™ Library

Operating journey / step 50

Stock and returns

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.

Processing Returns and Restocking

The manual workflow for logging returned items and determining condition.

Updated Aug 2026
Owner: Operations Admin
Area: Returns

Before you begin

Log every returned line, record its condition, and restock only eligible good inventory.

Prerequisites

  • A Warehouse Admin can identify the client and available order reference.
  • Each physical line is inspected before its condition is saved.
  • The SKU can be matched to an existing client inventory row before restocking.

Stop and check

Do not restock damaged, writeoff, unmatched, or invented items.

Returns are logged manually line by line.

Logging Workflow

  1. Open Returns and create a return, adding an order reference when one is available.
  2. Log each line condition explicitly as 'good', 'damaged', or 'writeoff'.
  3. Only lines marked as 'good' can be restocked individually.

What this is and when to use it

Use this Admin guide after a return is identified and each physical line can be inspected.

Record each line

  1. Open or create the return with the available order reference.
  2. Inspect every line and choose good, damaged, or writeoff.
  3. Restock only a good line whose SKU matches the client inventory row.
  4. Read the resulting counts and leave unmatched lines for review.

Questions and hand-off

If The item is damaged or a writeoff

Record that condition and keep it out of sellable stock.

If The SKU or client cannot be matched

Do not substitute a row; leave it unresolved and hand it to the Operations Admin.

If A good-line restock fails

Keep the error and physical item together and escalate rather than repeating blindly.

What happens next

Every line has a condition and the return shows which good lines were restocked and which remain exceptions.

Expected Outcome

Returned items are documented with a defined condition. A good line can be restocked when its SKU matches an existing client inventory row.

Runbook evidence

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

State checkpoints

Received and unclassified

The return exists, but no condition decision has been recorded for one or more lines.

Next: Inspect and classify each line.

Classified

Every line is marked good, damaged, or writeoff.

Next: Restock only a good line with a matching inventory row.

Restocked or written off

The permitted line action has completed and the return counts show the result.

Next: Check the counts and leave any unmatched line for review.

Completion evidence

  • Every line has a condition and the resulting restock or write-off counts are visible.

Escalation evidence

  • Record the client, return reference, line or SKU, condition, and displayed error.

Work safely

Who may take this action

Warehouse Admin

What you should see

The return exists, but no condition decision has been recorded for one or more lines.

Safe next step

Inspect and classify each line.

What not to do

Do not restock damaged, writeoff, unmatched, or invented items.

How to tell it is complete

Every line has a condition and the resulting restock or write-off counts are visible.

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

Content Index