Regulation into workflow
Reporting duties, timing constraints, data fields, identity requirements, and exception paths were converted into explicit application behaviour and acceptance criteria.
Global Pharmaceutical Company
Delivering an end-to-end automated SaaS platform for daily medicine stock and commercial-operation reporting in Romania, built on AWS Amplify in less than two months.
Project context
Delivery window
Less than two months
Industry
Pharmaceuticals
Platforms
Responsive web application · Managed SaaS platform
The solution supports reporting workflows for medicine stocks and commercial operations submitted through Romania’s electronic reporting system, SER.
Its functional scope was designed around the reporting obligations described by Romanian Ministry of Health Order 1345/2016 for authorised medicine manufacturers, importers, wholesale distributors, and pharmacies.
The end client is one of the largest pharmaceutical companies operating in Romania and internationally. Its identity is withheld under client confidentiality.
The challenge
Daily regulated reporting involved strict data, identity, timing, and traceability requirements. The client needed a secure way to prepare and submit stock and invoice information, support both manual and automated reporting, track every attempt, adapt as requirements changed, and avoid taking ownership of complex infrastructure.
How we moved
Delivery methodology
Reporting duties, timing constraints, data fields, identity requirements, and exception paths were converted into explicit application behaviour and acceptance criteria.
AWS Amplify and managed AWS services provided a modular foundation that could scale with demand without transferring server administration to the client.
The reporting workflow, delivery pipeline, environment updates, monitoring, and operational alerts were designed to minimise repetitive manual intervention.
End-to-end tests exercised complete user and reporting journeys, while automated delivery made the same checks repeatable for every release.
The solution
PharmaTrack is a secure SaaS reporting platform that supports daily stock and invoice reporting to SER and the relevant Romanian health authorities. It combines MFA-protected access, user management, reporting dashboards, manual and automated submissions, per-user activity history, medicine-catalogue maintenance, encrypted reporting, qualified-certificate authentication, monitoring, and managed cloud operations in one service.
Business outcomes
Measured from implementation start through delivery of the production-ready scope described in this case study.
The product supports the daily stock and commercial-operation reporting workflow for which it was designed.
Build, deployment, and complete functional journeys were automated and exercised through end-to-end tests.
MTD provided the web application and its cloud infrastructure as a managed service rather than transferring server operations to the client.
From requirement to delivered state
Starting point
Daily submissions required a dependable process across stock, invoice, product, and reporting information.
Delivered state
One workflow for manual or automated submission, status visibility, and reporting history.
Starting point
Sensitive reporting actions required controlled user access and trusted interaction with SER.
Delivered state
MFA, role-aware user management, secure sessions, and qualified-certificate authentication for SER interaction.
Starting point
The client did not want to administer application servers and supporting infrastructure.
Delivered state
A managed, serverless AWS foundation with automated scaling, updates, monitoring, and alerting.
Starting point
Frequent regulatory or functional changes needed a repeatable path to production.
Delivered state
Automated delivery backed by end-to-end tests covering complete product journeys.
Capabilities
Technology
Evidence & disclosure
The pharmaceutical company’s identity is withheld under client confidentiality. The sector, reporting context, architecture, technology, delivery method, and product scope are published without identifying the organisation.
Published 24 August 2026