> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-conversion-data/submit-new-skus-after-conversion.md).

# 转化后提交新 SKU

在某些情况下，用户在订单已被跟踪后仍可返回该订单并添加更多产品。在这些情况下，您可以通过 FTP 将新产品提交到 impact.com，以便为您执行 UPSERT。了解更多关于 [通过 FTP 提交转化数据](/brand/zh/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-conversion-data/submit-conversion-data-via-ftp-or-email.md)。如果您在此过程中需要更多帮助，请联系您的 CSM（或 [联系支持团队](https://app.impact.com/support/portal.ihtml?createTicket=true)).

#### 要求

在 impact.com 中，订单的开放、已计费记录必须已存在。任何尝试将项目 UPSERT 到已锁定订单的操作都会失败。

{% stepper %}
{% step %}

#### 准备您的数据

您可以使用下面的 .csv 模板来帮助构建数据。第 2 行和第 3 行中的示例值应替换为您自己的数据。

```programlisting
ActionTrackerId,订单ID,货币代码,金额,类别,Sku,数量,原因,方式
12345,1076543345142,USD,123.50,新增商品类别,新增商品,新增商品Sku,12,订单更新,UPSERT
12346,1076543345143,USD,98.50,新增商品类别,新增商品,新增商品Sku,11,订单更新,UPSERT
 
```

{% endstep %}

{% step %}

#### 提交您的数据文件

请参阅 [通过 FTP 提交转化数据](/brand/zh/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-conversion-data/submit-conversion-data-via-ftp-or-email.md) 如需帮助将您的 FTP 数据提交到 impact.com。
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**注意：** 对最初订单应用的任何折扣都不会被重新处理。
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-conversion-data/submit-new-skus-after-conversion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.