> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/learn-netsuite/synchronization-flows/products-and-inventory/inventory-reset.md). # Inventory Reset Learn how to efficiently manage inventory resets between HotWax and NetSuite. NetSuite is often the system of record for inventory at all locations. The OMS usually syncs a full inventory reset from the OMS once a day. This requires a scheduled export from NetSuite and an import job into the OMS be scheduled. To learn more about the inventory sync integration with NetSuite read the full documentation **Generate inventory items from NetSuite** ``` HC_generateCSV_InventoryItems ``` **Place inventory items at SFTP** ``` HC_uploadCSV_InventoryItems ``` **Import inventory into HotWax** ``` Import inventory FTP Config: RESET_INVENTORY ``` ## Reset inventory by quantity on hand Use a quantity-on-hand (QOH) reset when NetSuite is the source of truth for a facility's physical inventory and the reset file contains the physical count. The OMS compares the QOH in the file with its current QOH, then applies the difference to both QOH and available to promise (ATP). This calculation does not preserve existing reservations. For example, if the OMS has QOH of 10 and ATP of 5, and NetSuite sends QOH of 4, the OMS applies a delta of -6. The resulting QOH is 4 and ATP is -1. Use this method only when the file represents a physical inventory count. For the field-level configuration and alternative reset methods, see [inventory reset configurations](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/data-manager/freq-used-configurations.md#reset-inventory-by-qoh). --- # 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://docs.hotwax.co/documents/learn-netsuite/synchronization-flows/products-and-inventory/inventory-reset.md?ask=&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.