Frequently asked questions

We design, build, integrate and support business software, including airport billing, flight permit management, pharmaceutical systems (PMS and BSMS) and courier management, as well as custom web, mobile and desktop applications.

Yes. We build applications around your process, from requirements and design to development, testing, release and support. If a module you need is missing from our solutions, we build it.

Airports, aviation authorities, pharmaceutical and life sciences, courier and logistics, education and government, IT and telecom, HRMS and payroll, finance, real estate and construction, and data analytics.

Web applications, mobile apps (iOS and Android), enterprise and desktop software, e-commerce, API and systems integration, client-server and cloud applications, database and data systems, legacy modernization, QA and test automation, IT consultancy, resource augmentation, and maintenance and support.

Our office is at Plot 8, Ashoka Marg, Moti Vihar, South City I, Sector 30, Gurugram, Haryana 122003. We deliver systems that run in live operations in India and abroad.

Yes. Our systems run in live operations in India and abroad.

Yes. We connect to operational databases, ERP and accounting systems, meter systems, payment gateways and SMS, using JSON/XML APIs and third-party integrations.

Yes. We re-engineer older applications onto maintainable stacks, so the business keeps what works and gains a platform that can grow.

Yes. All our applications record automatically who did what, and when, for every action.

Use the contact page, email info@catabatic.co.in, or call or WhatsApp +91 9560044150. Tell us about your workflow and we will show how the closest module fits.

Custom software is an application built specifically for one organisation, around its own processes, rules and users, instead of a generic product bought off the shelf.

Off-the-shelf software is built for many customers and you adapt your process to it. Custom software is built to fit your process. A ready solution that is configured to your rules, such as our airport billing or courier systems, sits in between: it starts from proven modules and is extended to your requirements.

When your rules, tariffs, approvals or reports are specific to you, when off-the-shelf tools force costly workarounds, or when you need the software to connect with your own systems.

A description of the process you want to automate, who uses it, the rules and tariffs involved, and samples of your forms, reports or data. We document the requirements and agree the scope with you before development begins.

A minimum viable product is a first version with only the essential features, released early so it can be used and improved. It is a good way to start a larger system.

It depends on scope: the number of modules, users, integrations and reports. We can give a reliable estimate only after understanding your requirements, so please contact us with your process and we will respond with a proposal.

It depends on scope and complexity. A focused module takes less time than a full system. After the requirements are documented we can plan the stages and agree a timeline with you.

It is the sequence of stages a software project passes through: requirements, design, development, testing, and release and support.

Five stages: requirements, design, development, testing, and release and support.

Requirements are documented, the scope is agreed and signed off before work starts, so everyone knows what will be built.

Architecture, database and screen design are reviewed before build starts, so problems are found while they are still cheap to fix.

The system is built with version-controlled code and peer review.

Unit testing, integration testing and user acceptance testing against your data.

Deployment, user training and ongoing maintenance.

Version control, such as Git, records every change to the code, who made it and why, so the team can work together safely and go back to an earlier version if needed.

A code review is when another developer checks a change before it is accepted. It catches errors early and keeps the code consistent.

UAT is the final check where the people who will use the system confirm that it does what the business needs, using realistic data, before it goes live.

A written description of what the software must do, who uses it, its rules and its reports. It is the agreed reference for design, development and testing.

Changes are common. A change is reviewed for its effect on scope, effort and timeline, and agreed before it is built.

Send us your requirements through the contact page, or call or WhatsApp +91 9560044150. Describe your process and we will reply with how we would build it, and a demo of the closest module we already have.

Yes. Resource augmentation adds vetted developers to your team without the hiring cycle, and QA and test automation can be built into delivery.

Yes. We study your process, build and test against your data, train your team, and support you after go-live. Ongoing maintenance and support is available for software already in production.

A web application runs in a browser, so users need no installation and can reach it from any device. Examples are billing portals, permit systems and customer tracking pages.

Yes. We build iOS and Android apps alongside the backend they depend on.

A native app is written separately for each platform, iOS or Android. A cross-platform app shares most of its code across both. The right choice depends on features, performance needs and budget.

Yes. We build Windows and .NET desktop applications as well as cross-platform desktop software.

Yes. We build storefronts, catalogues and checkout wired into inventory and payments.

An application where users work on client programs or browsers while the data and business logic run on a central server, so many users share the same up-to-date records.

A website whose layout adjusts to the screen, so it works on phones, tablets and computers with a single set of pages.

Software for employee records, attendance, leave and payroll processing. We build it as part of our work for HRMS and payroll businesses.

An application programming interface lets one system request data or actions from another in a defined way, so systems can work together without manual re-entry.

Connecting separate systems, such as billing, ERP, meter readings or payment gateways, so data flows between them automatically.

We build JSON and XML APIs and integrate with third-party systems.

Yes. We build client-server and cloud applications with a secure, available architecture, deployed on-premise or in the cloud.

Cloud software runs on servers hosted by a provider and reached over the internet. On-premise software runs on servers you own or control. Some organisations choose on-premise for policy reasons, others choose cloud for easier scaling.

We design schemas, build data pipelines and create reporting layers, so the data your systems collect can be queried and reported reliably.

Moving data from an old system to a new one, with checks that records are complete and correct. It is a key step when replacing legacy software.

Yes. We build reporting, dashboards and statistical models on your operational data.

Re-engineering an older application onto a maintainable, supported technology stack, while keeping the business rules that still matter.

QA is the work of checking that software meets its requirements and is free of defects before and after release. It includes planning tests, running them and tracking issues.

Using scripts to run tests automatically, so the same checks can be repeated quickly after every change. We offer QA and test automation built into delivery.

Unit tests check small pieces of code. Integration tests check that parts work together. Acceptance tests check that the finished system meets the business need.

A record of who did what, and when, for every action in the system. All our applications record it automatically.

A way of limiting what each user can see and do according to their role, so people can perform only the steps they are meant to.

A digital way to sign off an action, linked to the responsible user and recorded with the action. In regulated settings it replaces paper signatures.

Ongoing upkeep for software already in production, including fixes and improvements.

An accountable technology partner for the whole stack, helping you decide what to build, how, and with what technology.

A bug is the software not doing what it was specified to do. An enhancement is a new or changed capability that was not part of the original specification.

It is software that calculates and invoices every charge an airport raises: aeronautical charges such as landing, parking and passenger fees, and non-aeronautical charges such as tenant contracts, utilities, royalty and airport passes.

Twenty billing types: 14 aeronautical and 6 non-aeronautical. They include landing, parking, housing and hangar, passenger service fee, user development fee, security, overflight, contract, electricity, water, royalty, miscellaneous and airport pass billing.

Yes. Rates, rules and taxes are configurable to your approved tariff, and we build new billing modules to your requirements.

Yes. Invoices are generated for every billing type, and corrections are handled through credit and debit notes. Every action is recorded in an automatic audit trail.

From on-block and off-block time, with the night parking rate included in the same bill.

UDF is calculated from passenger numbers and reconciled against the figures reported by airlines.

Through cash and carry billing, where charges are paid before departure.

Electricity bills use sub-meter readings and configurable tariffs. Water bills use metered consumption.

Yes. It covers new, renewal, duplicate and lost-pass fees, deposits and penalties, collected at the counter or billed to the sponsoring organisation.

Through credit and debit notes covering corrections, disputes, refunds and added charges, all recorded in the audit trail.

It is a platform where airlines or their agents apply online for flight permits and each department reviews and approves in a defined order, ending in an issued permit with a unique number and QR code.

Landing and take-off permits, overflight permits, non-scheduled and charter flight permits, technical landing permits and special flight clearances.

Yes. An approved overflight permit can trigger the overflight invoice, charter flights can be required to pay before release, and amended or cancelled permits adjust fees through credit and debit notes.

Amendments, extensions and cancellations are recorded against the original permit, so the full history stays in one place.

Required fields and documents are checked when the application is submitted, and anything missing is flagged.

Each department records its decision and remarks, in a defined order, so every step is visible and traceable.

Each issued permit carries a unique number and a QR code, and the applicant is notified when it is issued.

PMS is the Pharmacy Management System for store inventories such as IPs, materials, equipment, columns, impurities and working standards. BSMS is the Bio Sample Management System for bio-samples in development, validation and bio-study work.

PMS and BSMS are built for GxP and designed to meet the requirements of 21 CFR Part 11, with electronic signatures, an automatic audit trail and role-based access on every step.

Receipt with batch, quantity and expiry, requisition and approval before issue, issuance, transfer between stores and laboratories, expiry extension, discard with a recorded reason, and accountability reports for every movement.

Receipt and dispatch with temperature logs, courier slips and gate passes, chain of custody through storage and transfer, barcode scanning at collection and separation, retention alerts and electronic signatures.

An expiry extension is recorded with a reason and goes through approval, so it is always traceable.

No. Issuance is made against approved requisitions only.

It tracks bio-samples with accountability at every site, activity, project and study, with chain of custody through storage and transfer.

Yes. Actions are signed electronically by the responsible user, in place of paper forms.

Role-based access limits each user to the steps their role allows.

It is a platform that runs the consignment journey: booking, pickup, hub scanning, routing, delivery with proof, exception handling, billing and customer tracking.

Booking, pickup and tracking; hub, routing and delivery; billing and accounts; and reports with a customer portal.

Yes. Rate cards can be set by service, zone and weight, and cash on delivery is tracked and reconciled, with invoicing for customers and agents.

Yes. The customer portal offers online tracking, and status notifications can be sent to senders and receivers.

Consignments are scanned in and out of every hub, with manifests and bagging, routing and dispatch, and run sheets for riders and drivers.

Undelivered and returned parcels are recorded with reasons, so exceptions are visible and can be acted on.

Yes. Delivery is confirmed with proof of delivery for each consignment.