Returns Setup
Returns Setup
Configure Returns
This involves setting up the returns parameters and config, based on the requirements capture from the Process Requirements Gathering chapter.
Some of the returns-related application properties are shown below.
The following properties relate to the nature, condition and routing of the returns and their associated items:
Return Properties - Nature and Routing
| Name | Description |
|---|---|
| return.types | "Types for the return as a whole." |
| return.location.types | "Location types for items to be returned." |
| returns.reasons | "Possible reasons for the returning a particular line." |
| returns.conditions | "Possible conditions for a returned item." |
| default.return.[locationtype].location | "For each location type defined using the property above, a default location should be specified." |
The following properties concern the relationship between returned items and the orders against which the return is to have occurred.
Return Properties - Order Relationship
| Name | Description |
|---|---|
| returns.authorisation.must.be.existing.order.reference | "Authorisation value in returns must refer to an existing order item external reference." |
| return.lines.linked.to.original.order | "Mandates whether return should be linked to a existing order." |
| returned.lines.in.original.order | "When creating a return lines whether order line must be in original order and have equal quantity or less." |
| returns.order.permitted.states | "The states in which orders are permitted to be in order to be associated with a return." |
The main job in setting up returns is, in consultation with the customer, to set appropriate values for the above sets of properties.
Once this is done, then returns processing can be handed over.
Verify Returns Processing
The OrderFlow implementation Engineer should go through returns process end to end with the customer, and validate the processing steps involved.
Returns Notifications
It is possible for a notification to be triggered on receipt of returns. This can either be a notification to a third party eCommerce system, or an email to a preconfigured list or recipients. Setup for this functionality is normally done through a post-launch task. However, if this functionality is required for launch, the OrderFlow Implementation Engineer should raise a ticket to initiate the work required.