Skip to content

System integration, from analysis to operation

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.

Getting interfaces built: how it works

Choose where your systems stand today. The map shows your next step and what you get after each phase.

Where do you stand?
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.

The comparison further down shows which path suits your systems.Four paths compared

What is an interface?

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.

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.

  • Shop and inventory management connected
  • CRM and ERP in sync
  • Integration with DATEV
  • SAP
  • Microsoft Dynamics 365
  • Odoo
  • HubSpot
  • DATEV
Request a quote

Data Integration & Migration

Your data arrives in the new system cleaned up and checked.

  • Data migration when changing systems
  • Duplicates cleaned up
  • Data combined for reporting
  • SAP
  • Shopware
  • HubSpot
  • PostgreSQL
  • MySQL
Request a quote

EDI & Marketplace Integration

Orders from trading partners and marketplaces land directly in your ERP.

  • EDI with trading partners
  • Amazon, Otto, eBay and Kaufland
  • Payment and shipping connected
  • Amazon
  • Otto
  • eBay
  • Kaufland
  • DHL
Request a quote

Which system holds which data?

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.

Choose system
Example: which system holds which data and which systems take it over
ShopMarketplaceERPCRMAccounting
Items and pricesinstantlytakes overSKUtakes overSKUholdsItem numberNot involvedNot involved
Stockinstantlytakes overavailabletakes overavailableholdsStock on handNot involvedNot involved
OrdersinstantlyholdsOrder date YYYY-MM-DDholdsOrder date YYYY-MM-DDtakes overMM/DD/YYYYNot involvedNot involved
Customer master datainstantlytakes overCustomer no.Not involvedholdsCustomer numbertakes overCustomer no.takes overCustomer no.
Contacts and quotesinstantlyNot involvedNot involvedtakes overOrderholdsQuote wonNot involved
Invoices and recordsat fixed intervalsNot involvedNot involvedholdsInvoiceNot involvedtakes overRecord

How we carry over data when you change systemsData Integration & Migration

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.

  1. 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.
  2. 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.
    Process Automation
  3. Middleware or iPaaS

    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.
  4. 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.

  • SAP
  • Microsoft Dynamics 365
  • Odoo
  • JTL
  • Xentral
  • plentymarkets
  • weclapp
  • DATEV
  • sevDesk
  • Lexware Office
  • HubSpot
  • Salesforce
  • Pipedrive
  • Zoho CRM
  • Shopware
  • Shopify
  • WooCommerce
  • Magento
  • Amazon
  • Otto
  • eBay
  • Kaufland
  • PayPal
  • Stripe
  • Klarna
  • Mollie
  • DHL
  • DPD
  • UPS
  • GLS
  • n8n
  • Make
  • Zapier

ASES in numbers

  • 1 teamOur own team, no subcontractors
  • 15+More than 15 years of experience on the team
  • 35+Companies in more than 35 countries work with us
  • 10Conversations in ten languages
About ASES

Frequently asked questions about system integration

Answers on costs, systems, data flows, operation and data protection for your interfaces.

Let's talk about your interfaces

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.

  • Free initial consultation
  • No obligation
  • NDA on request