Define one row as one distinct stock item

A stock list needs a stable identifier. Use a unique SKU for each item or variant you need to distinguish, such as NOTE-A for one notebook type. Two products with different sizes or costs should not share a row merely because their names are similar.

Record a physical count in a consistent unit: pieces, boxes or another clearly understood stock unit. The quantity field uses whole numbers, so define the row’s unit before entering the amount. The tool is a manual browser list, not a shared warehouse database or a system that automatically updates after a sale.

Understand the value calculation

Recorded stock value is quantity multiplied by entered unit cost. If 12 notebooks cost NPR 80 each, the modeled value is 960. Four pens at 20 contribute 80, and three bags at 450 contribute 1350. The combined value is NPR 2390.

That value reflects your chosen cost basis. It is not automatically retail revenue, profit, tax valuation or a formal accounting inventory value. Use a consistent cost definition and one currency throughout. The tool rejects totals too large for its exact minor-unit arithmetic.

Treat a reorder flag as a prompt

An item is flagged when recorded quantity is at or below its entered reorder threshold. If the threshold is five and quantity is four, the row asks for review. A quantity of five also triggers the threshold. This is a simple comparison, not a demand forecast or an automatic purchase order.

Set thresholds using your actual needs, lead times and stock process. The tool cannot know supplier reliability, seasonal demand, reserved stock or incoming orders. Verify the shelf and outstanding orders before purchasing.

  1. Enter a unique SKU and descriptive item name.
  2. Record the current whole-unit count.
  3. Enter unit cost and a deliberate reorder threshold.
  4. Review value totals and low-stock flags.
  5. Export CSV and a JSON backup after a verified count.

Make updates traceable

A browser list becomes stale when sales, damage or deliveries are not recorded. Choose a routine for recounting and updating it. Keep source receipts or another appropriate business record outside the tool; a revised quantity does not preserve a complete transaction history.

Optional local storage belongs to one site origin and browser profile. It can disappear when site data is cleared and cannot resolve simultaneous edits from several employees. Export a backup if the list matters. If the business needs audit history, access controls, barcode workflows or multiuser synchronization, move to a system designed for those requirements instead of stretching a manual utility beyond its purpose.

References & method notes

The linked references explain the underlying formats, APIs or methods. Worked examples and instructions are original to this guide; a reference is not an endorsement of Nepocore.