case study

Goodlok

summary: In this case study, we look at how we helped Goodlok create a API-first foundation for its digital activities in just two days of work. If you're interested in building your own small ERP system or are just curious about what's possible with Contember, this is definitely one project that makes the most of the Contember Engine.

Headless backend for coldpress fresh delivery

We want to drink well and have a healthy gut. Goodlok makes coldpress vegetable and fruit freshes. And delivers them via mobile app around Prague. They also have a cafe, a fresh room and a fermentation plant at Jungmaňák.

We like their products, and when they told us they needed a new backend for their day-to-day operations because the old one wasn't flexible enough and hard to maintain, we knew Headless and Contember was the way to go.

This is a short story about how we helped them get their new headless backend up and running in two days.

Juices

"We make coldpress vegetable and fruit freshes. And deliver them via mobile app around Prague. Then we built a cafe, a freshroom and a fermentation plant at Jungmaňák and things have been happening ever since."

Our goal was to build something for them that would be flexible enough for the future and provide them with a fast and secure GraphQL API. Plus set up administration for the internal Goodlok team. Goodlok has access to some front-end developers from time to time, so they can build basically anything they need on the front-end. The backend is much more painful and that's one of the reasons Contember makes so much sense.

We sat down with them and quickly went through their processes and plans and translated the vision into concrete tasks:

  • 1
    Create a data model for orders, customers, products, recipes and raw materials.
  • 2
    Building an administration for the people who manage orders and deliveries
  • 3
    Secure data for multiple user roles using role-based ACLs
Photo of whiteboard with Goodlok schema
Photo of team discussing stuff

We quickly realized that it was actually a small ERP. Well, why not. It raised a few questions:

  • ?
    How much of the e-commerce functionality should be handled directly by Contember?
  • ?
    How does the taxation of things like gift cards work?
  • ?
    What does working in the old Goodlook system look like, and what can we adopt to get users used to the new one quickly?

After answering these questions with the Goodlook team, it was time to start coding.

Results

We created a data model of the basic parts of the Goodlok backend. There are users, companies, products, resources, price groups and more. Order prices are calculated through the PostgreSQL view. We also laid the groundwork to easily add functionality to calculate the price in the cart and the entire shopping process.

We had the most fun with user roles and permissions. We took advantage of Contember's advanced role-based ACL functionality and, for example, there is now a "courier" role that only sees a user's contact information for orders that have been assigned to them for delivery. And only until they are marked as delivered. All it took was a few ACL rules.

And we re-created admin views similar to the old Goodlok administration. So no one has to relearn where to click. We used the same screens and text and only updated the parts that needed to be modified to add new features.

Photo of whiteboard with Goodlok schema
Photo of team discussing stuff

Onward

Goodlok now has a Github repository with a Contember + CI setup that deploys it to the Contember cloud. And they're already starting to add new micro frontends like B2B shopping, internal shopping lists, and influencer apps. Of course, we're available when they need support or just a quick consultation.

In 2 days of work, we've created a foundation for Goodlok that will (we believe) last them at least the next 5 years.

Let's discuss how we can kickstart your project.

Schedule a free 30 minutes call to discuss your project and see if Contember is a good fit for it.

Schedule a free call