---
title: "Add order details from Shopify to Transaction Related Data Table"
slug: "add-order-details-from-shopify-to-transaction-related-data-table"
updated: 2024-03-18T10:37:51Z
published: 2024-03-18T10:37:51Z
canonical: "docs.mapp.com/add-order-details-from-shopify-to-transaction-related-data-table"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add order details from Shopify to Transaction Related Data Table

In this How-To, we will show you how to add order details from Shopify (or another eCommerce data provider) to Transactional Related Data Table.

1. [Create a new Zap](/v1/docs/create-a-new-zap) and choose **Shopify**. ![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/6dc2ddcb-e77c-46de-9a42-dbef60ef0b8d.png)
2. Choose **Mapp Connect** and **Create Transaction Event.**

*![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/6cb6e81f-6903-4084-b50e-2694e43fb307.png)*
3. Mapping for transactions is set by default between Mapp Engage and Zapier so you need to provide a source from Shopify data fields.

![](https://cdn.document360.io/554b9b98-6720-4d8b-9919-c7b203d72648/Images/Documentation/794da5d4-a48e-4a36-91cf-b3b9ced3bd6c.png)

**Fields mapping**

| Source | Mapp Engage | Required | Description | Type |
| --- | --- | --- | --- | --- |
| Email | email | YES | User email is changed to **userId.** If the user is not in the system, they will be added. | string |
| UserId | userId | no | User email is changed to **userId.** If the user is not in the system, they will be added. | string |
| OrderId | orderId | YES | Identification of this order | number |
| Timestamp | timestamp | NO | If the timestamp is not provided, it saves time from an incoming call. | datetime |
| StoreId | storeId | NO | For multi-shop purposes | string |
| Currency | currency | NO | The default currency is set in transactional related data. If not provided here, default currency is assigned. | string |
| ProductSKU | productSKU | YES | Product identifier (stock-keeping unit) | string |
| ProductPrice | productPrice | YES | Product price: number only, without currency and spaces. | number |
| ProductQuantity | productQuantity | YES | Quantity of this product in this order. | number |
| ImageURL | imageURL | NO | Link (URL) to the product image. | string |
| ProductURL | productURL | NO | Link (URL) to the product page. | string |
| Category | category | NO | Category of this product. | string |
| Brand | brand | NO | Brand of this product. | string |
| Variant | variant | NO | Use this field if the **productSKU** does not provide variant, such as colour, material, or size. | string |
| DiscountValue | discountValue | NO | Value (without currency) of discount **per order** (not per item) | number |
| DiscountPercent | discountPercent | NO | The percentage value of discount **per order** (not per item) - value from 0 to 1 | number |
| PurchaseSource | purchaseSource | NO | Source (campaign name, Facebook, and so on) of this order | string |
| customDetail1 | customDetail1 | NO | Custom transactional details need to be first defined in Transactional Related data structure and added to mapping. | defined by the Related Data structure that you have in place |