Features Inventory – Stock

Stock deducted per visit, flagged before it runs out

The shared warehouse and every branch on one table; receiving, usage, write-offs and transfers are all logged, with MISA integration.

Inventory in Qub-X CRM
  1. 01 / 03

    Stock per branch

  2. 02 / 03

    Deducted per visit

  3. 03 / 03

    Low-stock alerts

Features

Inside Qub-X Inventory

See what every branch has left on one table.

01 / 05

Stock per branch and shared warehouse

See what every branch has left on one table.

  • Each product page shows roughly how many days it will last
  • Cost updates with every receipt

Versus the old way

Moving 20 boxes from the warehouse to the Dallas branch: 3 spreadsheets → 1 transfer

Create the transfer, the receiving branch clicks Confirm receipt. Stock on both sides updates itself and history records who sent, who received and when.

  1. 01Fewer stepsOne slip covers sending and receiving; no two people editing two files.
  2. 02Stock that is rightAn unconfirmed transfer shows a warning at the top of the page until it is done.
  3. 03No manual usageSet material norms per service once; every finished visit deducts stock by itself.

The usual way · 5 steps

  1. Warehouse edits its Excel to subtract
  2. Message the branch on Zalo
  3. Branch edits its own file to add
  4. Month-end count shows a gap
  5. Go looking for who forgot

3 files, 2 people, a gap with no origin

With Qub-X · 2 steps

  1. 1Create the transfer, pick items and quantities
  2. 2Receiving branch clicks Confirm receipt

1 slip, both sides agree

The problem

Out of stock, and the customer is already on the bed

01/ 07

One spreadsheet per branch and nobody deducts what a visit uses, so the count comes up short with no explanation.

  • No view of what each branch still has
  • Materials used in visits never deducted
  • Batches sent that the other side never confirmed
The usual way: Warehouse edits its Excel to subtract, Message the branch on Zalo, Branch edits its own file to add, Month-end count shows a gap, Go looking for who forgot
The usual way
  • No view of what each branch still has
  • Materials used in visits never deducted
  • Batches sent that the other side never confirmed

What stands out

Open inventory, see which branch is running low

02/ 07

The stock table shows every branch against its alert threshold, and anything at the threshold is tagged LOW and counted in the Running low filter.

  • Stock per branch, warehouse kept separate
  • An alert threshold and nearest expiry on every row
  • Low-stock and unconfirmed-batch warnings at the top
Stock
  • Stock per branch, warehouse kept separate
  • An alert threshold and nearest expiry on every row
  • Low-stock and unconfirmed-batch warnings at the top

Saves logging usage

When a service is done, the branch's stock deducts itself

03/ 07

Set the materials for one session of each service once, and every service line marked done on an appointment deducts them from that branch's stock.

3 files, 2 people, a gap with no origin1 slip, both sides agree
  • Usage tied to appointments, traceable both ways
  • Packages can set their own norm
  • Analytics: net usage, shrinkage, days left
Usage analytics
  • Usage tied to appointments, traceable both ways
  • Packages can set their own norm
  • Analytics: net usage, shrinkage, days left

Products

Open a product, see roughly how many days it will last

04/ 07

The product page estimates how many days the stock will last from the last 30 days of use, next to stock per branch, cost and stock value.

  • Cost from the latest receipt
  • Received and used in the last 30 days
  • Receive, issue or transfer straight from the product
Product page
  • Cost from the latest receipt
  • Received and used in the last 30 days
  • Receive, issue or transfer straight from the product

Transfers

Move stock to another branch, both sides agree once it is received

05/ 07

One transfer slip records the sending branch, the receiving branch and the quantities, and stock on both sides updates when the receiver clicks Confirm receipt.

  • Draft → In transit → Done
  • Alerts for batches nobody has confirmed
  • Filter slips by from and to branch
Transfer slip
  • Draft → In transit → Done
  • Alerts for batches nobody has confirmed
  • Filter slips by from and to branch

Receiving

Stock arrives from a supplier, the cost updates itself

06/ 07

A receipt records the supplier, quantities, unit cost and expiry per line, and completing it updates stock and cost.

  • Suppliers and receiving slips tied to each batch
  • Write off expired or damaged stock with a reason
  • Receiving slips synced to MISA
Receiving
  • Suppliers and receiving slips tied to each batch
  • Write off expired or damaged stock with a reason
  • Receiving slips synced to MISA

Easy to use

Wherever a box went, the ledger shows each step

07/ 07

Every receipt, issue, write-off, adjustment, transfer or sale is one line with the document, the change, stock after and who did it.

  • Filter by branch, product and movement type
  • Every slip shows who created and completed it
  • Excel export for reconciliation with accounting
Stock ledger
  • Filter by branch, product and movement type
  • Every slip shows who created and completed it
  • Excel export for reconciliation with accounting

Three questions stock managers ask

Can branches see each other's stock?
Depends on permissions. By default a branch sees its own stock and the warehouse; managers see everything.
What about services without a norm yet?
Stock is not deducted for them; the service page shows No materials yet, and Analytics shows how many services still need norms so you can add them over time.
Can stock be adjusted by hand?
Yes, but manual adjustments are flagged and excluded from net usage so they do not distort the analysis.

BOOK A DEMO

See how Qub-X fits the way your clinic works

Share how your clinic operates. The Qub-X team will prepare a demo focused on your workflow and needs.

City
Which areas do you want to review?

Qub-X will send a confirmation on Zalo and contact you to set a suitable time.

  • A 30-minute demo based on a real clinic scenario
  • Focus on the features you care about
  • No commitment required after the demo