---
title: "Transaction Feed"
slug: "transaction-feed-mapp-fashion"
status: "update"
updated: 2026-08-05T08:20:40Z
published: 2026-08-05T08:20:42Z
canonical: "docs.mapp.com/transaction-feed-mapp-fashion"
---

> ## 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.

# Transaction Feed

## Introduction

The Transaction Feed provides Mapp with order and return data for use in analysis and product recommendations. It contains details about the products purchased or returned by customers.

You need to send Mapp an ongoing Transaction Feed so that recommendations and analysis are based on real purchase behavior.

---

## Transaction Feed Format and Delivery

Mapp requires an ongoing Transaction Feed containing order lines, updated daily. Each file should include transactions that occurred since the previous extract, including purchases and returns.

In addition to the daily feed, a one-off historical extract is required. This historical file should cover at least the previous 12 months of transactions and is used to train the recommendation system and support analysis.

Only product data from categories relevant and in scope should be included.

The file name must be consistent and include a timestamp in the `YYYYmmDDHHMM` format.

---

### CSV format

The Transaction Feed must be provided in CSV format.

CSV files must:

- Include a header row
- Contain one row per item purchased
- Include a separate row for each instance of the same item, or aggregate units of the same variant using the `Quantity` column (see below)
- Use a unique, incrementing `EntryId` per order, starting at 1

Each item must be uniquely identifiable using `OrderId` and `EntryId`. If multiple instances of the same product are purchased in a single order, either give each its own entry, or combine identical variants bought at the same price into a single row and set `Quantity` to the number of units.

#### Example CSV structure

```plaintext
OrderId,CustomerId,EntryId,ProductId,EAN,Channel,StoreCode,Price,Discount,Currency,OrderDate,ReturnDate
123-456,ABC-123456,1,ABC,123456,online,,15.00,0.00,GBP,2023-01-05T14:30:00.000Z,
123-456,ABC-123456,2,ABC,123456,online,,15.00,0.00,GBP,2023-01-05T14:30:00.000Z,2023-01-08T10:00:00.000Z
```

Alternatively, units of the same variant bought at the same price can be combined into a single row using a `Quantity` column:

```plaintext
OrderId,CustomerId,EntryId,ProductId,EAN,Channel,StoreCode,Price,Discount,Quantity,Currency,OrderDate,ReturnDate
123-456,ABC-123456,1,ABC,123456,online,,15.00,0.00,3,GBP,2023-01-05T14:30:00.000Z,
```

---

### Data handling requirements

Please ensure that:

- Literal double quotes and commas in attribute values are correctly escaped
- Files are encoded in UTF-8 without a BOM
- Product and customer identifiers are validated and match those used elsewhere

---

### Personal data

In line with GDPR obligations, personal data must be omitted from the Transaction Feed unless prior arrangements have been made.

---

### Attributes

The Transaction Feed includes attributes describing orders, items, pricing, and dates.

For a complete list of supported fields and definitions, see the [Attributes Reference](/v1/docs/attributes-reference-1).

---

### Delivery

You transfer files to Mapp Fashion via SFTP. Mapp Fashion provides SFTP credentials, or alternatively polls your SFTP server.

If you operate IP allowlisting, our IP addresses will need to be permitted access.

## Related

- [Transaction Feed Attributes Reference](/attributes-reference-mapp-fashion.md)
- [Transaction Feed FAQs](/transaction-feed-faqs.md)