
Software · Integration · Digitalisation · Dornbirn
We build the software that is needed.
C.O.P.S develops custom software and interfaces and connects systems: ERP, accounting, vending machines, telephony. Sometimes that is an application, sometimes a small module. We do not build more software than necessary.
Software and digitalisation
What we build and connect
Six areas, one principle: understand first what is really needed.
Custom software
Applications with offline operation, roles and several languages, built for a specific business.
Learn moreInterfaces and system integration
Systems that do not talk to each other get a connection: interfaces, file formats, workflows.
Learn moreERP integration
Modules for what the ERP system lacks: accounting, contracts, point of sale, master data.
Learn moreProcess automation
Read invoices, match bank lines, re-invoice costs: without retyping and without flying blind.
Learn moreData and business intelligence
Reports from vending machines and accounting, with a single source for tax rules.
Learn moreTechnical consulting
Question requirements, analyse processes and consider the consequences for operations and maintenance.
Learn more
How we work
The 60/20/20 Philosophy
A mindset, not a split of working hours. It describes how we build: build fast, think critically, try to break our own solution.
BUILD60 %
Build what runs
We develop, integrate and deliver. A working prototype teaches us more than a long concept, and small steps beat the big bang.
THINK20 %
Question requirements
We ask what is really needed and what it means for operations, maintenance, security and extensibility. Sometimes the best solution is to build less.
- A simple list instead of batch tracking, as long as the simple solution is enough
- Protection inside our own module, because the external system only knows full access
BREAK20 %
Break our own solution
We look for failure cases, edge conditions, data deviations and security gaps before a customer does. Not every finished feature is automatically ready for operations.
- Export compared document by document with the source system before it went live
- Vending machine bookings compared with existing documents over 18 months
- Development and test environment as a neutralised clone of production
Code fast. Think critically. Hack mercilessly.Human-directed. AI-powered. Adversarially tested.
This describes our way of working, not a certification. The case studies show which checks we actually carry out.
From our own business
We run our own businesses to work out solutions ourselves.
Vending stores, a specialist shop, parcel shops and wholesale: we run our own businesses to work out solutions for customers ourselves and to work with them. As a licensed wholesaler within the tobacco monopoly, we supply tobacconists (Trafiken) and other shops with e-liquids, FMCG products and other trends. The problems there are real: stock, tax rounding, parcels nobody collects. What does not hold up there does not reach a customer.
- RELOAD: refilling, prices and checks in the vending store
- PORTER: parcel intake and parcel depot
- PRIME: product data for specialist shop and wholesale

Our own applications
What runs in operation
Three applications that we develop and use every day.
- In useDaily
RELOAD
Refill vending machines, change prices, run checks and shopping lists. With offline operation and rights per role.
See RELOAD - In useDaily
PORTER
Parcel intake and storage: scan, store, read the label and answer enquiries by phone.
See PORTER - In useDaily
PRIME
Product master data and media with approval before every change, on its way to a standalone solution for retail and wholesale.
See PRIME
Four habits
They run through everything we build.
Small where small is enough
A module just for splitting cash discount. One single rule for a wrongly reported tax type. We do not build more than necessary.
Connected instead of retyped
Invoices from the mailbox, bank lines from the statement, sales from the machine: data travels between systems, people check the result.
Check first, then switch
Comparison with the old records, a trial run with rollback, a draft instead of a booking. Nothing is booked automatically that we cannot explain.
Stay in operations
We run the businesses we build for. We are the first to notice what does not work.
What can be checked
Numbers we can count, not estimate.
- Founded
- 2020Entry in the company register
- Own applications
- 3RELOAD, PORTER, PRIME
- Modules for the ERP system
- 20+developed in-house, used in our own business
- Automated tests
- 600+in the ERP modules
A team, lots of experience
Together, as a team of clever minds, we look back on over 500 joint software projects. Anyone who has completed that many projects knows where things go wrong: master data, interfaces, tax, permissions.
- Team
- Clever mindswho develop, advise and operate together
- Software projects
- 500+shared experience of the team
- BI models
- Hundredsprepared and analysed
- Own businesses
- 3vending stores, specialist shop, parcel depot
Frequently asked questions
Answers that our work can back up.
What does C.O.P.S do?
C.O.P.S is a company from Dornbirn, Austria, that develops software and connects systems. We also run our own businesses: 24/7 vending concepts, an e-liquid specialist shop under the supervision of the Austrian tobacco monopoly administration (Monopolverwaltung), a multi-carrier parcel shop and a wholesale business. We are a licensed wholesaler within the tobacco monopoly and supply tobacconists (Trafiken) and other shops with e-liquids, FMCG products and other trends. That is how we work out solutions for customers ourselves and work with them every day. RELOAD, PORTER and PRIME are such examples.
Does C.O.P.S develop custom software?
Yes. Our own applications RELOAD, PORTER and PRIME are in operation, and we develop interfaces and modules for ERP systems. We first check whether a small module or an interface is enough before we build a whole application.
Which systems does C.O.P.S work with?
ERP systems, the accounting software of tax advisers, the telemetry system of vending machines, telephone systems and workflow tools. Our knowledge is not tied to a single ERP system. Today we work with one of them.
Does C.O.P.S work with external developers?
We have our own development team. Our partner network also includes InfraNext, a development company we work with closely.
What role does AI play in development?
AI-assisted tools speed up development, analysis and documentation. People are responsible for architecture, requirements and results.
How is the software checked?
Before every switch we check: comparison with the old records, trial runs with rollback and automated tests in the ERP modules. The case studies list the individual checks.
Do you have systems that do not talk to each other?
Tell us briefly what it is about. We will tell you honestly whether it needs an interface, a small module or an application. Or whether it needs nothing new at all.
Discuss a project