Setting up integrations

You set up an integration via Settings › Master data › App connector › Apps.

1. Choose Add app and select the service you want.
2. Save the app.
3. Open Connection and authorise, or enter the details provided by the supplier.
4. Choose the correct external organisation, shop, division or profile.
5. Set up the synchronisation direction, actions, matching fields and mappings for each data type.
6. Test one contact, one product and one transaction before you activate automatic synchronisation.
7. Check History › Synchronisation for successful processing.

An app in the list means the connector is available. It does not automatically mean that every data type or direction is active for your organisation.

Before you start, decide for each data type which system is leading: for customers, products, prices, stock, orders and payments.

For webshops the safe default is: one leading system for the product structure, one for prices and one for stock. If you manage the same field in both directions, the risk of overwriting and synchronisation loops increases.

Never change the synchronisation direction, matching fields and mappings for a large data set at the same time. Change one thing, test with one record and check both systems. Always make a reference export before changing the synchronisation direction.

Each app has its own combination of synchronisation settings. The most important are:

• Synchronisation direction per data type: from the app to Count-IT, from Count-IT to the app or both ways.
• Add, edit and delete: which changes may go to the other side.
• Automatic and manual synchronisation: in the background, or a controlled full or partial run.
• Matching fields: how existing records are matched, for example on item number.
• Value and field mapping: translates, for example, VAT, units, journals, warehouses and payment methods.
• Email address for synchronisation errors: receives a notification when processing fails permanently.

The Exact Online integration exchanges master data (such as contacts and products), sales and purchase orders, invoices and stock in both directions.

Exactly what is exchanged depends on your set-up and your Exact subscription. Some Exact processes do not accept different contacts for “invoice to”, “ordered by” and “deliver to”; the app has a setting that makes them the same.

Count-IT also integrates with other accounting packages, such as e-Boekhouden.nl, Moneybird, Visma eAccounting, AFAS Online, Uniconta and SnelStart. See the integrations page.

Shopify: products, product groups and orders come from Shopify into Count-IT; stock and prices go from Count-IT to Shopify. Matching is usually done on a stable item number or external identifier.

WooCommerce: customers, products and product groups are synchronised in both directions; prices, discounts and stock go to WooCommerce, and orders come in from WooCommerce.

Are changes in WooCommerce overwriting each other? Then both systems are probably leading for the same field. Set one direction for each type of product data and then check one product.

Magento 2: Count-IT exchanges customers, products, stock, prices, discounts, shipments and loyalty points, and orders come in from Magento. In the Magento 2 app, under Settings, enter the store ID you want separately for Product price - Store ID and Discount - Store ID; 0 keeps the default processing.

Shopware: this integration is used for gift cards and vouchers.

Count-IT integrates with payment providers for in-store and online payments.

• Buckaroo: in-store payment terminals and Buckaroo Tap to Pay.
• Mollie and Pay.: online payments and payment links on invoices and orders.

A provider must be correctly linked both as an app and to a payment method or local device. In case of a fault, check the app status, terminal status, payment method and the device the POS runs on. Count-IT also supports various local terminals; see hardware.

For fulfilment, Count-IT integrates with Monta and 3BM. With Centraal Boekhuis you retrieve the assortment and send purchase orders electronically.

You activate supplier integrations alongside the general app connector; the supplier then shows a Supplier data section. Assortment synchronisation can overwrite selected fields in Count-IT. So first check which fields the supplier provides and link a small selection.

Fiskaly provides the TSE (technical security of POS data) and the DSFinV-K export for German fiscal regulations.

Scrada handles Belgian daily receipts and the cash book, and sending invoices via Peppol.

These functions depend on the country and contract. Only change fiscal mappings or device registration in consultation with an authorised administrator or adviser. Read more about fiscal requirements on the certification page.

With webhooks, Count-IT receives changes from a partner faster than with periodic synchronisation, if the service supports it. A payment provider can, for example, pass on a payment status straight away.

You can see received webhooks in History › Synchronisation: an app shows the Webhooks tab as soon as there are webhook subscriptions for your company. Use Added on (from) and Added on (to) to filter by time of receipt.

When you delete an app, Count-IT first unsubscribes the webhooks. So do not revoke the external access beforehand.

Yes. Count-IT has a REST API with OAuth2 for your own apps and custom integrations. You create an API app for this and receive a client identity and secret.

Treat these details as secret and never share them by email, chat or in documentation. Record who the owner is, which data the app may use and how access is revoked. Use a separate identity for each integration. If access does not work, check whether the function is enabled, the secret is still valid and the creator has sufficient rights.

Through the Count-IT MCP server, a supported AI assistant can read your data for analysis, within the rights of the user who created the token.

1. Switch on AI data access for your organisation.
2. Create a personal MCP token under App connector.
3. Give it a recognisable name and an end date, and store the token securely.

The token has the same rights as its creator, so use a user with as few rights as possible. Revoke the token when it is no longer needed or may have leaked, and then create a new one.

You view and resolve synchronisation errors in History › Synchronisation.

1. Filter by app, data type and status, or search for (part of) the error message.
2. First resolve the oldest underlying error, for example a missing customer or product mapping.
3. Click an error line. For supported errors you will find Analyse error; the analysis only runs checks and shows possible solutions that you confirm separately.
4. Then use Try again.

A full synchronisation can overwrite local values; only use it after checking. With the copy icon next to the error analysis, you copy the analysis as text to discuss with support.

“Invalid authorisation” means that the permission for the integration has expired, has been revoked or belongs to a user without sufficient rights.

Open the app, check the selected organisation and reconnect via Connection. Do not change any synchronisation settings if only the authorisation has expired.

When you delete an app, Count-IT cleans up the integration, but your products, customers and other business data remain.

First, Count-IT unsubscribes the webhooks that are no longer used by another integration. Then automatic synchronisations, open and failed synchronisation tasks, ID links, field mappings and app settings are removed. Successful synchronisation tasks and existing logs are kept.

If processing is still running, the deletion may be refused with In progress; wait and try again.