Field mapping

Jota includes default mappings, so most fields sync without any changes. Customize them when your org uses its own fields or your teams need extra data.

Mappings work in each direction separately. Open both from the Home page in Jota:

• Shopify to Salesforce mapping controls what Jota writes to Salesforce.
• Salesforce to Shopify mapping controls what Jota writes to Shopify.

Shopify to Salesforce

1. Open Shopify to Salesforce mapping.
2. Choose a Shopify resource.
3. Change, add, or remove mappings. Each row pairs a Shopify field with a Salesforce field.
4. Select Save mapping.

Shopify resource	Salesforce objects
Customer	Lead, Contact, and Account
Order	Opportunity and Opportunity Line Item
Draft order	Opportunity and Opportunity Line Item
Product	Product and Price Book Entry
Catalog pricing	Price Book Entry
Company	Account
Company location	Account

Jota manages Opportunity Line Item and Price Book Entry fields on the order, draft order, and product resources with its standard mapping, so you can’t edit those rows. Shopify IDs and required Salesforce relationships also stay under Jota’s control so that updates don’t create duplicates.

To go back to the defaults for a resource, select Delete mapping.

Match existing Contacts

Under Customer → Contact match field, choose the Salesforce field Jota uses to find an existing Contact. You can choose from the fields mapped on the Contact tab. Existing Contacts are reused rather than duplicated.

Create Leads for new customers

Select Create customers without orders as Leads to send customers who haven’t ordered yet to Lead rather than Contact. When the customer places their first order, Jota converts the Lead to an Account and Contact. B2B customers keep their company Account.

• Initial Lead status sets the status of new Leads, or uses your org’s default.
• Salesforce’s active Lead assignment rule runs when each Lead is created.
• Owner for Leads assigned to queues is required if your assignment rule can send Leads to a queue, because Salesforce can’t convert a queue-owned Lead without a user owner.

Leads are matched by Shopify customer ID, then by email.

Assign record types

Under Record type assignment, choose a Write target, then select Enable rules to set record types based on the Shopify data.

1. Add a rule with one or more Match conditions.
2. Choose the Salesforce record type to assign.
3. Choose what happens when no rule matches, separately for creating and updating records.

For Opportunities, you can also choose the Open stage, Closed won stage, and Closed lost stage for each record type. Sync history shows the decision Jota made for each event.

Shopify SKUs

Shopify allows two variants to share a SKU, but Salesforce doesn’t allow duplicates in Stock Keeping Unit. Jota maps variant SKUs to its own non-unique SKU field on the Product instead.

Salesforce to Shopify

These mappings apply when Jota writes to Shopify: customers, draft orders, and, with Jota B2B, companies and company locations.

1. Open Salesforce to Shopify mapping.
2. Choose the Shopify resource.
3. Choose a Salesforce source field and a Shopify target type.
4. For a standard field, choose the Shopify field. For a metafield, enter its Namespace, Key, and Type.
5. Select Save mapping.

Company location defaults

With Jota B2B, the Company location resource also has Buyer experience defaults: Payment terms, Shipping address at checkout, and Order submission. These apply to every company location. To override them for individual locations, map a Salesforce field to the matching Shopify field.