Custom B2C Commerce Storefront Data Integration

Only the B2C Commerce attribute ID and the Order Management field name at the API level are compared. UI labels aren’t considered.

If order data includes a custom attribute value but the corresponding Salesforce object has no matching custom field, the attribute is ignored. If a custom field exists in Salesforce and order data doesn’t include a matching custom attribute value, the field is ignored.

Also consider datatype compatibility between your storefront and Salesforce. All text values in order data that exceed the size of the corresponding field in Salesforce by three characters less than the datatype size limit and appends three periods (...). For example, if order data includes the value Albuquerque for a custom field with a maximum length of 10 characters, the value is stored as Albuque... in Salesforce.

Important If a custom field in Salesforce is required, and it corresponds to a custom storefront attribute, order data must include a value for that attribute. Otherwise, Order Management can’t create the corresponding Salesforce record and an error occurs.

At the API level, Salesforce custom field names always end in __c. Don’t include __c in the names of the matching attributes on your storefront objects. However, if you include a custom namespace in a custom field name, also include it in the name of the matching storefront object attribute. For example, if the API name of your custom field in Salesforce is mynamespace_FieldName__c, name your matching storefront object attribute mynamespace_FieldName. Limit your custom field names to 40 characters (37 plus __c).

You can use matching custom attributes and fields on these objects.

We don’t support custom object mapping or custom object lookup. If you try to map a custom attribute with a custom object lookup, the mapping fails.