Order Status

order status overview order status provides forter with the most up to date information about the status of individual orders the purpose of this job is to allow forter's machine learning models to understand if the order was completed/delivered or it was rejected/canceled at a later phase receiving the status of every order also updates forter on unshipped/canceled orders which allows for automated, accurate billing improves forter's ability to catch sophisticated fraudsters (it is a common practice for fraudsters to cancel the first order at a later phase) creates an accurate benchmark to capture the real dollar value forter is creating for your business provides feedback to approve even more legitimate customers defines the window of time within which forter can notify the merchant of fraud rings order status from sfcc oms order status from your sfcc platform if you currently receive the order status and updates to existing transactions (shipped, completed, cancelled, etc ) available in your sfcc store platform, you’ll want to enable the forter order update job order status for pre auth integrations in the case of pre auth integrations where the forter decision is returned prior to the payment processor authorizing payment the order status call should be made immediately after payment is authorized and the status should include the authorization response from the gateway (including authorization rejections) please see our dedicated \[pre auth paths section]\( /checkout/pre auth credit card/sfra md) to review recommended mapping of the authorization response and instructions for including the order status during the time of purchase scheduling and editing the order update job for merchants on a post auth integration and to provide downstream, post purchase order status data, there is a built in order status automation the order update job checks for an sfcc order status change, and sends it to the relevant forter api endpoint via https it is recommended that the job be run every 6 hours please note that in the custom site preferences section you can configure the parameter number of weeks that is used by this job to determine the time range (number of weeks) that the job queries in order to update order status the default value is 4 weeks to access the forterorderupdate job, you can go directly to administration > operations > job schedules > forterorderupdate order void job (optional) if you are on an pipelines or older version/non sfra of the sfcc platform, you can use the order void job to automatically void declined orders in your sfcc oms depending on the configuration of the site preferences, you can choose to keep orders for which forter returned a "decline" decision in order to review them depending on the payment gateway you have and how it is integrated, you may be able to use this job to void the payments of those orders and cancel the order after 24 hours forter recommends scheduling this job to run every 24 hours to schedule and edit this recurring job, you can go directly to administration > operations > job schedules order status from an external oms if the status of your orders is done through a separate or external oms, please see forter's # order status api documentation for all relevant information and options for sending the relevant order statuses to forter