Skip to main content

Stock management

TicTAP's Stock Management module now works with a product catalogue and store-based inventory. Products are defined once in the catalogue, then each store, warehouse, van, or other stock location keeps its own quantities, minimum and maximum levels, and stock value.

This page gives a high-level overview. For the full workflow, see Stock management.

Current Stock Workflow​

Stock is managed through two connected areas:

  • Backend management: administrators maintain the product catalogue, review inventory by store, configure stock thresholds, check replenishment needs, subscribe users to stock events, and audit stock transactions.
  • Stock application: store users scan the store QR code, choose an operation, add products to a basket, confirm quantities, and create a stock transaction.

The catalogue is the source for product data such as name, part number, description, image, category, manufacturer, and unit cost.

Product Catalogue​

The catalogue centralizes the products that can be stocked. From the backend you can:

  • Create and edit products.
  • Organize products by category.
  • Assign a manufacturer when applicable.
  • Import products in bulk from a CSV file.
  • Export the catalogue for review or external processing.

The catalogue area includes dedicated views for products, categories, and manufacturers. Categories define the tree used later to group products below each store, while manufacturers keep supplier or brand data consistent across all stores.

Store Inventory​

Each store has its own inventory based on the shared catalogue. To add catalogue products to a store, open the store in the Workspace and create a new product holding for that store. A product holding links one catalogue product to one store and defines the store-specific quantity, minimum stock, and maximum stock.

You can create product holdings one by one by selecting an existing catalogue product, or import them in bulk when preparing a store inventory. Once created, they appear under the store and inherit catalogue data such as name, part number, image, manufacturer, and category.

In the Inventory Summary you can select a store and see:

  • The number of stocked products.
  • Product categories present in that store.
  • Total units available.
  • Total stock value in the configured currency.

The store view is organized by the product categories defined in the catalogue, so products appear grouped under their catalogue category instead of as a flat list. For each product holding you can review current quantity, minimum and maximum levels, unit cost, and product details.

Stock Operations​

Users operate stock from the Stock Application. After accessing a store, they choose the operation type:

  • Stock out: remove units from stock.
  • Stock replenish: add units to stock.
  • Stock adjust: set the recorded quantity to match the real count.
  • Stock transfer: move units from one store to another.

Products can be selected by searching, browsing categories, or scanning a product QR code. Selected products go into a basket where quantities can be reviewed and edited before confirmation.

Replenishment and Notifications​

When a product quantity in a store falls below its configured minimum, it appears in the Stock Replenishment view and TicTAP automatically creates a replenishment reminder for that product in that store. The suggested replenishment quantity is calculated from the current quantity and the configured maximum when one exists.

When the product is replenished back to the expected level, the reminder is resolved automatically.

Users can subscribe to stock events such as depleted stock, replenished stock, and outgoing stock transactions.

Transactions and Audit Trail​

Every confirmed stock operation creates a transaction. Transactions record the operation type, affected products, quantities, user, date, reason, notes, and order number when provided.

Transfer transactions also record the source store and destination store, so administrators can audit stock movements between locations.

The backend transaction list allows administrators to filter movements by date, transaction type, user, and product, making it possible to audit how inventory changed over time.