# Preventing overselling of the last item across a custom website and Square POS

**URL:** <https://developer.squareup.com/forums/t/preventing-overselling-of-the-last-item-across-a-custom-website-and-square-pos/28021>\
**Category:** Questions\
**Created:** [September 28, 2026, 9:51pm UTC](https://developer.squareup.com/forums/t/preventing-overselling-of-the-last-item-across-a-custom-website-and-square-pos/28021 "2026-09-28T21:51:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![UiTgG658KBM7](https://avatars.discourse-cdn.com/v4/letter/u/8e8cbc/32.png) [@UiTgG658KBM7](https://developer.squareup.com/forums/u/UiTgG658KBM7)\
**Post date:** [September 28, 2026, 9:51pm UTC](https://developer.squareup.com/forums/t/preventing-overselling-of-the-last-item-across-a-custom-website-and-square-pos/28021/1 "2026-09-28T21:51:57Z")

</div>

I’m building a website that sends orders and payments to merchants’ Square accounts.

In a sandbox test, I started with one item in stock. Another Square API purchase bought it after our website’s stock check but before our website completed payment. Both payments succeeded, leaving inventory at −1.

Does Square offer an API-supported reservation or checkout mechanism that prevents this across a custom website and Square POS? I noticed `RESERVED_FOR_SALE` is read-only through the Inventory API.

If so, which endpoints and merchant settings should we use? If not, what approach does Square recommend for integrations?

---

<div class="post-metadata">

**Author:** ![jaeha](https://avatars.discourse-cdn.com/v4/letter/j/ebca7d/32.png) [@jaeha](https://developer.squareup.com/forums/u/jaeha)\
**Post date:** [September 29, 2026, 10:45pm UTC](https://developer.squareup.com/forums/t/preventing-overselling-of-the-last-item-across-a-custom-website-and-square-pos/28021/4 "2026-09-29T22:45:22Z")

</div>

Welcome to the Developer Forum!

Your test shows a check-then-pay race. Square does not document an API operation that reserves the last unit against both your website and Square POS; the Inventory API cannot move stock into `RESERVED_FOR_SALE`.

You can [enable inventory tracking and automatic sold-out status for the relevant variations and locations, check availability right before taking payments, and use inventory/catalog webhooks to update your site](https://developer.squareup.com/docs/inventory-api/monitor-sold-out-status-on-item-variation). However, these measures reduce stale availability but cannot really guarantee that another sale won’t complete first. I suggest you reconcile completed sales and have an out-of-stock/refund process.
