fc.order.sourcing.proceeding.time
Changed on:
7 Aug 2025
| Setting Area | UI component, Workflow, Orders |
|---|---|
| Supported context levels: | RETAILER AGENT |
Overview
This setting determines the time when we start the pick and pack process for an order. It is measured in hours and set at retailer and/or agent levels. The setting also determines when a fulfillment will appear in the store by changing the status from `SCHEDULED` to `AWAITING_WAVE`.
Values
| Data Type | Values |
|---|---|
| INTEGER | Sample Value:
|
Detailed technical description
This setting is used by the rule ScheduleFulfilmentReleaseForDeliverAfter in the reference multi-order (aka mixed basket) workflow.
When a consumer makes an order with a future delivery date, most businesses will want to fulfill the order close to the delivery date rather than right away. This setting, along with the reservation time setting, is used to help facilitate this use case.
In our reference, in the mixed basket order model, fulfillment is not created right away for orders that are set to be delivered after a certain date. Instead, it is scheduled to be created a number of hours before the delivery date. This fulfillment creation reserves the stock to be picked and packed for the order and is thus called the reservation time.
After that, another event is scheduled to move the fulfillment into the awaiting wave status so that it may start the pick and pack process. This is scheduled some hours before the fulfillment's delivery date and is called the proceeding time. This setting controls this value.
See the following diagram for a visual representation of this model:
As the proceeding time controls the movement from fulfillment creation to awaiting wave, it is recommended to have the proceeding time value be lower than the reservation time.
If no value is found for the proceeding time (a setting has not been created), the fulfillment will be moved to awaiting wave on the delivery date.
Configuration example
1POST {{fluentApiHost}}/graphql
2
3mutation CreateSetting {
4 createSetting(input: {
5 name: "fc.order.sourcing.proceeding.time",
6 valueType: "INTEGER",
7 value: 24,
8 context: "RETAILER",
9 contextId: 1}) {
10 id
11 name
12 }
13}Update example
1POST {{fluentApiHost}}/graphql
2
3mutation updateSetting {
4 updateSetting(input: {
5 id: 5001464,
6 name: "fc.order.sourcing.proceeding.time",
7 valueType: "INTEGER",
8 value: 24,
9 context: "RETAILER",
10 contextId: 1}) {
11 id
12 name
13 }
14}
15