# Batch Modifications & Reversals Reference

When modifying or reversing action data in bulk, start by downloading one of impact.com’s provided template files and replacing the example data with your own. When adding your own data, be sure to follow the guidelines in the relevant reference table to ensure your file submission is formatted correctly. Once your submission file is ready, you can resume with [submitting your batch modifications / reversals](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-batch-modifications-and-reversals#submit-your-data-file-0-1) file.

{% hint style="info" %}
This reference article includes the most commonly used fields for batch modifications and reversals. To see a full, detailed reference including field descriptions, refer to [Action & Conversion Field References](https://integrations.impact.com/impact-brand/reference/action-conversion-field-references).
{% endhint %}

**See the references below to:**

* Learn which fields to use in an FTP/SMTP batch modification or reversal
* Download template files with placeholder example data
* Understand which reason codes to apply and when

#### Order-level modifications

This is for when you want to update action data in bulk at the order level rather than an item level, e.g., change the order Amount for multiple orders.

<details>

<summary>Accepted parameters</summary>

| Field             | Required?                | Editable?    | Note                                                                                                  |
| ----------------- | ------------------------ | ------------ | ----------------------------------------------------------------------------------------------------- |
| `ActionID`        | Conditionally Required\* | Non-editable | Providing this identifier is recommended when the deduplication window is short.                      |
| `Oid / OrderId`   | Conditionally Required\* | Non-editable | Providing this identifier is required when using *ActionTrackerId*.                                   |
| `ActionTrackerID` | Conditionally Required\* | Non-editable | Providing this identifier is required when using *OrderId/Oid*.                                       |
| `Amount`          | Optional                 | Editable     | Set the new total amount for the order.                                                               |
| `currencyCode`    | Optional                 | Editable     | Set the revenue currency of the action. Defaults to your impact.com account currency if not provided. |
| `CustomerStatus`  | Optional                 | Editable     | Set the customer’s status at the time of conversion, e.g., NEW / EXISTING.                            |
| `Reason`          | Required                 | Editable     | Provide a valid reason code for the modification.                                                     |

\*At least one identifier path must be provided, i.e., either *ActionId* **or** (\*OrderId/Oid \*+ *ActionTrackerId*)

</details>

<details>

<summary>Template files</summary>

* [Order-level modifications template](https://res.cloudinary.com/product-enablement/raw/upload/v1768295823/CSVs/Batch%20Action%20Processing/Order-level_modifications_template.csv)
* [Order-level approvals template](https://res.cloudinary.com/product-enablement/raw/upload/v1768295823/CSVs/Batch%20Action%20Processing/Order-level_approvals_template.csv)

</details>

#### Order-level reversals

This is for when you want to reverse partner-driven actions in bulk at the order level rather than an item level, e.g., reverse multiple orders.

<details>

<summary>Accepted parameters</summary>

| Field             | Required?                  | Editable?    | Note                                                                             |
| ----------------- | -------------------------- | ------------ | -------------------------------------------------------------------------------- |
| `ActionID`        | Conditionally Required\*   | Non-editable | Providing this identifier is recommended when the deduplication window is short. |
| `Oid / OrderId`   | Conditionally Required\*   | Non-editable | Providing this identifier is required when using *ActionTrackerId*.              |
| `ActionTrackerID` | Conditionally Required\*   | Non-editable | Providing this identifier is required when using *OrderId/Oid*.                  |
| `Amount`          | Conditionally Required\*\* | Editable     | Set to **0** to reverse order, unless original amount = 0\*\*                    |
| `Reason`          | Required                   | Editable     | Provide a valid reason code for the reversal.                                    |

\*At least one identifier path must be provided, i.e., either *ActionId* **or** (*OrderId/Oid* + *ActionTrackerId*)

\*\*If original *Amount = 0*, leave *Amount* unchanged to avoid misclassifying as a modification.

</details>

<details>

<summary>Template files</summary>

* [Order-level reversals template](https://res.cloudinary.com/product-enablement/raw/upload/v1768295823/CSVs/Batch%20Action%20Processing/Order-level_reversals_template.csv)

</details>

#### Item-level modifications

This is for when you want to update action data in bulk at the item level rather than an order level, e.g., change the Amount for multiple items in an order.

<details>

<summary>Accepted parameters</summary>

| Field             | Required?                | Editable?    | Note                                                                                                              |
| ----------------- | ------------------------ | ------------ | ----------------------------------------------------------------------------------------------------------------- |
| `ActionID`        | Conditionally Required\* | Non-editable | Providing this identifier is recommended when the deduplication window is short.                                  |
| `Oid / OrderId`   | Conditionally Required\* | Non-editable | Providing this identifier is required when using *ActionTrackerId*.                                               |
| `ActionTrackerID` | Conditionally Required\* | Non-editable | Providing this identifier is required when using *OrderId/Oid*.                                                   |
| `SKU`\*\*         | Required                 | Non-editable | Provide the SKU value of the item you want to modify.                                                             |
| `Amount`\*\*      | Conditionally Required   | Editable     | Set the new item amount, i.e., price\*quantity. If you modify the quantity, this field requires modification too. |
| `Quantity`\*\*    | Optional                 | Editable     | Set the new quantity of items in the order.                                                                       |
| `Category`\*\*    | Optional                 | Editable     | Set the category of the item.                                                                                     |
| `Reason`\*\*      | Required                 | Editable     | Provide a valid reason code for the reversal.                                                                     |

\*At least one identifier path must be provided, i.e., either *ActionId* **or** (*OrderId/Oid* + *ActionTrackerId*)

\*\*These fields must be included for each item you modify. The identifier fields are only included once per order.

</details>

<details>

<summary>Template files</summary>

* [Item-level modifications template](https://res.cloudinary.com/product-enablement/raw/upload/v1768295823/CSVs/Batch%20Action%20Processing/Item-level_modifications_template.csv)
* [Item-level approvals template](https://res.cloudinary.com/product-enablement/raw/upload/v1768295823/CSVs/Batch%20Action%20Processing/Item-level_approvals_template.csv)

</details>

#### Item-level reversals

This is for when you want to reverse action data in bulk at the item level rather than an order level, e.g., reverse multiple items in an order.

<details>

<summary>Accepted parameters</summary>

| Field             | Required?                | Editable?    | Note                                                                                                              |
| ----------------- | ------------------------ | ------------ | ----------------------------------------------------------------------------------------------------------------- |
| `ActionID`        | Conditionally Required\* | Non-editable | Providing this identifier is recommended when the deduplication window is short.                                  |
| `Oid / OrderId`   | Conditionally Required\* | Non-editable | Providing this identifier is required when using *ActionTrackerId*.                                               |
| `ActionTrackerID` | Conditionally Required\* | Non-editable | Providing this identifier is required when using *OrderId/Oid*.                                                   |
| `SKU`\*\*         | Required                 | Non-editable | Provide the SKU value of the item you want to modify.                                                             |
| `Amount`\*\*      | Conditionally Required   | Editable     | Set the new item amount, i.e., price\*quantity. If you modify the quantity, this field requires modification too. |
| `Quantity`\*\*    | Optional                 | Editable     | Set the new quantity of items in the order.                                                                       |
| `Reason`\*\*      | Required                 | Editable     | Provide a valid reason code for the modification.                                                                 |

\*At least one identifier path must be provided, i.e., either *ActionId* **or** (*OrderId/Oid* + *ActionTrackerId*)

\*\*These fields must be included for each item you modify. The identifier fields are only included once per order.

</details>

<details>

<summary>Template files</summary>

* [Item-level reversals template](https://res.cloudinary.com/product-enablement/raw/upload/v1768298926/CSVs/Batch%20Action%20Processing/Item-level_reversals_template.csv)

SKU O7427540 appears twice in this example because one line is reversing (Amount=0) and one is modifying (Amount=15).

</details>

{% hint style="info" %}
**Note:** If you anticipate having duplicate *OrderIds* and opt to use the combination of *OrderId + ActionTrackerId*, impact.com applies your update to the newest *ActionId* by default. Use the old *ActionId* if you want to apply the update to the older *ActionId*.
{% endhint %}

#### Reason Codes

Every time you modify or reverse action data, you must provide a reason. Use the relevant reason code below to explain why the action is being updated.

{% hint style="warning" %}
**Warning:** Passing a non-accepted value will result in the entry not being processed and returning an error instead. If you need custom reason codes, reach out to your CSM or [**contact support**](https://app.impact.com/support/portal.ihtml?createTicket=true&) **to discuss Disposition Codes**.
{% endhint %}

<table><thead><tr><th width="234">Code</th><th>Description</th></tr></thead><tbody><tr><td><code>CONS_FRAUD</code></td><td>Consumer fraud</td></tr><tr><td><code>CONS_ERROR</code></td><td>Consumer error</td></tr><tr><td><code>ITEM_RETURNED</code></td><td>Item was returned</td></tr><tr><td><code>APPROVED</code></td><td><p>Action is approved</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note:</strong> If you’re trying to approve actions, <code>Approve</code> needs to be set up as a <a href="../../tracking/set-up-tracking/manage-disposition-codes">custom disposition code</a>.</p></div></td></tr><tr><td><code>ORDER_ERROR</code></td><td>Order error</td></tr><tr><td><code>ORDER_UPDATE</code></td><td>Order was updated</td></tr><tr><td><code>PUB_ACT_DISPUTE</code></td><td>Partner activity dispute</td></tr><tr><td><code>ADV_ACT_DISPUTE</code></td><td>Brand activity dispute</td></tr><tr><td><code>NOT_COMPLIANCE_TERMS</code></td><td>Not in compliance with terms</td></tr><tr><td><code>ITEM_OUT_OF_STOCK</code></td><td>Item is out of stock</td></tr><tr><td><code>TEST_ACTION</code></td><td>Test action</td></tr><tr><td><code>PARTNER_NOT_ACTIVE</code></td><td>Partner account deactivated</td></tr><tr><td><code>CREDITED_DIFFERENT_MP</code></td><td>Credited to another partner</td></tr><tr><td><code>OTHER</code></td><td>Other reason</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/batch-modify-conversion-data/batch-modifications-and-reversals-reference.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
