---
schema_version: "1"
id: f38005e72c7843ab29e342c93e2aebb8901fe3f5341f081bd9219a42c2909616
title: Object Mappings
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/retail/latest/cim-mappings.md
canonical_url: https://docs.mulesoft.com/retail/latest/cim-mappings
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 7c737e2a78cd055b6b463942b6e53f53fb615f224a9c02ccbab0c19e556f1efb
description: MuleSoft Documentation Site
release: "3.2"
latest: true
---
---
product: Retail
version: 3.2
is-latest-version: true
---

# Object Mappings

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

## Customer profile sync

### Source-type mappings

The following table summarizes how representations of a customer or individual from each system will
be mapped to CIM types:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Source System</th><th>Source Type</th><th>CIM Types</th><th>Mapping Notes</th></tr></thead><tbody><tr><td><p>B2C Commerce</p></td><td><p>Customer Profile</p></td><td><p>Individual Customer</p><p>Contact Address</p><p>Contact Email</p><p>Contact Phone</p></td><td><p>One B2C customer profile will map to multiple CIM objects</p></td></tr><tr><td rowspan="3"><p>B2B Commerce Sales Cloud Service Cloud</p></td><td><p>Person Account</p></td><td><p>Individual</p><p>CustomerContactAddress</p><p>Contact Email</p><p>Contact Phone</p></td><td><p>Person Account is represented as record type, mapping to Account and Contact</p></td></tr><tr><td><p>Account</p></td><td><p>OrganizationCustomerContact Address</p><p>Contact Email</p><p>Contact Phone</p></td><td><p>Account is mapped separately from Contacts</p></td></tr><tr><td><p>Contact</p></td><td><p>Individual</p><p>Contact Address</p><p>Contact Email</p><p>Contact Phone</p></td><td><p>Similar mappings as for Person Accounts but at the Individual level only</p></td></tr><tr><td><p>Marketing Cloud</p></td><td><p>Subscriber</p></td><td><p>Individual</p></td><td><p>Requires a data extension</p></td></tr><tr><td><p>SAP</p></td><td><p>Customer</p></td><td><p>IndividualCustomer</p><p>Contact Address</p><p>Contact Email</p><p>Contact Phone</p></td><td></td></tr></tbody></table>

### Target-type mappings

The following table summarizes how representations of a customer or individual from each system will
be mapped from CIM types:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Target System</th><th>CIM Type</th><th>Target Types</th><th>Mapping Notes</th></tr></thead><tbody><tr><td><p>B2C Commerce</p></td><td><p>Customer</p><p>Individual</p><p>Contact Address</p><p>Contact Email</p><p>Contact Phone</p></td><td><p>Customer</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>MDM</p></td><td><p>All Types</p></td><td><p>Corresponding type</p></td><td><p>1:1 mappings; use join tables for relationships</p></td></tr><tr><td rowspan="3"><p>B2B Commerce Sales Cloud Service Cloud</p></td><td><p>CustomerIndividual</p><p>Contact Address</p><p>Contact Email</p><p>Contact Phone</p></td><td><p>PersonAccount</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>CustomerOrganization</p><p>Contact Address</p><p>Contact Email</p><p>Contact Phone</p></td><td><p>Account</p></td><td><p>Address fields mapped directly</p></td></tr><tr><td><p>Individual</p><p>Contact Address</p><p>Contact Email</p><p>Contact Phone</p></td><td><p>Contact</p></td><td><p>Similar mappings as for Person Accounts but at the Individual level only</p></td></tr><tr><td><p>Marketing Cloud</p></td><td><p>Individual</p></td><td><p>Subscriber</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>SAP</p></td><td><p>CustomerIndividual</p><p>Contact Address</p><p>Contact Email</p><p>Contact Phone</p></td><td><p>Customer</p></td><td><p>Relevant fields only</p></td></tr></tbody></table>

## Sales order sync

### Source-type mapping

The following table summarizes how representations of a sales order from each system will be mapped
to CIM types:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Source system</th><th>Source type</th><th>CIM Types</th><th>Mapping notes</th></tr></thead><tbody><tr><td><p>B2C Commerce</p></td><td><p>Order</p></td><td><p>SalesOrder</p><p>SalesOrderProduct</p></td><td><p>Order line items added as sales order products</p></td></tr><tr><td><p>OFBiz</p></td><td><p>Order</p><p>OrderLineItem</p></td><td><p>SalesOrder</p><p>SalesOrderProduct</p></td><td><p>TBD</p></td></tr><tr><td><p>SAP</p></td><td><p>Order</p></td><td><p>SalesOrder</p><p>SalesOrderProduct</p></td><td><p>Order line items added as sales order products</p></td></tr><tr><td><p>Salesforce</p></td><td><p>TBD</p></td><td><p>SalesOrder</p></td><td><p>TBD</p></td></tr></tbody></table>

### Target-type mapping

The following table summarizes how representations of a sales order from each system will be mapped
from CIM types:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Target system</th><th>CIM type</th><th>Target Types</th><th>Mapping notes</th></tr></thead><tbody><tr><td><p>B2C Commerce</p></td><td><p>SalesOrder</p></td><td><p>Order</p></td><td><p>Order status update only</p></td></tr><tr><td><p>OFBiz</p></td><td><p>SalesOrder</p><p>SalesOrderPRoduct</p></td><td><p>Order</p><p>OrderLineItems</p></td><td><p>Order status update only</p></td></tr><tr><td><p>SAP</p></td><td><p>SalesOrder</p><p>SalesOrderProduct</p></td><td><p>Order</p><p>OrderLineItems</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>Salesforce</p></td><td><p>SalesOrder</p></td><td><p>TBD</p></td><td><p>TBD</p></td></tr></tbody></table>

## Product sync

### Source-type mapping

The following table summarizes how representations of a product from each system will be mapped to
CIM types:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Source System</th><th>Source Type</th><th>CIM Types</th><th>Mapping Notes</th></tr></thead><tbody><tr><td><p>B2C Commerce</p></td><td><p>Product</p></td><td><p>Product</p><p>ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>OFBiz</p></td><td><p>Product</p></td><td><p>Product</p><p>ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>SAP S/4HANA</p></td><td><p>Product</p></td><td><p>Product ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>Salesforce</p></td><td><p>Product</p><p>Pricebook</p></td><td><p>Product</p><p>ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>PIM</p></td><td><p>Product</p><p>ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>Product</p><p>ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>1:1 mappings; use join tables for relationships</p></td></tr></tbody></table>

### Target-type mapping

The following table summarizes how representations of a product from each system will be mapped from
CIM types:

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Target System</th><th>CIM Type</th><th>Target Types</th><th>Mapping Notes</th></tr></thead><tbody><tr><td><p>B2C Commerce</p></td><td><p>Product</p><p>ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>Product</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>OFBiz</p></td><td><p>Product</p><p>ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>Product</p><p>ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>SAP S/4HANA</p></td><td><p>Product</p><p>PriceBook</p></td><td><p>Product</p><p>PricingCondition</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>Salesforce</p></td><td><p>Product</p><p>ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>Product</p><p>PriceBook</p></td><td><p>Relevant fields only</p></td></tr><tr><td><p>PIM</p></td><td><p>Product</p><p>ProductCategory</p><p>ProductCatalog</p><p>PriceBook</p></td><td><p>Product</p></td><td><p>Relevant fields only</p></td></tr></tbody></table>

## See Also

- [Prerequisites](https://docs.mulesoft.com/retail/latest/prerequisites)

- [MuleSoft Accelerator for Retail](https://docs.mulesoft.com/retail/latest/)