Order Fulfillment Flow Configuration

There are several configuration properties available for order fulfillment flows, which control:

Enables automatic reverse authorizing / refunding of payment on a fulfillment after it’s been cancelled.

Note that the reverse authorize transaction for the payment is not executed until the entire order has been fully captured and/or cancelled. By waiting to reverse all of the related authorizations, we can simply reverse authorize all the unused authorized amount.

Enables automatic reverse authorizing of any remaining authorized but non-captured payments on an order whenever the last fulfillment is fulfilled.

When a CSR hits "Capture Payment and Fulfill Items" for a fulfillment in the admin, this property ensures that the corresponding fulfillment is automatically be shifted into the FULFILLING or FULFILLED status (depending on other configuration).

Note: when this action is engaged, we start by changing the status of the fulfillment to CAPTURING_PAYMENT, see Capturing Payment Status to trigger the payment capturing portion of the process.

Enables automatic fulfillment of VIRTUAL goods following a successful checkout. This will automatically capture payment for the fulfillment as a prerequisite, and immediately moves the fulfillment into the FULFILLING or FULFILLED status (depending on other configuration) after.

If true, during auto-fulfill, VIRTUAL fulfillments will go through the FULFILLING status before they can be marked as FULFILLED.This will allow external systems to perform virtual fulfillment processes.

That system must be responsible for notifying this service to change the status to FULFILLED once fulfillment is complete.

This should have the same value as broadleaf.order.metadata.enable-fulfilling-step in OrderServices. (see Order Services Configuration)

Declares if components required to handle asynchronous capture and refund payment transactions are enabled. This should only be enabled if your project includes a payment gateway that only returns capture and refund transaction results asynchronously. Related components: FulfillmentCaptureWebhookListener and ReturnConfirmationRefundWebhookListener

Declares whether or not to distribute a payment transaction amount across the Order’s payments proportionally.

Enables automatic payment capture for VIRTUAL goods following order creation. Immediately moves the fulfillment into the CAPTURING_PAYMENT status, which will trigger payment capture.