Services
E-commerce & Online Sales
Custom Software & Apps
Company
Our company
What is business process automation?
Business process automation means software takes over the repetitive steps in a workflow instead of people doing them. In most cases it is about data that currently moves by hand from one system to another: from the inbox into the ERP, from the shop into accounting, from a spreadsheet into a quote. Automation works on those handovers, not on any single program.
This means commercial and administrative workflows, not production plants — for machine data and equipment monitoring, see our Industrial IoT service. RPA is one technique among several, and it pays off mainly where a system offers no API.
How to tell a process is worth automating
Not every workflow is worth automating. These five patterns show up in almost every project.
The same data is entered twice. An order arrives in the shop and is retyped into the ERP. Every change has to be made in two places.
Month-end close always slips. Documents are missing, allocations are unclear, someone has to chase. The same effort every month.
A case waits on one person. An approval, a price check, a reply — if they are away, the process stops.
Deadlines slip because nobody is watching them. Early-payment discount terms and delivery dates sit in a system, but nothing reminds anyone.
There is a spreadsheet nobody can replace. It sits between two systems and holds logic that is documented nowhere.
Which processes we automate
We never start from a platform. We start from a process. These three areas cover most of our automation projects.
Quote-to-order and sales processes
From quote to order confirmation without retyping. Configuration, pricing and order entry run as one chain instead of across four systems.
Customer communication and service processes
Answer recurring enquiries without reading every message. Enquiries are classified, routed and given a draft reply. Approval stays with your team.
Document and data processes
Capture, check, file and post documents into the ERP. Including multi-entity, cross-border and custom posting rules — the cases standard products do not cover.
Typical automation projects
- Order processing: automatic handover from webshop, EDI or email into the ERP
- Inventory synchronisation: real-time alignment across shop, marketplace and warehouse
- Document processing: classification, naming and filing of incoming documents
- Approval workflows: purchase approvals, project sign-off, internal requests
- Reporting: automated summaries that surface what needs attention
Automation approaches compared
There are five common routes to automating a process. None is better in principle. The difference is how well the result still runs after two years, and who maintains it then.
| Approach | Fits when | Does not fit when | Maintainability |
| Custom development (weeks–months) | The process logic is your competitive advantage | The process is standard and available off the shelf | High, if documented. You control the lifecycle |
| Integrations & APIs (days–weeks) | The systems are fine, they just don't talk to each other | A system has no API and cannot be extended | High. Needs updating at version changes |
| Low-code & workflow tools (hours–days) | The workflow is simple and should be editable in-house | Branching and exceptions dominate | Medium. Fast to build, often hard to hand over. Licence costs scale with use |
| RPA (days–weeks) | A system offers no interface and has to stay | An API exists — then RPA is more expensive and more fragile | Low. Any interface change can stop the bot |
| Standard product (hours–days) | The process is common and requirements fit the standard | You need special logic the product does not know | High while you stay in the standard. The vendor controls the lifecycle |
In most projects the answer is a combination: a standard product for the common part, a custom integration for the part that works differently at your company. If a vendor tells you which route is right before analysing the process, they don't know the process.
Automate business processes: let's talk about your workflow
We work with companies across Italy, Germany, Austria and Switzerland from our base in South Tyrol. The starting point is usually the same: one workflow that takes too long.
Smart Dato Cockpit: our own product for automated processes
We built Cockpit because we kept solving the same problems for clients: recognising and filing incoming invoices, reconciling payments, answering recurring enquiries, sorting the inbox. Cockpit runs inside Microsoft 365 or Google Workspace, and approval stays with your team. Available EU-hosted or on-premise.
If your process fits the standard, Cockpit is the faster and cheaper route. If it doesn't, we build it.
Case studies: process automation in Italy and the DACH region
OMEST OLC: logistics across more than 50 carriers
- Situation: international transport, customs, warehousing, shipping and returns ran across separate systems and owners.
- Solution: a SaaS platform for planning, real-time tracking, billing, and automation, including a driver app.
- Integrations: more than 50 shipping carriers through dedicated connectors.
- Result: fewer manual steps at every handover, faster decisions, an architecture that extends.
Landwirtschaftliche Hauptgenossenschaft Südtirol: documents for 10,000+ members
- Situation: delivery notes, invoices and technical information had to reach over 10,000 members across more than 30 branches.
- Solution: an app with direct access to the cooperative's own ERP, plus rule-based notifications including regional weather data.
- Integrations: ERP integration services for documents and master data.
- Result: documents available without asking, fewer day-to-day enquiries.
Polyfaser: quoting with price and configuration logic
- Situation: pool configurations with many variants were checked and priced by hand, with the error rate that implies.
- Solution: a custom CRM with a central product database, price and configuration matrices, and automated notifications.
- Integrations: OMBIS ERP for consistent product and pricing data.
- Result: fewer configuration errors, shorter response times, faster sales onboarding.
How we work: business process automation consulting from analysis to operation
Automation does not start with software. We work in five steps, and after the second you know whether the project pays for itself.
1. Process analysis
We look at the workflow where it actually happens. What gets documented is how the process really runs, not how the manual describes it.
2. Prioritisation and business case
Every candidate is scored on effort, frequency and error rate. If a process does not pay for itself, we say so.
3. Pilot
We automate one process completely rather than five halfway. The pilot runs in production and produces the numbers for everything that follows.
4. Rollout
Further processes in the agreed order, each with handover to the department and documentation that reads without us.
5. Operation and further development
Monitoring, error handling and adjustment at system changes. An automated process is not a closed project, it is something you operate.
Related services
- Custom Software Development — When the process logic is the product itself.
- Smart Dato Hub — Interfaces between ERP, PIM, shop systems and carriers.
- Industrial IoT — Machine data rather than administrative workflows.
- Innovative Technologies — AI applications and computer vision.
Frequently Asked Questions
What is the difference between business process automation and RPA?
RPA is one of several techniques within business process automation. A bot drives existing interfaces the way a person would, and it is useful when a system offers no API. Business process automation also covers API integrations, workflow engines, custom development and standard products. In practice RPA is the emergency exit, not the default route.
Is process automation worth it for small and mid-sized companies?
Yes, and often more than for large organisations, because the workflows are easier to see and decisions are faster. The calculation is the same: frequency × handling time × staff cost, against build and running costs. From a few hours of manual work per week on the same workflow, a project usually pays back within a year.
Should we use no-code tools or an API-driven solution?
No-code holds up well as long as branching stays the exception. Once special cases become the rule, the model gets hard to follow and licence costs scale with usage. The usual path for companies starting with standard processes and later needing industry-specific workflows: no-code for the simple part, API integration for the core.
What is the ROI of business process automation?
Honestly, that can only be answered after process analysis. Four things are calculable: hours saved, error costs avoided, shorter lead times and removed waiting periods. In our projects the second is almost always larger than expected, because error costs are usually recorded nowhere.
Can you automate processes around an older ERP with no API?
Usually yes. We regularly work with systems that have grown over years, including OMBIS, TeamSystem and Zucchetti. Without an API, the options are database access, file exchange over established standards, or RPA as a last resort. Replacing the ERP is not a prerequisite.
Which processes should not be automated?
Workflows that happen rarely, where almost every case is different, or that need to be clarified first. An unclear process does not get better through automation — it just goes wrong faster. And if a process is about to be replaced, automating it is a wasted investment.