Turn your ERP Integration into a Cloud App
A new merchant calls. They just switched accounting software and want their JTL-Wawi (also known as ERP) orders to flow into it automatically. You know exactly what they need, because you've built it four times already. So you do what you always do. You copy the last project, adjust the field mappings, and book a day to install it on their server. You set up remote access, test it, hand it over,…
Turn an ERP Integration into a Cloud App: A Reporter's Account
A new merchant recently switched accounting software and requires their JTL-Wawi (also known as ERP) orders to flow automatically into the new system. As this scenario is not new, we can replicate the previous project, modify field mappings, and schedule a day for installation on their server. After setting up remote access, testing, and handing over the solution, the integration is added to the maintenance list.
While this works and generates revenue, it's worth questioning if the build could instead be an install instead of a project.
Cloud Apps offer a solution to this problem. In this article, we will discuss how to turn a frequently rebuilt integration into a once-built, installable app for every client. This includes the consistent parts, variable parts, and trade-offs. If you are new to Cloud Apps, begin with "What are JTL Cloud Apps?" to familiarize yourself with the basics. The article assumes readers have basic knowledge of the subject.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
