All of EMS logistics. One system from the ambulance to HQ.
Warehouse, consumption cards, orders, KSeF invoices, PZP settlements, equipment, expiry dates, shifts and rosters — in one database instead of spreadsheets and paper. A report from the smartphone in the ambulance flows without retyping all the way to a settled invoice.
- Built on the processes of a working station.
- Every operation leaves a trail: who, what, when, why.
- Works in the ambulance without signal too.
One database, three places of work
AMBULANCE
Smartphone · PIN · offline
Consumption, checklist, failures, announcements — four big actions.
STATION
Warehouse · cards · roster
The manager fulfils cards, watches stock and expiry, plans crews.
HQ
Orders · KSeF · PZP
Approvals, split by supplier, settlements, statistics.
Data is everywhere. The ambulance can't wait.
Scattered spreadsheets, separate tools and paper — and every retyped number is an error that surfaces only at the tender or the audit.
Today
- Five workbooks — each in a different version with a different person.
- Paper consumption cards retyped after the shift.
- Invoice, order and delivery never meet.
- Expiry dates tracked from memory.
- Rosters in Excel, with no control of rest time or licences.
With Paralog
- One database — stock, shortages and expiry visible at once.
- Consumption and failures from the smartphone in the ambulance, PIN-confirmed.
- Order ↔ invoice ↔ delivery protocol — three-way control.
- The system watches expiry in the warehouse and in every ambulance.
- Roster with a crew generator and norm control.
Paralog in two minutes
From paper and spreadsheets to one system — ambulance, station, HQ.
Polish narration with Polish and English captions. Turn the sound on or select captions.
Ambulance. Station. HQ.
One database, three places of work. Data entered once in the ambulance flows without retyping all the way to invoice settlement.
01 · AMBULANCE
Four buttons. PIN instead of password. Works without signal.
The smartphone assigned to the vehicle is the ambulance account. The paramedic clocks in, runs the checklist, reports consumption (also by voice) and failures with photos. Every action is confirmed with a PIN. Without network, reports are stored locally and sync on their own.
02 · STATION
Warehouse, team cards, shifts and roster in one place.
Consumption cards arrive from ambulances on their own; issuing takes a few clicks, shortages carry over to the next card. Minimum levels suggest requisitions, and the Teams hub joins shifts, work cards and a roster with a crew generator.
03 · HQ
Approvals, suppliers, invoices and PZP — without retyping.
An approved requisition splits itself into orders per supplier. An invoice from KSeF or a scan (OCR) is matched to the order line by line, and HQ settles it against PZP contracts and allocates costs to teams. XLSX/PDF exports ready for tenders and audits.
Twelve modules. One start screen.
Every tile replaces a specific spreadsheet, tool or paper flow. You only see what you have permission for.
Warehouse
Stock, movements with history, corrections with justification, transfers between stations.
Orders
Wizard with shortage hints, approval, auto-split by supplier, deliveries.
Replenishment
Team consumption cards, warehouse issue, carry-over of shortages.
PZP settlements
Contracts, time-bound prices, CPV codes, invoice validation, costs to teams.
Expiry dates
Registry in the warehouse and ambulances, periodic checks, disposal protocol.
Reports
Failures with photos, receipt discrepancies, transfer requests.
Announcements
To everyone, a station or people. Evidential announcements PIN-acknowledged.
Teams
Shifts with checklists, work cards, roster with a crew generator.
Equipment and ambulances
Serial numbers, inspections and service, history, costs, documents.
Product catalogue
One base with categories, units and quantity guards.
Documents
Protocols, orders, invoices, PDFs and exports in one registry.
Statistics
Consumption per team and product, stock valuation, SIWZ calculator, XLSX/PDF.
Plus activity history, settings with search, help and bug reporting from every screen.
Paralog from the inside
The key views of a station manager and HQ. Click a screenshot to enlarge.
01 / 12
Everything that matters, one click away
- Tiles with counters: what awaits a decision, what is overdue, how many cards to fulfil
- The station picked here carries over to every other screen
- Only modules with permission are shown
02 / 12
Stock without spreadsheets
- Current stock of every product in the warehouse and ambulances
- Receipts, issues, corrections, transfers — with full history
- Stock always results from a movement: who, when, why
03 / 12
From the ambulance report to the warehouse issue
- Consumption cards reach the manager on their own
- Issue in a few clicks, shortages carry over
- The team confirms receipt with a PIN
04 / 12
Requisition in minutes, order by itself
- The wizard suggests shortages against minimum levels
- After approval the system splits the requisition per supplier
- An invoice from KSeF or a scan matches the order
05 / 12
Invoices against contracts, costs to teams
- PZP contracts and tasks with time-bound prices and CPV codes
- Every invoice line validated against the price on the invoice date
- Allocation to teams, exports for accounting
06 / 12
No more expired drugs
- Every expiry date in the warehouse and in every ambulance
- What expires today, this week, this month
- Periodic checks with a PDF disposal protocol
07 / 12
Crew rosters without Excel
- Availability → plan → confirmations → execution
- The generator respects rest time, norms and driving licences
- The plan warns, never blocks — the manager decides
08 / 12
The manager sees every shift
- Checklist status of all ambulances in one view
- Crew on shift with clock-in and clock-out
- A checklist problem becomes a report by itself
09 / 12
The station's entire assets under control
- Equipment and vehicles with serial numbers and documents
- Inspection and service schedule
- History of every device — from purchase to repairs
10 / 12
Messages that arrive
- To everyone, to a station or to selected people
- Evidential announcement PIN-acknowledged in the ambulance
- Recipients recorded at send time
11 / 12
Data you can see
- Consumption per team, product and period — on charts
- Item rankings, stock valuation as of a date
- XLSX and PDF exports for accounting and tenders
12 / 12
Who, what, when — in plain language
- Every operation in the registry, names instead of identifiers
- History is immutable — a correction is a new entry
- Filter by person, module and station
From the ampoule at the patient to a settled invoice.
Today this path is travelled by paper, three spreadsheets and two people retyping numbers. In Paralog data is entered once.
- 01
Consumption at the patient
The paramedic adds an item from the smartphone — by hand or voice — and confirms with a PIN.
- 02
Card at the manager
The manager issues from the warehouse, the team confirms receipt, shortages carry over.
- 03
Requisition
The wizard shows what is missing against norms. One click and it goes to HQ.
- 04
Approval and split
The system splits the requisition into orders per supplier. PDF and e-mail from the system.
- 05
Invoice and delivery
KSeF or a scan matched to the order. Receipt protocol, expiry dates in the registry.
- 06
PZP settlement
Invoice validated against the contract, costs to teams. Ready for the tender and the audit.
A smartphone in the ambulance. Works without signal.
Four big actions on the home screen, a PIN instead of a password, offline-first architecture.
Four actions from the home screen
Report consumption
By hand or voice, straight onto the card.
Equipment failure
With photos, straight to the manager.
Ambulance failure
Vehicle swap from the terminal.
Shift checklist
Medical and driver. Problem = report.
Clock-in and crew on shift
Paramedics join the crew with a PIN at the start of the shift. It is always known who used, reported and checked what.
Offline-first
No app store
A PWA installed from the browser. An update is one "Refresh" toast.
Cache for the whole shift
Catalogue, cards and checklists stored locally for 36 hours.
Work without network
Reports are saved locally and sync on their own, keeping the event time.
PIN instead of password
A short PIN and a one-time token — the system knows who reported, no login.
One system, four account types
Access comes from a permission profile and station scope. Everyone sees what they need — nothing more.
HQ / management
Every station: approvals, PZP contracts, invoices, statistics, permissions.
Station manager
Warehouse, cards, requisitions, reports, shifts and roster of their station.
Medical staff
Availability, my roster, my hours, leave, announcements.
Ambulance account
The shared smartphone in the vehicle. Every action PIN-confirmed.
From analysis to pilot — without stopping the station
The system grew out of months of conversations with paramedics and managers of a working station. The rollout runs alongside daily work.
- 1
Stage 1
Process analysis
Stations, teams, document flow, spreadsheets and PZP contracts.
- 2
Stage 2
Data migration
Catalogue, stock, equipment, contracts, price lists and expiry — from your spreadsheets.
- 3
Stage 3
Configuration and training
Stations, permissions, checklist templates. Separate training for managers and teams.
- 4
Stage 4
Pilot
Go-live at a chosen station with ongoing support. Changes in days, not quarters.
- 5
Beyond
Development and support
New features from real needs, every change with automated tests.
A quote tailored to your organisation
Each quote is prepared individually — for one station, a network with an HQ, or a whole organisation.
One station
An ambulance station or a medical transport base.
Warehouse, consumption cards, orders, expiry, equipment, teams and ambulance accounts with the offline app.
Custom quote
Ask for a quoteStation network
Several stations and an HQ.
Everything for one station, plus transfers, PZP settlements, invoices at HQ and network statistics.
Custom quote
Ask for a quoteWhole organisation
A large entity with non-standard needs.
Dedicated features and integrations, SLA, test environment, development around your processes.
Custom quote
Ask for a quoteStandards for management — and for IT
Permissions and station scope
Permission matrix per module and action, "view only" accounts. Enforced in the API.
Immutable log
Who, what, when, why. A correction is a new entry, never an overwrite.
Secure cloud
Encrypted connections, login limits, backups with point-in-time recovery.
Exports and documents
PDF protocols, XLSX exports, invoices — generated from data.
AI-ready
The assistant, invoice OCR and voice entry already work today.
Questions about ambulance station software
How does Paralog support ambulance station logistics?
Paralog connects inventory, consumption cards, orders, equipment, shifts and rosters in one database. HQ can access procurement settlements, invoices and network statistics. During a demo, we discuss these processes in the context of your organization.
Does the ambulance app work without internet?
Yes. The mobile app supports offline work. Consumption, checklists and equipment issues can be recorded without a signal; data synchronizes when the connection returns.
Can existing Excel data be migrated?
Rollout includes process analysis, migration of catalogs, stock, equipment, contracts, price lists and expiry dates from spreadsheets, configuration and training. A pilot starts at a selected station.
How much does Paralog cost?
Pricing is tailored to a single station, a station network with HQ or the whole organization. A free demo lets us discuss scope, integrations and rollout needs.
Our Vision
We want emergency medical stations to operate in one integrated environment — connecting staff, ambulances, equipment and administration, with the information they need always at hand.
Our vision is a station that anticipates needs, prepares teams for work more efficiently and reduces repetitive tasks. A station where it is easier to plan staffing, replenish supplies and keep ambulances ready.
That is why we want to develop Paralog into an ecosystem combining software, smart devices and artificial intelligence — so that data from daily operations helps anticipate problems, automate processes and make informed decisions.
See Paralog in action
A free demo on real scenarios — from consumption in the ambulance to a settled invoice.
- Wojtek Soczyńskiwojtek.soczynski@reago.pl
- Daniel Celińskidaniel.celinski@reago.pl