To maximize the value of a field inventory system, best practice dictates integration with an ERP system. While most companies have an ERP system, the thought of integration is concerning because of the associated complexity and cost. To prevent this, we adopted a newer integration strategy. This methodology isn’t unproven, however, and several leading technology companies have already employed it. One of the best examples of a well-executed webhook strategy is Paypal – they integrate with almost any payment system to simplify the buying process for customers.
“… One of the best-executed examples of a webhook strategy is Paypal …”
Using this cutting-edge technology, our integrations are faster and more cost effective when compared to other legacy approaches. We leverage an open API structure, enabling clients to easily integrate not only their ERP, but a CRM, finance or logistics platform as well, without the traditional complexity and cost that would accompany such integrations. Figure 1 shows how TurnsLift’s architecture differs from the traditional integration methodology.
For any integration, TurnsLift uses webhooks to send data to an ERP. A webhook is an HTTP callback that is usually triggered by some event, such as creating a case, requesting inventory, shipping kits, billing a client, etc. Simply put, a webhook is the ability for a SaaS solution to push data to a secure url address, which your ERP will automatically read and consume. When the event occurs, the SaaS solution sends an HTTP request to the URL configured for the webhook , containing the details about the event.
“…Simply put, a webhook is the ability for a SaaS solution to push data to a secure url, which your ERP will automatically read…”
What this means in practice, is that any time something changes in your SaaS solution (like the status of a case), your ERP will be updated. This happens without the need for copious amounts of custom code, transformation layers or anything of that sort. Webhooks come pre-configured out of the box, letting you cut down on integration time and cost. That being said, the ultimate question remains, how does this impact the total cost of an integration? Check out Figure 2 below.
If ROI on a field system is partially driven by a successful integration with a client’s ERP system, then a SaaS company must ensure that the integration is robust and repeatable. Seldom do clients only want one integration; ideally there are multiple integration points so real-time data can be passed between systems and everyone benefits form the increased efficiency that accompanies an integration.
For more information on how this might work for your organization, reach out to our TurnsLift team by sending an email to email@example.com. We’d be happy to answer any questions you might have.