Frequently asked questions.

Met een gratis proces-scan van een uur. We kijken naar je orderstromen, systemen en het handwerk daartussen, en je hoort meteen waar de winst zit en wat realistisch is. Daarna volgt een fixed-fee offerte, zodat je vooraf weet waar je aan toe bent.

Een kort, vrijblijvend gesprek waarin we je proces in kaart brengen: welke systemen praten met elkaar, waar zit dubbel werk, en welke stappen kunnen weg. Geen verkooppraatje, wel concrete punten waar je ook zonder ons iets aan hebt.

Graag. Wij bouwen de koppeling of het portaal en de integratielaag eromheen; jouw partner of interne afdeling regelt waar nodig de inrichting en autorisaties aan hun kant. We documenteren elke interface, zodat het voor iedereen navolgbaar blijft.

Van mkb tot multinational, vooral in logistiek, groothandel, productie, retail en zakelijke dienstverlening. De rode draad is een operatie met veel handmatig werk tussen systemen. Sinds 2008 bouwden we zo 50+ portals en integraties.

We're a small team, sometimes the queue runs a few weeks. Better honest up front than stuck halfway in. If it's genuinely urgent and we can't take it, we'll think along about partners who can at that point.

Yes. Quote requests come in via a central overview, plus optionally as a notification to your sales team or directly into your ERP/CRM. We connect it to what you're used to.

In 16+ years it hasn't happened, but if during scoping we doubt the fit, we say so. Better honest up front than stuck halfway in. Sometimes a hybrid with a SaaS tool is the smarter path, we'll think along.

In de praktijk vrijwel alles met een API, EDI-bericht, database of bestandsexport. Denk aan ERP's als Exact, AFAS, SAP, Dynamics en Oracle, webshops als Shopify, WooCommerce en Magento, WMS-pakketten als Boltrics, en betaalproviders, PIM- en CRM-systemen. Staat jouw pakket er niet bij? Dan kijken we in de proces-scan of het kan.

Vrijwel altijd. Heeft je applicatie een API, database of bestandsexport, dan bouwen we daar een koppeling op. We hebben tientallen maatwerk-pakketten gekoppeld, van planningstools tot productiesystemen.

Waar het kan werken we met webhooks en events, zodat wijzigingen binnen seconden doorkomen. Systemen die dat niet ondersteunen, pollen we met korte intervallen. In de scope leggen we per stroom vast wat je mag verwachten.

Elke koppeling heeft retry-logica met exponential backoff. Berichten die niet doorkomen, landen in een wachtrij en gaan alsnog door zodra het systeem weer reageert. Er gaat niets verloren, en je ziet in de monitoring wat er speelt.

Yes. Both run on the same Connector foundation, so the technology is the same. SB+ has a more compact setup than Profit, which often makes the scope smaller. In the process scan we quickly see what your environment can handle.

Yes. Shopify, WooCommerce, Magento and custom shops have all been connected to AFAS by us before. Orders and customers go to Profit, while stock, articles and customer-specific prices come back to the shop.

AFAS applies limits on the number of calls, so we build integrations that bundle smartly and stay neatly within those limits. If AFAS is briefly unavailable, messages stay in a queue and go through automatically afterwards. Nothing gets lost.

Boltrics runs on Microsoft Dynamics 365 Business Central. We connect through the web services and OData the platform offers, on the standard pages and tables. That keeps the integration neatly within what Boltrics allows, without changes that get in the way of updates.

Yes. Whether Boltrics runs in the Business Central cloud or on-premises, we connect to the web services that are available. In the process scan we look at which variant you use and what that means for the integration.

Yes, if Boltrics allows it. We previously built a web service that let a customer adjust batches of their own products directly in the WMS, with strict scope isolation so a customer can only reach their own stock. Self-service on stock and mutations is very doable.

Business Central and the former NAV, Finance & Operations and the former AX, and Dynamics 365 for sales and relationship management. Each has its own interfaces. In Business Central we work with OData and API pages, in Finance & Operations with data entities, and for CRM with Dataverse.

Yes, both. We connect Dynamics 365 in the cloud via the official APIs and OAuth. For on-premises NAV or AX we connect to the web services or an intermediate layer. In the process scan we determine which route is most stable for your environment.

Almost always. If your application or extension has an API, database or file export, we build an integration on it. We have connected dozens of custom packages to Dynamics, from planning tools to production systems.

The common standards: EDIFACT, ANSI X12, GS1 variants and PEPPOL BIS, alongside XML, JSON and CSV for partners that don't run classic EDI. In terms of messages it's usually ORDERS, ORDRSP, DESADV and INVOIC, but we also cover inventory and status messages.

Both work, and often it's a mix. Direct AS2 or OFTP2 connections are cheaper to run and faster, a VAN is sometimes mandatory because the partner requires it. We advise per partner what makes sense and manage both options.

No, that's exactly our job. The EDI layer translates your partners' messages into what your ERP can actually receive: an API call, an import or a database connection. We even bring legacy packages without a modern interface into the chain this way.

Every message is tracked from dispatch to the partner's functional acknowledgement. If an acknowledgement fails to arrive or a message is rejected, a retry follows automatically, and persistent errors trigger an alert with the cause. You stay informed through reports and the audit trail.

Yes, both. We connect Exact Online via the REST API, Globe via the interfaces available for it. The differences sit in details like journals and VAT handling, and we know those from previous projects.

Yes, via webhooks or short polling intervals, depending on what your Exact version supports. In practice a stock change is on your site within seconds to a few minutes.

For them in particular a portal is the low-threshold route: log in via the browser, no software to install, no IT department needed. We deliberately keep the screens simple, registering a delivery takes a supplier a few minutes at most.

Yes, and that is often the biggest gain. Quality certificates, safety data sheets and packing slips are uploaded to the right order or the right article. The portal monitors expiry dates and sends reminders itself, so you do not have to chase anything during an audit.

Yes. We connect the till (Retail) and the webshop (eCom) both, and bring till turnover and webshop orders together in one flow to your ERP or accounting. Which parts you use determines which flows take part.

Exact Online, AFAS Profit, SnelStart and various WMS packages, among others. We talk to the Lightspeed API on one side and to the API or interface of your package on the other.

Both are possible. Many retailers post a daily total per store with a breakdown by VAT and payment method; those who want more detail can post per ticket. In the scope we set down what fits your administration best.

Yes. We link stock per store to the locations in your ERP or WMS, so every store and the webshop show the same, current figure.

Yes. You manage items, variants and prices in your ERP or PIM, and we push them through to Lightspeed. That way you no longer maintain the assortment in two places.

Yes, both. The APIs are largely the same; Adobe Commerce adds B2B features such as company accounts, shared catalogs and requisition lists. We connect on the standard REST and GraphQL API, so your edition mainly determines which B2B flows take part.

SAP, Exact Online, AFAS Profit and various WMS and PIM packages, among others. We talk to the Magento API on one side and to the API or interface of your package on the other, so the choice of ERP is rarely a blocker.

Yes, that is often the core. We take customer-group prices, shared catalogs and company-specific conditions from your ERP and put them into Magento, so every customer sees their own price without double maintenance.

We bundle calls smartly, work with delta synchronisation so only changes go along, and respect rate limits neatly. That keeps the integration running smoothly even with tens of thousands of products and orders.

Yes. We link stock per source to the locations in your ERP or WMS, so stock per warehouse adds up and MSI in Magento shows the right figure.

Through the Multivers API. We write sales invoices, entries and debtors into the standard administration and read data back where needed. That keeps the integration neatly within what Multivers allows, without changes to your database.

Yes. Whether you use Multivers Online or a locally installed version, we connect to the available API. In the process scan we look at which variant you run and what that means for the integration.

Yes. We match on fixed attributes such as email address or account number before a new debtor is created. If the customer already exists in Multivers, we update them instead of creating a duplicate relation.

Yes. For ERP Cloud we work with the REST services and FBDI imports, for NetSuite with the REST API and SuiteTalk, and for E-Business Suite with the available interfaces. In the process scan we determine the most stable route per flow.

Yes. Messages in EDIFACT, X12 or another format we translate to the right format and process straight in Oracle, with statuses and confirmations back to the partner.

We bundle where we can, work with queues and retries, and account for Oracle's API limits. That keeps the chain running reliably even at peak volume.

Yes. We connect on the Webservice API, which is largely the same across these versions. With older or heavily customised shops we take a quick look in the process scan, so we choose the right route.

Exact Online, AFAS Profit, SAP, SnelStart and various WMS packages, among others. We talk to the PrestaShop Webservice API on one side and to the API or interface of your package on the other.

Preferably not as the only layer. Modules are handy for the simple work, but they get stuck on customisation, B2B prices or a custom order type. We build the integration outside your shop, so a module update or theme switch does not bring your order flow down.

Yes. Multiple PrestaShop shops, languages and currencies come together on one integration layer with your ERP, with its own rules per shop for stock, prices and VAT.

Yes. Before go-live we migrate existing orders, customers and items once, so your history and open items add up. We de-duplicate at the same time, so you start clean.

Yes. For S/4HANA and ECC we work with IDoc, BAPI, RFC and OData; for Business One with the Service Layer and DI API. In the process scan we determine which interface is most stable per flow for your system.

Yes. Messages in EDIFACT, X12 or another format we translate to the right IDoc types and process straight in SAP, with statuses and confirmations back to the partner.

We bundle messages where we can, work with queues and retries, and account for SAP's processing capacity. That keeps the chain running reliably even at peak volume.

Among others Exact Online, AFAS Profit, SAP, SnelStart and various WMS packages. It makes little difference to our approach: we talk to the Shopify Admin API on one side and to the API or interface of your package on the other.

Yes, that is precisely the strength of an own integration layer. Multiple stores, Shopify Markets, currencies and languages come together on one integration with your ERP, with separate rules per market for stock, prices and VAT.

Yes. Before go-live we can transfer existing orders, customers and articles once, so your history and outstanding items are correct. We deduplicate at the same time, so you start clean.

Through the SnelStart API. We write sales invoices, entries and debtors into the standard administration and read data back where needed. That keeps the integration neatly within what SnelStart allows, without changes to your database.

Yes. We connect to the available SnelStart API. In the process scan we look at which version and modules you use and what that means for the integration.

Yes. We match on fixed attributes such as email address or account number before a new debtor is created. If the customer already exists in SnelStart, we update them instead of creating a duplicate relation.

That depends on what your WMS or ERP offers. With webhooks or events a change is in the portal within seconds, with polling we work with short intervals of a few minutes. During the process scan we tell you honestly what your system makes feasible.

Yes. You arrange permissions per user or per organization: which assortment, which warehouses, and whether someone sees exact quantities or only an indication. A logistics provider can thus let each client see only their own goods.

InStock is our ready-made stock portal: proven functionality, fast live, lower entry. You choose custom work when your process asks for more, such as reserving, ordering or a combination with a customer portal. Many customers start with InStock and grow on later, which works on the same foundation.

Exact Online, AFAS Profit, SAP, SnelStart and various WMS packages, among others. For our approach it matters little: we talk to the WooCommerce REST API on one side and to the API or interface of your package on the other.

Preferably not as the only layer. Plugins are handy for the simple work, but they get stuck on tiers, bundles, VAT per country or a custom order type. We build the integration outside your WordPress, so a plugin update or theme switch does not bring your order flow down.

Yes. Multiple WooCommerce sites, languages and currencies come together on one integration layer with your ERP, with its own rules per shop for stock, prices and VAT.

Almost always. We've worked with Exact, AFAS, SnelStart, SAP, Oracle, Business Central, NetSuite, Lightspeed, Salesforce, Dynamics, and bespoke apps. API, file or webhook: anything with an interface, we can connect.

We build integration layers around message queues (RabbitMQ, SQS, Redis streams) and async workers. A few hundred messages per minute is standard, thousands per second is achievable if we design the architecture for it. Load and growth projections go into scope.

We design for it from day one. Mapping configuration lives in tables or YAML, not hard-coded. A new supplier, format or field can be added by someone on your team (or us) without a release.

Out of the box with Boltrics (WMS), AFAS, Microsoft Dynamics 365, Exact, e-Boekhouden, Visma, SAP, Oracle, Business Central and RouteLogic. If your system has an API or file format, we can almost always connect to it.

Yes, that's the default. Insight runs on portal.yourcompany.com (or any subdomain you prefer). Including your own SSL certificate and full branding alignment: logo, colours, typography.

That's exactly what Insight is good at. Bespoke modules are built at relatively low rates and often without recurring monthly costs. Specific data integrations, custom tables or extended fulfilment modules, we build it in.

Yes, Insight includes a personalised manual module configurable per client or client group. Plus at go-live we produce short intro videos and an onboarding manual tailored to your operation.

Out of the box with AFAS, Exact, SnelStart, SAP, Oracle, Microsoft Dynamics 365, Business Central and e-Boekhouden. If your ERP has an API or file format (CSV, XML, JSON), we can almost always connect to it.

Yes. Per client account you set which price list or volume tier is visible. Dealer-specific conditions, volume discounts or contract pricing, all configurable without clients seeing each other's prices.

No problem. InStock syncs with your ERP several times a day by default. New items appear, old ones disappear or are flagged. More frequent syncing is possible, up to real-time.

Almost always. We've worked with Exact, AFAS, SnelStart, SAP, Oracle, Business Central, NetSuite and bespoke ERPs. If yours has an API or file format, we'll talk to it. If not, we build the missing piece.

We build toward that by default. Modular, API-first, with clear data models. A second customer group, new role, extra integration or new language goes in as iterations, no rebuild.

EDI is about standardised batch messages between trading partners and has existed for decades; APIs are more modern, real time and more flexible. In practice we often use both: EDI towards partners who expect it, APIs towards webshops and modern systems.

Not necessarily. Sometimes we connect directly via AS2 or SFTP, sometimes via an existing EDI provider or VAN. In the process scan, we determine which route is most stable and cost-effective for your partners.

Yes, that is the core of a B2B order portal. Price agreements, volume tiers and discounts come from your ERP and apply automatically per customer. You also steer the assortment per customer or customer group: a hospitality customer sees something different than a retailer.

We connect with GS1 Data Source or your PIM, so product sheets, allergens and nutritional values are automatically up to date. If a supplier changes its recipe, your customers see it without anyone having to update anything. Your own additions per product remain possible.

Both are possible. The portal works responsively in any browser, also on a phone in a busy kitchen. If you want a real app with barcode scanning or offline order lists, we build it on the same foundation.

Yes. Orders from the portal land directly in your ERP as sales orders, and stock and prices flow back. If you also have a POS system such as Lightspeed, we feed the portal and the POS from the same product source, so no differences arise anywhere.

Yes. You manage which products can be ordered and when, with promotional prices, end dates and featured blocks on the order page. You prepare a Christmas assortment and activate it on the day it should go live.

Yes. We know Boltrics from earlier projects, and we also connect other WMS and TMS packages via their APIs or message traffic. If your package has no proper API, we work with file exchange or database views. In the process scan we look at what your environment can handle.

We set up the message flows your partners expect: orders, order confirmations, shipping notices and invoices in formats like EDIFACT or X12, via AS2 or SFTP. The portal and the EDI layer share the same data, so an order that comes in via EDI is immediately visible to your team and your customer.

That is up to you. Usually: the current status per shipment, expected delivery time, proof of delivery and the related documents. The data comes straight from your TMS, so customers see the same as your planners. Per customer you set who is allowed to see what.

Yes. Carriers and customers book a time slot themselves within the limits you set: number of docks, block times, type of cargo. Double bookings are impossible and your warehouse sees tomorrow's schedule ready and waiting.