> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/agentic-commerce/esw-agentic-discovery/faqs.md).

# FAQs

Resolve common catalog upload and product discovery questions.

### Uploading catalogs

<details>

<summary>Where do I upload my catalog?</summary>

Upload to your assigned tenant folder through SFTP. Use the exact brand code, environment, and `ProductFeed/Pending` path provided by ESW. Confirm the folder with your ESW Customer Success Manager if needed.

</details>

<details>

<summary>Can I upload multiple files for one market?</summary>

No. Send one CSV per market. Include every product for that market. Do not split files by category, brand, or action type.

</details>

<details>

<summary>What belongs in my first upload?</summary>

Include every active, in-stock product you want discoverable in Microsoft Copilot. Include required fields and useful selling points, features, category, material, and intended use.

</details>

<details>

<summary>What format do I need?</summary>

Send a UTF-8 CSV. Populate mandatory fields for each product category. Validate the file before upload.

</details>

### Timing and markets

<details>

<summary>When do products appear in Microsoft Merchant Center and Copilot?</summary>

Allow up to 72 hours after successful upload. Upload at least four days before launches, campaigns, or price changes.

</details>

<details>

<summary>Which markets support Microsoft Copilot purchases?</summary>

Microsoft Copilot purchasing currently supports the United States. Prioritize accurate US catalogs, then prepare market-specific files for future expansion.

</details>

<details>

<summary>When should I upload sale prices?</summary>

Upload changes at least 72 hours before launch. Upload major event changes at least four days ahead. Verify results before peak traffic.

</details>

<details>

<summary>How often should I update catalogs?</summary>

Send a full catalog at least once a month. Upload price, availability, and removal changes as soon as they occur. ESW uses these files to update Microsoft Merchant Center.

</details>

### Errors and corrections

<details>

<summary>Why was my entire file rejected?</summary>

A structural error prevented parsing. Export a fresh UTF-8 CSV. Confirm equal column counts, escaped commas and quotes, then re-upload.

</details>

<details>

<summary>Can some products succeed while others fail?</summary>

Yes, if the file structure is valid. ESW uploads valid products and logs failed products. Correct failed SKUs and re-upload them.

</details>

<details>

<summary>How do I update or remove products?</summary>

Use the same SKU or product ID and upload the latest values. To remove a product, set `availability` to `out_of_stock`. Omitting a SKU does not remove it.

</details>

<details>

<summary>Why are IDs displayed as scientific notation?</summary>

Excel converted long IDs and corrupted them. Regenerate the CSV from the source system. Import with **Data → From Text/CSV** and set ID columns to **Text**.

</details>

<details>

<summary>How do I verify data before uploading?</summary>

Open the CSV in Notepad. Confirm long IDs appear in full, such as `5063589815347`, not `1.23E+13`. Regenerate the file if values are converted.

</details>

<details>

<summary>What does an empty catalog file error mean?</summary>

The CSV has no product rows. Re-run the export. Confirm it has headers and product data, then upload it again.

</details>

<details>

<summary>Why are products missing mandatory fields?</summary>

Each category requires specific fields. Use the catalog specification, populate required fields, and re-upload corrected products.

</details>


---

# 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 dynamically by asking a question.

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

```
GET https://developer.esw.com/agentic-commerce/esw-agentic-discovery/faqs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.