DEFAULT_RETURN_DESTINATION_LOCATION
Setting
Changed on:
12 Aug 2025
| Setting Area | UI component, Workflow, Orders |
|---|---|
| Supported context levels: | RETAILER |
Overview
If the return destination is not provided to the workflow, then the rule will look for the default return destination stored in this setting.
The value in this setting will be used to populate the `destination location` field on the return order object when it is created.
A field may optionally send in its destination location for custom returns solutions when submitting the user action. The setting will serve as a fallback value if the field does not provide a destination location (which the reference solution does not)
See destinationLocation in the `CreateReturnOrder` GraphQL schema for details.
Values
| Data Type | Values |
|---|---|
| STRING | Example Value:
|
Configuration example
1POST: {{fluentApiHost}}/graphql
2
3
4GraphQL Query:
5mutation CreateSetting {
6createSetting(input: {
7 name: "DEFAULT_RETURN_DESTINATION_LOCATION",
8 valueType: "STRING",
9 value: "LOC_SYD",
10 context: "RETAILER",
11 contextId:1}) {
12 id
13 name
14 }
15}Update example
1POST {{fluentApiHost}}/graphql
2
3mutation updateSetting {
4 updateSetting(input: {
5 id: 5001464,
6 name: "DEFAULT_RETURN_DESTINATION_LOCATION",
7 valueType: "STRING",
8 value:"LOC_MELB",
9 context: "RETAILER",
10 contextId: 1}) {
11 id
12 name
13 }
14}
15