CartronPOS medicine and stock management foundation

Pharmacy

Control medicine identity, prescriptions, batches, dispensing, expiry, recalls, and pharmacy stock.

Combine medicine-specific controls with the shared POS and inventory engine. Community and hospital pharmacies can receive batches, prioritize FEFO stock, dispense prescriptions, and preserve branch-level medicine history.

What the Pharmacy module covers

The workspace is organized around complete operational responsibilities, not a collection of disconnected menu labels.

01

Medicine catalog

Link sellable products to medicine profiles, dosage information, prescription requirements, and controlled identifiers.

02

Batch receiving and availability

Receive costed quantities with expiry dates and determine eligible stock by branch, batch, quarantine, recall, and FEFO order.

03

Prescription and dispensing

Review prescriptions, select eligible batches, record dispensing, and connect the outcome to billing and stock deduction.

04

Safety and traceability

Identify expiring, expired, quarantined, or recalled stock and preserve medicine movement and dispensing history.

Records kept by the workspace

These are the principal operational records staff create, update, review, or hand to another connected module.

  • Medicine profiles and linked products
  • Medicine batches, quantities, cost, and expiry
  • Prescriptions and prescribed items
  • Dispensing records and stock deductions
  • Quarantine, recall, and batch movement history

What the connected workflow is designed to improve

The module combines records, permissions, location scope, and shared services to support these practical operating results.

01

Safer stock selection

Branch, batch, expiry, quarantine, recall, and FEFO controls help staff select eligible medicine stock before recording a dispensing event.

02

Connected dispensing

Prescription review, chosen batches, quantities, stock deductions, billing, and medicine history remain part of one traceable operational flow.

03

Earlier expiry action

Pharmacy teams can identify expiring, expired, quarantined, or recalled batches and act before affected quantities are offered for normal dispensing.

Included functionality

The module connects the following working capabilities through one tenant and branch model.

  • Medicine profiles, dosage details, prescription requirements, and product linkage
  • Batch receiving with quantities, cost, expiry, and FEFO availability
  • Quarantine, recall, expired-stock, and dispensing controls
  • Prescription review, dispensing records, and terminal stock deduction
  • Hospital prescription and billing integration with pharmacy inventory

How work moves through the module

A typical operating sequence; permissions and branch configuration determine who performs each step.

  1. 1

    Link products to medicine profiles and receive traceable batches

  2. 2

    Review prescription requirements, available batches, expiry, quarantine, and recall state

  3. 3

    Select eligible stock using FEFO controls and record the dispensing event

  4. 4

    Post the charge, stock deduction, batch history, and prescription outcome together

Deployment, data ownership, and management oversight

The workspace is connected to the wider platform without removing tenant, location, department, or permission boundaries.

Deployment model

Community and hospital pharmacies use the hosted pharmacy workspace for profiles, prescriptions, and oversight while supported branch stock and terminal activity can continue locally and synchronize by branch.

Access and data scope

Medicine stock is store and batch scoped. Pharmacy permissions distinguish medicine setup, receiving, prescription review, dispensing, inventory control, and management reporting.

Management visibility

Review prescription status, dispensed quantities, batch availability, expiry exposure, quarantines, recalls, medicine stock value, and branch pharmacy performance.

Assign the workspace by responsibility

Module enablement makes the workspace available to the organization. User assignments and permissions still control its menus and actions.

PharmacistDispensing technicianPharmacy stock officerPharmacy manager

Administrators can combine module access with branch, store, campus, facility, department, menu, and action permissions. A shared user may work across approved workspaces without receiving access to unrelated records.

Start with Pharmacy, then assign the right locations and people.

Hosted onboarding records the organization, first branch, business type, module selection, and owner account. Additional branches, roles, and permissions can be configured from administration.