NL

    Integration

    AFAS integration

    Connect AFAS Profit to your warehouse, webshop or CRM so finance and operations work from the same numbers. We select, build and run the integration and stay your point of contact.

    What is connected

    Which data moves between AFAS and your other systems?

    AFAS keeps the books. Articles, purchase orders and sales orders go to the WMS or webshop, and receipts, deliveries, counts and stock corrections come back into AFAS. Nobody has to re-key any of it.

    First we settle which system is the master for which piece of data. Which further messages you need, such as webshop orders or production, depends on your process and on the AFAS modules you use.

    How it works

    How the integration works

    For a WMS integration we often use the integration layer of BizBloqs. According to BizBloqs, the AFAS Profit connection runs through the AFAS app connectors: data is read from AFAS with GetConnectors and written back with UpdateConnectors. You create the app connector and the token in your own AFAS environment. You can revoke that token from AFAS, and you decide which fields are visible.

    Messages that fail stay visible and can be sent again.

    You ask Operion your questions, not BizBloqs. We coordinate the work with BizBloqs and your other suppliers.

    Cost and lead time

    Cost, lead time and intake

    What an AFAS integration costs and how long it takes depends on the systems involved and the number of data flows. After a free intake call, we give you a fixed quote.

    We connect through the official AFAS APIs and check during the intake whether your modules are covered.

    Process

    How an AFAS integration runs

    1. 01

      Take stock

      Which AFAS modules, which data and which processes. We record which system is master for what.

    2. 02

      Connect

      You create the app connector and token in your own AFAS environment, and we validate the connection on a test environment.

    3. 03

      Map the data

      We decide how articles, orders and stock line up in both systems.

    4. 04

      Test round

      The integration is run through real scenarios from your daily work, including failures.

    5. 05

      Go live and run

      Go-live with monitored message flows. After that we run the integration.

    This is part of our Integration service. If you use another system, also see custom API integration or Exact Online integration.

    Questions

    Frequently asked questions

    Can I control what the integration can access in AFAS?

    Yes. You create the token in your own AFAS environment, you can revoke it yourself and you decide which fields the integration may see.

    Are my AFAS modules supported?

    We connect through the official AFAS APIs and check during the intake whether your modules are covered.

    What happens if a message does not arrive?

    Failed messages stay visible and can be sent again, so nothing disappears quietly.

    What happens after go-live?

    After go-live you get four weeks of aftercare. After that you can reach us on working days from 08:30 to 17:00, and we respond within 24 hours.

    Need an AFAS integration?

    Tell us which systems AFAS needs to talk to. We will explain how we would approach it and what we need to get started.