Tuesday, 7:45 a.m. Inside sales arrives at the office, and last night's requests are already in Mercura. The AI has read them, matched every line item to a product in your range and prepared the quotes. Now the team reviews: adjust a quantity here, pick an alternative there, approve. One click, and the quote is in the ERP. Nothing gets re-keyed.

ERP integration makes that possible. This guide explains which data flows between Mercura and your ERP, CRM or PIM, which integration options exist, how to recognize a good integration and how we run integrations under the hood.

Key takeaways

• Definition: An integration connects two systems so data flows between them without manual entry. With Mercura: master data in, quotes and orders back.

• Systems: Essentially any ERP, CRM or PIM, because you decide whether Mercura pushes the data or your system pulls it.

• Three options: your system pulls data via the Mercura API, Mercura pushes it via webhook, or you exchange files via SFTP. Mercura can also fetch master data from your APIs via the Integration Suite.

• Middleware: usually needed, unless your system can call APIs itself, exposes its own APIs or exchanges files via SFTP.

What data flows between Mercura and your ERP?

From your system to Mercura:

• Products with descriptions, units, prices, ETIM features, successors, alternatives and accessories

• Customers and business partners

• Suppliers

• Contacts

From Mercura to your system:

• Quotes with all line items, matched products, quantities and prices

• Captured orders with matched line items

• Status updates, for example when a request has been processed

Your system can confirm receipt, so both sides always know which quote has already arrived. Without integration, Mercura is an island: the AI works with outdated product data and every finished quote has to be keyed into the ERP again.

What are the ERP integration options?

Mercura isn't tied to any specific system. You choose one of three options and decide who triggers the exchange.

1. The Mercura API: our recommended option. The API is the most flexible option and the one we invest in most. You keep full control over which data flows when and in which direction. Your system asks what has been completed since the last call and fetches it. You set the frequency. Optionally, Mercura also notifies your system via webhook as soon as something is ready.

2. SFTP: file-based exchange. Every organization can set up its own SFTP access in Mercura's settings. Your system drops master data as a file; you map the columns once and Mercura processes every new file automatically. In the other direction, Mercura drops quotes and orders as CSV, Excel, JSON, XML, GAEB or SAP IDoc files.

3. Direct connection via webhook push. If your system already exposes APIs, Mercura can call them directly. We configure the webhook payload to match the format your API expects, so your IT doesn't need to build anything new. In the other direction, the Integration Suite fetches master data from your APIs on a schedule you set.

Which systems can Mercura integrate with?

• ERP: SAP S/4HANA, SAP ECC, SAP Business One, Microsoft Dynamics or your industry ERP. Products, customers and prices come from here; finished quotes and orders go back here.

• CRM: Mercura sends quotes with all line items to your CRM, for example Microsoft Dynamics 365. Customers and contacts can come from there.

• PIM and product data: products with descriptions, technical features and successors come straight from your PIM.

• Email: requests reach Mercura directly from your inbox, by forwarding or via the Microsoft Outlook connection.

• User management: single sign-on and automatic user provisioning via SCIM, for example with Microsoft Entra ID.

6 criteria for a good ERP integration

An integration is only as good as its behavior on a bad day.

How Mercura runs integrations under the hood

This section is for your IT team. All integrations run on four standard building blocks of the Mercura platform, set up by configuration rather than custom code.

• Mercura API: your system sends master data to Mercura and fetches finished quotes and orders. Publicly documented and versioned.

• Integration Suite: Mercura fetches master data from your REST or OData API on your schedule, authenticated via API key or OAuth 2.0, with fields mapped by configuration.

• Webhooks: Mercura sends quotes, orders and status updates to your system, with a configurable, signed payload.

• SFTP: your system drops or picks up files on Mercura's SFTP; column mapping is set once and applied automatically.

Operations: imports and deliveries run asynchronously, failed deliveries are retried automatically, credentials are stored encrypted, rejected credentials pause the connection and notify admins by email, and every delivery is logged and can be re-triggered.

Further reading

• Integrations: connect Mercura to ERP, CRM and PIM

• SAP Integration for Orders: Email Orders Into SAP

• Dynamics 365 Integration: Automate Order Entry

• Customer story: Sanitär-Heinze (plumbing and HVAC wholesale)

FAQ

Which systems can Mercura integrate with?

Essentially any ERP, CRM or PIM. You decide who triggers the exchange: Mercura pushes data to your system via webhook, or your system pulls it via the Mercura API. Whether SAP, Microsoft Dynamics or an in-house system, all that matters is that your system or a middleware layer can work with APIs.

Do we need middleware?

Usually yes. You can do without it if your system can call APIs itself, exposes its own APIs that Mercura can write to, or can export and import files via SFTP. Otherwise a middleware layer translates between Mercura and your systems; many companies already have one.

What is the difference between API and SFTP?

Via the API, Mercura and your system exchange data directly and in real time. With SFTP, both sides drop files in a secure folder that the other side processes automatically. SFTP is easier to set up; the API is more flexible and faster.

How long does an ERP integration take?

It depends on the system and project scope, from a few days to a few months. The scope of data flows and the testing phase in your test systems make the biggest difference.

How secure is the data exchange?

All transfers are encrypted via HTTPS or SFTP. Webhooks are signed, credentials are stored encrypted, and each organization sees only its own data.

Can our IT team build the integration itself?

Yes. The Mercura API is publicly documented, so your IT team or IT partner can build the integration on their own. We support them with test access and sample data.

Bottom line: a quote is only finished when it's in the ERP

The best quoting AI is of little use if its output has to be re-keyed. Good ERP integration closes the loop: current master data from ERP, CRM and PIM in, finished quotes and orders back, with no handoffs. With Mercura, you decide the route and the frequency.

Book a demo or dive straight into the API documentation.