Fluent Commerce Logo
Docs

fc.graphql.returnOrder.create.event

Setting

Changed on:

2 Nov 2026

Setting AreaOrders
Supported context levels:ACCOUNT

Overview

This setting is a feature toggle that controls which Retailer's workflow processes a Return Order. By default, the corresponding `CREATE` event is sent for the Retailer of the Return Order, so a user who works with several Retailers can create Return Orders for any of them, and each Return Order is processed by the workflow of the Retailer it belongs to.

Values

Data TypeValues
STRINGDefault Value(s):
  • `normal`
Possible Values:
  • `normal`
  • `disable-cross-retailer`

Detailed technical description

To ensure full backward compatibility, this setting toggles between the following:
  • Normal behavior:
    A Return Order created with the `createReturnOrder` mutation for any Retailer starts the workflow of the Retailer of the Return Order. The `CREATE` event takes the Retailer of the Return Order, not the primary Retailer of the user. This is valid under the following conditions:
    • The `fc.graphql.returnOrder.create.event` setting is created with the `normal` value set
    • The `fc.graphql.returnOrder.create.event` setting is created with any invalid value
    • The `fc.graphql.returnOrder.create.event` setting is not created
  • And previous functionality:
    The Return Order is created for the Retailer provided in the mutation, but the `CREATE` event is sent for the primary Retailer of the user, so the Return Order is processed by the workflow of the user's primary Retailer. This is valid under the following conditions:
    • The `fc.graphql.returnOrder.create.event` setting is created with the `disable-cross-retailer` value set (the value is case-insensitive)

Configuration example

1POST {{fluentApiHost}}/graphql
2
3mutation CreateSetting {
4   createSetting(input: {
5		name: "fc.graphql.returnOrder.create.event", 
6		valueType: "STRING", 
7		value: "disable-cross-retailer", 
8		context: "ACCOUNT", 
9		contextId: 0
10   }) {
11    id
12    name
13  }
14}

Update example

1POST {{fluentApiHost}}/graphql
2
3mutation updateSetting {
4  updateSetting(input: {
5		id: 123,
6		name: "fc.graphql.returnOrder.create.event", 
7		valueType: "STRING", 
8		value:"normal", 
9		context: "ACCOUNT", 
10		contextId: 0
11  }) {
12    id
13    name
14  }
15}