Salesforce B2C Commerce provides data maps to illustrate how the platform’s data is recorded within Salesforce Order Management. This is particularly helpful if you are implementing your very own storefront integration, because it can clarify the requirements of order data.
When considering the organization of order data there are a few generalities that are worth keeping in mind to get your ball bearings straight if you’re a relative newbie to the platform or just curious as to the setup of the platform.
These include such things like B2C Commerce Cloud sends orders that have a status of New or Open to Salesforce Order Management. By keeping it in the status Created you are able to do things like delay sending an order or make a fraud check.
Also to keep in mind is that B2C Commerce Cloud sends order data over to Salesforce Order Management under certain circumstances that include 1) according to a set frequency and 2) when a bunch of pending orders reaches a certain size. Furthermore, every 5 minutes the integration connects with B2C Commerce to request the data of any pending orders.
And finally, Salesforce Order Management will always use a standard account and contact to represent the consumer if the value for the order, billing address, and company name is not null.
International order considerations
Next up, there are considerations to bear in mind for orders that are made internationally, and which are only applicable to them.
These include when an order value is net, the integration will create an OrderItemTaxLineItem value that corresponds to every OrderItem and every OrderItemAdjustmentLineItem.
If the fields of the state and country are not enabled, then the state code values in order data has to match a standard ISO of 2 characters for the state or for the province. The integration then copies them to the State field in its records. Also, the country code values in order data has to match a standard ISO of 2 characters for the country, and then copies them to the Country field.
If the fields of the state and country are enabled, then the state values in order data has to match the state code of an entry in Salesforce’s picklist. The integration then copies them to the State field, which matches the integration values from the picklist. In addition, the country values in order data has to match the country code of an entry in Salesforce’s picklist. The integration then copies them in the Country field, which matches the integration values from the picklist.
When it comes to the data of payments, there is a lot of communication between Salesforce B2C Commerce Cloud and Salesforce Order Management. And the reasons for this are long, which include the following.
If an order or payment value in the order data begins with auth then a PaymentAuthorization is created for the transaction. If the value is sale or capture, then a Payment record is created. In these cases they are not case-sensitive.
Another scenario is when the order data includes a payment instrument that is paired and the payment for each one is connected with the other.
A third scenario is when a payment method doesn’t connect with a DigitalWallet or CardMaymentMethod CardType. In this scenario a custom payment method must be created.
Fourthly, when a card payment type (whether it be debit or credit) is used, the payment value has to match with a value in the CardType picklist.
Finally, when the integration recognizes certain custom attributes when it comes to payment, it copies them to standard fields on the PaymentGatewayLog in Salesforce.
Then there is promotional data, which can be part of a campaign or a stand alone, targeted promotion. The integration of SFB2C and Salesforce Order Management creates an OrderAdjustmentGroup record for each promotion included in the order data. For each of these, it makes an OrderItemAdjustmentLine record corresponding to each item that a promotion applied to.
And finally, if the value of an order is net, then an OrderItemTaxLine record is created for each item that it applies to.