Order Preferences

You can select how orders are processed with Salesforce B2C Commerce.

Some order preferences can be imported and exported.
  1. Select site > Merchant Tools > Site Preferences > Order.
  2. Configure order export settings.
    1. Enter the delay in minutes, after which an order can be considered for export.
      The default is 30 minutes.
    2. To delay the exporting of an order once the order has been opened for editing, enter the amount of time in minutes.
      The default is 30 minutes.
    3. Enter the version of the XML schema (order.xsd) to use for order export.
      You can select the most recent version of B2C Commerce or remain on a specific version, if necessary.
  3. Enable Order IP Logging if you want to store the customer IP addresses during order creation.
    First determine if you are legally required to inform the customer about storing this type of information.
  4. Configure order data settings.
    1. Enter the number of days B2C Commerce stores orders (Order Retention).
      Orders older than the specified number of days are automatically removed from B2C Commerce. To retain orders, leave this setting blank.
    2. Enter the number of days B2C Commerce stores failed orders (Failed Order Retention).
      Failed orders older than the specified number of days are automatically removed from B2C Commerce. To retain failed orders (unless the Order Retention preference is set), leave this setting blank.
    3. Select whether to preserve orders that have not yet been exported (Retain Non-Exported Orders)
      If set to Yes, an order in status NEW, OPEN, or COMPLETED is purged. However, the order is purged only if the order export status is EXPORTED when the purge job is executed. Orders in status CREATED, FAILED, CANCELLED, or REPLACED are purged regardless of the export status. This setting in only relevant if 'Order Retention' is enabled.
  5. Enter the number of days from 1 through 365, after which B2C Commerce masks order payment information (Payment Information Retention).
    Order payment instruments older than the specified number of days are automatically masked. Masking these instruments ensure that the original credit card and bank account numbers are not recoverable. This masking is permanent and can't be undone if the number of days is changed later. The default is 30 days.
  6. Enter the number of minutes after an order has not been placed when the order is eligible for automatic failing (via a job).
    Leave this blank if orders are never to be auto-failed.
  7. Specify if access to orders from the storefront is limited.
  8. Specify whether to validate storefront order searches against the session customer. Set to Yes unless you have a specific reason to disable this validation.
    Yes or No
  9. Specify if customer numbers are generated for orders placed by unregistered customers.
    If set to Yes, a customer number is generated for orders placed by unregistered buyers, no matter how the order is created: via script API, OCAPI, or pipelets (CreateOrder or CreateOrder2). If set to No, and if the Script API or OCAPI creates the order, a customer number is not generated. When pipelets create the order (CreateOrder or CreateOrder2), the corresponding pipelet configuration parameter specifies whether a customer number is generated for guest orders.
  10. Configure order calculation rounding.

    Select Item Price Rounding or Item-Level Rounding. This setting is applied for net and gross sites, and the B2C Commerce Script API and OCAPI.

    Also enable the promotion site preference.

  11. Specify whether to include orders in this site in Order Management. To enable, Order Management integration must be enabled.
  12. Specify how inventory and coupon redemptions are handled. If inventory cannot be reserved or coupons cannot be redeemed, the respective order history entries are written.
    1. Specify whether to turn failed orders into valid orders, even if there is no inventory available for a reservation, known as overselling.
    2. Specify whether to turn canceled orders into valid orders, even if there is no inventory available for a reservation, known as overselling.
    3. Specify whether to turn failed orders into valid orders, even if not all coupons can be redeemed. Unsuccessful coupon redemptions result in having coupons used more often than configured.
    4. Specify whether to turn canceled orders into valid orders, even if not all coupons can be redeemed. Unsuccessful coupon redemptions result in having coupons used more often than configured.
  13. Click Apply.
X Privacy Update: We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used. By continuing to use this site you are giving us your consent to do this. Privacy Policy.