winemaker.com is a platform that delivers wine directly from wineries to end customers all over the globe. A crucial benefit of using winemaker.com is that they also take care of all related customs documentation - something that can usually be tricky to handle when alcohol (and tobacco for that matter) are transported across borders - whether within EU or for example to Switzerland.
We spoke with Elian Kool to dig into the value that winemaker.com is getting from using PDF Generator API and their specific use case.
winemaker.com has been our user for almost 3 years, and is using our Zapier integration for the generation of various client-oriented documentation - invoices, shipping labels, to name a few. All of winemaker.com’s data is kept in their central - Studio database and queried using Zapier. The main processes winemaker.com has implemented using PDF Generator API (so far) are invoicing and shipping. And while they service their customers in 4 languages, the number of different document templates grows fast.
winemaker.com has been our user for almost 3 years, and is using our Zapier integration for the generation of various client-oriented documentation - invoices, shipping labels, to name a few
In PDF Generator APIs case, winemaker.com uses Zapier to call the correct template, in the correct language - and on the basis of this the correct invoice, in the correct language, and containing the correct data is generated. The process is very similar to the fulfillment process, the documentation there consists of delivery slips and packing labels. Elian points out that, while they are constantly developing their technology stack and utilizing more functionality of PDF Generator API while doing so, the initial setup was straightforward and took only a few days.
According to Elian, building a similar tool in-house would have probably required 10-fold the same resources as opposed to taking an external tool and implementing it using the API. That allowed them to focus on building their core product, and not spend valuable resources on what are essentially non-essential functionalities. It is also worth noting that the distinction between initial development time and maintaining the system was also a key influencer.
According to Elian, building a similar tool in-house would have probably required 10-fold the same resources as opposed to taking an external tool.
With PDF Generator API and its drag-and-drop, what-you-see-is-what-you-get editor, which was something winemaker.com had been specifically looking for, the employees can create and manage the templates themselves - as opposed to running every template change through the normal development cycle, further inflating the resource needs.
Employees can create and manage the templates themselves - as opposed to running every template change through the normal development cycle, further inflating the resource needs.
When I ask Elias what type of companies would benefit from using PDF Generator API the most, he says this product is actually suitable for any client that wants to have flexible processes. Many companies still think they need to code everything themselves. So, it would be safe to say that it is probably not meant for companies that have all of their processes ready and running as needed. It is, however, really good for companies that are still figuring out what the best approach is, and hence still have evolving processes and procedures that are not set in stone.
Adaptation of various no-code, low-code solutions is really booming. In addition to PDF Generator API, winemaker.com utilizes DocuSign for contracts, Jira for managing issues, Google Calendar, Google Drive for managing files, Revolut for credit card management - which is directly integrated with bookkeeping systems. SendinBlue for transactional emails flows, shipping providers, Slack, Trustpilot, GitHub - as a testament to the adaptation of no-code/low-code, winemaker.com uses close to 30 different integrations as part of their technology stack.
To conclude - Elias says PDF Generator API did exactly what they were looking for. It was easy to integrate with Zapier. Everything just worked as they wanted too! And super easy to implement! Over time the complexity of their use case will most definitely increase, but we are off to a great start!
As you can see, PDF Generator API is truly a flexible product that adapts to the needs and requirements of its customers, regardless of the sector - independent of whether it is implemented on top of an existing stack or used as a building block for something entirely new. We hope these case studies will help anyone interested in ways to utilize PDF Generator API to further their own business to gain insights, examples and best practice in making the most out of the tool.