Pyle

How to Process a Return ​

What This Task Does ​

This task records and advances a return from returned-item intake through confirmation, approval, and completion.

Use it when items are coming back from a customer and your team needs to process the operational return correctly.

Before You Start ​

Make sure:

  • the original order exists
  • the relevant fulfillment request is known
  • you know which quantities are being returned
  • your team has access to the internal return workflow or return-management screen used in your project

In the shared package, the return lifecycle is well defined, but the exact packaged operator screen is not present in the repo inspected in this pass.

Steps ​

  1. Open your project’s return workflow and create a new return.
  2. Enter the core return context:
    • order
    • fulfillment request
    • customer
    • current location
    • inventory location
    • return type
    • internal reason
  3. Add the fulfillment-request items and quantities to return.
  4. Add the required fees before moving forward:
    • shipping fee
    • restocking fee
  5. Add return shipping-line or transport details if they apply.
  6. Confirm the return items with a confirmation number.
  7. Approve the return items when the return is accepted.
  8. Complete the return only after the record is ready for closure.
  9. Send supplier return details or customer drop-off details when the return data is complete enough to support them.

What Happens Next ​

After the return is processed:

  • the return record reflects confirmed, approved, or completed state
  • return activities are logged
  • customer or supplier communications can be sent, including approval or return-authorization details
  • the parent order amount due can be recalculated when the return is configured to revise it

Common Mistakes ​

  • Forgetting to add shipping and restocking fees before confirm, approve, or complete.
  • Returning more quantity than is still left to return.
  • Completing the return before confirmation and approval data are ready.
  • Forgetting that the return workflow and the refund workflow are related but not identical.
  • Treating approval as the same thing as refund settlement.

Sources ​

  • packages/framework/src/Http/Controllers/Api/Admin/OrderReturnsController.php
  • packages/framework/src/Actions/OrderReturn/CreateOrderReturn.php
  • packages/framework/src/Actions/OrderReturn/UpdateOrderReturn.php
  • packages/framework/src/Actions/OrderReturn/ConfirmOrderReturnItems.php
  • packages/framework/src/Actions/OrderReturn/ApproveOrderReturnItems.php
  • packages/framework/src/Actions/OrderReturn/CompleteOrderReturn.php