---
title: "Discussion on \"A 200 that wasn't a save: how fetch() redirects could delete queued POS sales\" | Hashnode"
description: "Discussion on \"A 200 that wasn't a save: how fetch() redirects could delete queued POS sales\". An offline POS queue could delete unsaved sales when fetch() followed a redirect to a 200. The bug, the receipt rule that fixed it, and the tests."
url: "https://hashnode.com/posts/a-200-that-wasn-t-a-save-how-fetch-redirects-could-delete-queued-pos-sales/6aea0e1c3e7249bb19d48172"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A 200 that wasn't a save: how fetch() redirects could delete queued POS sales](https://tukri.hashnode.dev/a-200-that-wasn-t-a-save-how-fetch-redirects-could-delete-queued-pos-sales?utm_source=hashnode&utm_medium=feed)

An offline POS queue could delete unsaved sales when fetch() followed a redirect to a 200. The bug, the receipt rule that fixed it, and the tests.

Nov 3 · 6 min read · tukri.hashnode.dev  
Read the article

-   [#javascript](https://hashnode.com/tag/javascript)
-   [#pwa](https://hashnode.com/tag/pwa)
-   [#service-workers](https://hashnode.com/tag/service-workers)
-   [#web-development](https://hashnode.com/tag/web-development)

## Written by

[Tukri](https://hashnode.com/@tukri)

@tukri · Dhaka, Bangladesh

  
[View profile](https://hashnode.com/@tukri)

Bangla POS, stock & dues book for small shops

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
