ASES develops APIs and integrations so that your programs work with the same data. We connect ERP, CRM, shop and accounting as well as payment services, shipping, marketplaces and your own software, such as SAP, DATEV, HubSpot, Shopify or Stripe. Your programs stay, and the data flows between them without anyone typing it in. If a suitable interface is missing, have us build it. On request, we also look after your interfaces during ongoing operation.
Choose where your systems stand today. The map shows your next step and what you get after each phase.
You are here
You are here
Initial consultation and assessment
We
We ask you to show us which programs you work with, which details travel between them and who transfers them today. We also ask how up to date the data needs to be in each case.
You
You name your systems and show us typical processes, such as an order or an invoice.
At the end
A clear picture of your systems and data flows.
You are here
Data flow and quote
We
We check which interfaces your systems offer and define the data flow with you. We describe every integration in the quote.
You
You set the priorities and review the quote.
At the end
A fixed-price quote with a precisely described scope.
You are here
Development and testing
We
We develop the interfaces and test them with examples from your daily work before real data flows.
You
You give feedback and decide with us how special cases are handled.
At the end
Tested interfaces, ready for launch.
You are here
Data migration and launch
We
If a new system replaces a previous one, we carry over your data. Then we take the interfaces live and train your team in the new processes.
You
You review the processes with us before the launch.
At the end
Systems that work with the same data.
You are here
Support and further development
We
On request, we adapt your interfaces when a vendor changes its API, and we connect further systems.
You
You tell us which integration comes next.
At the end
Interfaces that keep pace with your systems.
Your first step
We start with a process your team transfers by hand today, such as an order that someone enters into the ERP. Using it, we clarify with you which details should flow automatically in the future.
Enough to get started
The names of the programs you work with, and one process that runs by hand today.
Your first step
We read your partner's requirements, such as their EDI guide or the marketplace's API documentation, check them against your ERP and describe the integration in the quote. Then we build it, via EDI or as an API integration.
Enough to get started
Your partner's requirements or documentation and your contact person there.
Your first step
First we look at which data is in the previous system and which of it should move over. Then we plan the data migration and integrations for the new system.
Enough to get started
Name and version of both systems. A data sample from the previous system helps if you would like to share one.
Your first step
We look at your existing interfaces, even if another company built them, and take over their support and extension.
Enough to get started
Access to the code or configuration and a list of the connected systems.
The comparison further down shows which path suits your systems.Four paths compared
An interface defines how two programs exchange data. Usually this happens through an API: one program requests data or reports a change, and the other responds in an agreed format.
That way, in an integration, several systems work with the same data, whether shop and ERP, CRM and accounting, or your own app and a payment service. No one has to re-enter by hand what another program already knows.
Order
Sales order in the ERP
Invoice
Shipping
Interfaces and integrations we build
We build single API integrations as well as system integration across many programs. On request, we also open up your own systems to trading partners through an API.
ERP & CRM Integration
Shop, inventory management, accounting and CRM show the same customers, prices and orders everywhere.
Before we build an interface, we define with you, for every type of data, which system it is maintained in, which systems take it over and when it flows. That way, your programs do not overwrite each other. The example shows a typical distribution. We define yours in the data flow and quote phase.
Example: which system holds which data and which systems take it over
Custom interface, middleware or iPaaS: what suits you?
For every software integration, there are several paths, from a ready-made connector to a custom interface. Which one fits depends on how many systems are involved, how much data flows and how specific your processes are.
Little data, one processMany systems, large data volumes
Ready-made connector
A plugin or app from the vendor connects two widely used systems.
Fits if
both systems are widely used and your processes follow the standard.
Watch out for
updates on both sides and processes the plugin does not cover.
Automation tool
With n8n, Make or Zapier, a workflow starts by itself as soon as something happens and passes the data to the next program.
Fits if
individual workflows run by fixed rules, such as an inquiry from the website form that should land in the CRM.
Watch out for
costs that rise with the number of runs, depending on the plan, and the place where the tool processes your data.
An integration platform connects many systems through a central point. This can be custom software (middleware) or a rented service in the cloud (iPaaS).
Fits if
many systems are involved, such as shop, ERP, marketplaces and shipping at the same time.
Watch out for
another system to operate, license costs that rise with usage, and lock-in to the platform.
Custom interface
We develop the connection for your systems and your data rules.
Fits if
your processes are specific, large data volumes flow or a system offers no suitable interface.
Watch out for
the upkeep when connected systems change. It is part of the support.
We give the reasons for the path we propose in the quote.
How your interfaces work in operation
This is how we set up every interface before it goes live. During ongoing operation, we take over monitoring on request and let you know if an interface is not working as intended.
Every order is created in the ERP only once, even if it is transmitted again.
If a system is briefly unavailable, the interface sends the data again as soon as it is reachable again.
The interface holds back incomplete records and states the reason. After correction, they go out again.
A regular reconciliation shows whether all systems are in the same state.
We decide with you who on your side receives a message when a record is waiting for a correction.
What does an interface cost? What the price depends on
You know the price for your interfaces before development begins. The review of your systems before the quote is free. For development and launch, you pay a fixed price per project; for support, a flat monthly fee.
Quote
Development, one-off
Fixed-price project
Fixed price for the precisely described scope
If the scope changes, we adjust the quote first
No billing by the hour
Launch
After the launch, monthly
Support and further development
Flat monthly fee for maintenance and support
Phone support around the clock
New integrations per work package, each with its own quote
What the scope depends on
How many systems are connected and in which direction the data flows
Whether your systems offer a documented API or only export files
How many special cases the data rules have, such as variants or customer-specific prices
How much data flows and how up to date it needs to be
Whether data from a previous system is carried over and cleaned up
Whether trading partners are connected via EDI
If you have a budget range, mention it in the initial consultation. We align the scope at launch with it and plan further integrations for later steps.
Costs during operation
There are costs during ongoing operation as well: API fees from some providers, licenses for integration platforms or automation tools, hosting and maintenance. In the quote, we calculate these items over several years.
What you own at the end
After full payment, we hand over everything you need to run your interfaces yourself or have them developed further by another team.
Code
The source code of the interfaces developed for you
Git repository with the complete change history
Technical documentation
Data flows
Documentation of the data flows with field mapping
Interface description as an OpenAPI file
The workflows set up, for example in n8n or Make
Access
Servers and hosting
Accounts for all services
Credentials for all interfaces
Rights
Rights of use
Accounts with integration platforms, marketplaces and cloud services are in your name from the start, and so are the API keys.
We write code and documentation so that a new team can also find its way around. You decide who looks after your interfaces in the future.
Systems we connect
We connect the systems your team works with today and add what is missing.
ERP and inventory management
Items, prices, stock and orders.
Accounting
Invoices and records from the ERP.
CRM
Contacts, quotes and revenue.
Shop systems
Orders from the shop, items and stock from the ERP.
Marketplaces
Marketplace orders in the ERP, stock up to date on every marketplace.
Payment
Every payment, matched to its order, in accounting and the ERP.
Shipping
Orders to the shipping service, tracking numbers back to shop and ERP.
Automation
Individual workflows that an event in a program starts.
Frequently asked questions about system integration
Answers on costs, systems, data flows, operation and data protection for your interfaces.
That depends on the scope: how many systems we connect, whether they offer a documented API or only export files, how many special cases your data rules have and whether data is carried over from a previous system. As soon as the scope is set, you receive a fixed-price quote for the project. We bill maintenance and support as a flat monthly fee, and we offer new integrations per work package. Running costs such as API fees or a platform license are also stated in the quote.
The duration depends on how well your systems' interfaces are documented, when test access is available and how clear the data rules are. Our own team starts promptly. If you have a fixed date, such as the switch to a new ERP or a trading partner's go-live date, mention it in the initial consultation. We plan the scope at launch accordingly.
The widely used ERP, accounting, CRM and shop systems, such as SAP, Microsoft Dynamics 365, Odoo, DATEV, sevDesk, HubSpot, Salesforce, Shopware or Shopify. There are also marketplaces such as Amazon and Otto, payment services such as PayPal and shipping services such as DHL. For any other system, we first check which interfaces it offers.
Interface is the umbrella term for any point where two programs exchange data, for example through a file, a database or an API. An API is an interface with fixed requests and responses: your shop requests the stock of an item, and the ERP responds with the quantity. Most current systems offer an API, usually of the REST or GraphQL type. Many also report changes by themselves, via webhook.
When a trading partner requires it. EDI is the exchange of business documents such as orders, advance ship notices and invoices in a standard format, and large trading partners often expect it from their suppliers. An API connects systems directly and delivers data at the moment of the request. Many companies need both: EDI with their trading partners and APIs between shop, ERP and CRM. The formats your partner expects are usually described in their EDI guide.
Yes, for example through the database, through file exports as CSV or XML, or through existing web services. If the system offers none of these paths, we add an interface to the system itself if its code is accessible, or we replace the software step by step with a new one. We decide with you which path fits after we have looked at the system and the data.
That depends on the type of data. Stock and orders usually flow instantly: the system reports every change, for example via webhook, and the interface passes it on. Invoices and postings often go to accounting at fixed intervals, for example once a day. We define what flows when in your case in the data flow and quote phase.
For individual workflows by fixed rules, yes, for example when every new order should trigger a message to your warehouse. If large data volumes flow, many systems are involved or your processes have many special cases, an integration platform or a custom interface fits better. The two can be combined: a tool handles the simple workflows, a custom interface the large data stream. We clarify in the initial consultation which path suits you.
First we look at a data sample and record which data is where. Then we clean it up, map every field to its target in the new system and carry everything over in a trial run with real data. We check counts and spot samples against the previous system before we switch over. Until the switch is complete, you keep working with the previous system.
Interfaces and workflows we operate for you run on servers in the EU by default, preferably in Germany. If we process personal data on your behalf, we conclude a DPA under Art. 28 GDPR. A role and permission model defines who accesses which data; we encrypt data in transit and at rest and back it up regularly. Each interface transmits only the fields the workflow needs. For services from other providers such as HubSpot, Shopify or Zapier, we check before using them where they process your data and discuss this with you.
You do. After full payment, you receive the source code of the interfaces developed for you, with the Git repository and technical documentation, the documentation of the data flows and the OpenAPI file, the access credentials for servers and all services and the rights of use. With this, any development team can continue working on your interfaces.
An interface runs as long as the connected systems run. If a vendor releases an update or a new version of its API, the interface has to be adapted. On request, we handle this as part of the support, with the team that knows your interfaces. If your own IT should take over parts of it, we define the split together.
Tell us which programs your team uses and where data is transferred by hand today. We will get back to you as soon as possible and find a date for the initial consultation with you.