Orders in an Integrated System

When Salesforce B2C Commerce and Order Management are integrated, two types of sales orders are considered:

Website orders, including pricing and tax data, are integrated into Order Management via automated tasks (legacy connector) or API calls (new integration). They then proceed through the order lifecycle without further connection to B2C Commerce. Orders entered in Customer Service Center can initially retrieve pricing or product data from B2C Commerce, but don't otherwise interact with the website front end.

B2C Commerce orders usually appear in Order Management within two minutes of entering New or Open status. Longer delays can indicate a problem.

Other useful information about order integration:

Controlling the Integration Workflow of Individual Orders

The integration picks up any orders in New or Open status in B2C Commerce and brings them into Order Management. You can prevent an order from being integrated by keeping it in Created status. This delay allows for any processing that must happen before the order is handled in Order Management. For example:

An alternative method is to let an order be integrated into Order Management, but set up a custom hook to hold the order for further processing. For example, an order that fails its fraud check is allowed to be integrated, but has its fraud check status set to error. A custom hook in Order Management recognizes this status and keeps the order in the Waiting Approval state for manual intervention.

Shipping Methods

For the new integration, map B2C Commerce shipping methods to Order Management shipping methods in the B2C Commerce Business Manager. If you are using the legacy connector, you must map B2C Commerce shipping method codes to Order Management shipping method names in the Demandware provider. When planning your integration, ensure that all shipping methods used by your company are available and configured in both B2C Commerce and Order Management.

Payment Methods

Before running an integrated system, map B2C Commerce payment method codes to Order Management Payment Method IDs in the Demandware provider. As part of your integration planning, ensure that all payment methods used by your company are available and configured in both B2C Commerce and Order Management. If payments or payment transactions include custom attributes, name them the same in Order Management and B2C Commerce and associate them with the appropriate object types. If you don't configure these custom attributes, Order Management ignores them.

When an order is integrated into Order Management, the payment method is determined according to the following order of priority:

  1. If the omPaymentInstrumentMethod attribute has been set on the payment in B2C Commerce, then that payment method is used. Otherwise, the payment_method field on the order record is used.
    Note: These fields are not case-sensitive.
  2. The system checks the value against the known payment method IDs listed in the following table. If it matches, then that method is used.
  3. If the value doesn't match a known method, the system treats it as a custom payment method, using the value as the method name.
  4. If no matching custom payment method exists in Order Management, then an exception is thrown.

Order Management recognizes the following default payment method IDs and associated payment processor IDs:

Payment Method ID Associated Payment Processor IDs
bank_transfer (See Below for override attributes)
  • N/A
  • cybersource_credit
  • moneris_credit
  • cybersource_credit
  • moneris_credit
credit_card (See Below for override attributes)
  • authorizenet
  • first_data_global_gateway
  • cybersource_credit
  • moneris_credit
  • cybersource_credit
  • moneris_credit
  • givex_credit
gift_certificate (See Below for override attributes)
  • N/A
Payment methods mapped in the Demandware provider
  • paypal_express
  • ads

Certain payment methods offer extra attributes that can be used to override the values normally included in the order data. These attributes must be specified at the payment level. The following tables describe them.

Note: The payment data can include other attributes related to these payment methods. Order Management ignores them unless you configure them in the Order Management Attribute Manager and associate them with the appropriate object type (payment or payment transaction).


Attribute Description
omBankAccountHolder Overrides the standard property.
omBankAccountNumberMasked Stored in the AccountNumber field in Order Management.
omBankRoutingNumber Overrides the standard property.


Attribute Description
omCreditCardExpirationMonth Overrides the standard property.
omCreditCardExpirationYear Overrides the standard property.
omCreditCardHolder Overrides the standard property.
omCreditCardNumberLastFourDigits Stored in the CardNumberMasked field in Order Management unless omCreditCardNumberMasked is also included, in which case this value isn't used. If a plain-text credit card number is detected in this field, an exception is thrown.
omCreditCardNumberMasked Stored in the CardNumberMasked field in Order Management. If a plain-text credit card number is detected in this field, an exception is thrown.
omCreditCardType Overrides the standard property. The system makes the following value conversions:
  • VISA -> Visa
  • MASTER -> MasterCard
  • AMEX -> AmericanExpress
  • DISCOVER -> Discover
Other values are passed through unchanged.


Attribute Description
omGiftCertificateCode Overrides the standard property.

Data Mappings

The order data mapping between B2C Commerce and Order Management is documented in these topics:

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.