# Square Annoyingly Wipes Item Descriptions on New Batch Upsert's of Existing Products – Confirmed Bug + Workaround

**URL:** <https://developer.squareup.com/forums/t/square-annoyingly-wipes-item-descriptions-on-new-batch-upserts-of-existing-products-confirmed-bug-workaround/23538>\
**Category:** Questions\
**Created:** [August 6, 2025, 8:41pm UTC](https://developer.squareup.com/forums/t/square-annoyingly-wipes-item-descriptions-on-new-batch-upserts-of-existing-products-confirmed-bug-workaround/23538 "2025-08-06T20:41:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gsj123](https://avatars.discourse-cdn.com/v4/letter/g/839c29/32.png) [@gsj123](https://developer.squareup.com/forums/u/gsj123)\
**Post date:** [August 6, 2025, 8:41pm UTC](https://developer.squareup.com/forums/t/square-annoyingly-wipes-item-descriptions-on-new-batch-upserts-of-existing-products-confirmed-bug-workaround/23538/1 "2025-08-06T20:41:02Z")

</div>

I’ve spent hours trying to figure this out thinking it was my code and pulling my hair out. It wasn’t.

If you use `batch-upsert` with a catalog item that already exists and has a `description`, Square will **wipe the description** unless you send back a _new_ and different one.

Even if you send the exact same `description` value as before, Square still deletes it. With no response, or anything else.

This is silent, undocumented, and 100% reproducible.

**Tested Scenarios:**

- Existing item with description → send same description again → **wiped**

- Existing item with description → send no description → **wiped**

- Add new variation without updating description → **wiped**

- Send different description → **replaces it**

- Trick it with minor change (e.g. appending a dash) → **preserved**

**Workaround:**

1. Always send `item_data.description` with every upsert.

2. If the description hasn’t changed, append a character (I use a dash `-`) to bypass Square’s weird logic.

Posting this so the someone else doesn’t waste hours trying to figure this out.

---

<div class="post-metadata">

**Author:** ![Square-Dev-AI](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/square-dev-ai/32/2513_2.png) [@Square-Dev-AI](https://developer.squareup.com/forums/u/Square-Dev-AI)\
**Post date:** [August 6, 2025, 8:41pm UTC](https://developer.squareup.com/forums/t/square-annoyingly-wipes-item-descriptions-on-new-batch-upserts-of-existing-products-confirmed-bug-workaround/23538/2 "2025-08-06T20:41:14Z")

</div>

👋 I’m Square Dev AI, here to help answer your question!  
Based on the information you’ve provided, the following documentation will help answer your question:

> **[Monitor Sold-out Item Variations or Modifiers](https://developer.squareup.com/docs/inventory-api/monitor-sold-out-status-on-item-variation)**
>
> Learn how to use the Catalog API to set or inspect a sold-out item or to have it enabled to be set as sold out when its inventory count reaches zero.

> **[Inventory API Process Flow](https://developer.squareup.com/docs/inventory-api/how-it-works)**
>
> Learn about the inventory process flow and how the Inventory API works.

> **Additional Documentation**
>
> [Define Item Variations Using Options](https://developer.squareup.com/docs/catalog-api/item-options)  
> [Synchronize a Catalog with an External Platform](https://developer.squareup.com/docs/catalog-api/sync-with-external-system)  
> [Add a Catalog Item](https://developer.squareup.com/docs/catalog-api/build-with-catalog)

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.  
Otherwise one of our Developer Advocates will provide additional assistance shortly.
