This documentation provides a reference to the createAndCompleteReturnOrderWorkflow
. It belongs to the @medusajs/medusa/core-flows
package.
This workflow creates and completes a return from the storefront. The admin would receive the return and process it from the dashboard. This workflow is used by the Create Return Store API Route.
You can use this workflow within your customizations or your own custom workflows, allowing you to create a return for an order in your custom flow.
Source CodeWorkflow hook
Step conditioned by when
View step details
CreateOrderReturnWorkflowInput & AdditionalData
CreateOrderReturnWorkflowInput & AdditionalDataCreateOrderReturnWorkflowInput
objectAdditionalData
objectadditional_data
property accepted in HTTP
requests, that allows passing custom data and handle them in hooks.
Learn more in this documentation.ReturnDTO
ReturnDTOid
stringstatus
ReturnStatusorder_id
stringitems
OrderReturnItemDTO[]display_id
numbermetadata
null | Record<string, unknown>exchange_id
stringOptionalclaim_id
stringOptionallocation_id
stringOptionalno_notification
booleanOptionalcreated_by
null | stringOptionalcreated_at
string | DateOptionalupdated_at
string | DateOptionaldeleted_at
string | DateOptionalcanceled_at
string | DateOptionalrequested_at
string | DateOptionalreceived_at
string | DateOptionalHooks allow you to inject custom functionalities into the workflow. You'll receive data from the workflow, as well as additional data sent through an HTTP request.
Learn more about Hooks and Additional Data.
This hook is executed before the return's shipping method is created. You can consume this hook to return any custom context useful for the prices retrieval of the shipping method's option.
For example, assuming you have the following custom pricing rule:
You can consume the setPricingContext
hook to add the location_id
context to the prices calculation:
1import { createAndCompleteReturnOrderWorkflow } from "@medusajs/medusa/core-flows";2import { StepResponse } from "@medusajs/workflows-sdk";3 4createAndCompleteReturnOrderWorkflow.hooks.setPricingContext((5 { order, additional_data }, { container }6) => {7 return new StepResponse({8 location_id: "sloc_123", // Special price for in-store purchases9 });10});
The price of the shipping method's option will now be retrieved using the context you return.
Handlers consuming this hook accept the following input.
input
inputorder
OrderDTOadditional_data
Record<string, unknown> | undefinedadditional_data
property in HTTP requests.
Learn more in this documentation.This section lists the events that are either triggered by the emitEventStep
in the workflow, or by another workflow executed within this workflow.
You can listen to these events in a subscriber, as explained in the Subscribers documentation.
Event | Description | Payload | Action |
---|---|---|---|
| Emitted when a return request is confirmed. |
| |
| Emitted when a return is marked as received. |
|