Blog • Developer | eCommerce

7 pain points that Flows easily solves

Last updated: 21 Jun 2019

Every retailer wants to differentiate themselves from their competition. It is a natural way to become noticed in the constantly evolving commerce world. But there’s only ever so many commerce platforms to choose from and not all of them allow for the most treasured feature, customization.

That’s where Flows come into play. Moltin makes each part of its system extendable and usable individually or as a whole to meet the needs of many different use cases. But that’s not only it! You can customize your project by adding new resources and create brand new features uniquely adapted to your business logic.

Here at Moltin, we realise that every business is different, but there are some common pain points that many retailers struggle with when trying to conquer the digital space. Below, we have compiled the most common scenarios that could be easily solved with the use of Flows.

 

  • Your business outgrew its original plan

You had an excellent idea for business and a brilliant plan how you want your commerce site to look. But with time, you understood that customers want something more than you can offer. They want to want to see information outside of the norm about the product, and they want to add specific details, like delivery instructions, second email address, etc.

 

  • Your platform doesn’t allow you to do exactly what you want

You’ve invested in a platform that was a great solution back in the day, but now you’d like to expand beyond its capabilities and use a third-party integration to do so. All goes well until you realize you can’t store data coming back from your third party services. For example, you’re able to send a Twilio SMS with an order confirmation via a serverless function, but then you can’t automatically update the order in your system to say that the SMS has been sent.


  • You have a complicated data model and you don’t want to compromise its structure

Your business requires a very unique and specific data model and you find it hard to find a platform that can accommodate the entire solution without a compromise.


  • Your platform doesn’t play nice with other rigid systems

You find it hard to integrate with other third party integrations that follow strict data structure due to various regulatory compliance, such as 3PL logistics, hazardous material warehouses, etc. And you know that you either comply with the rules or you fail, there is no try.


  • You can’t use your platform’s API to create new features

You want to create a consistent commerce experience for your customers so you wish to use your API provider to add a bunch of new features to your project, a wish list, a blog, customer reviews, product rating, delivery requirements, etc., but your provider’s API doesn’t allow for that level of customization.


  • You don’t want to use an external service to append your data

You have a specific data model in mind that appends additional data to suit your business requirements, but you are not interested in a third party service or external database to host it. Instead, you want to create a system within your own API to use effectively within your project.


  • You don’t want to spend additional dime on a CMS system

You want to use your provider’s API to set up a lightweight content management system that will distribute the data easily without too much hassle. The model is not overly complicated, so you are not willing to pay extra for full-blown content management platform.

 

To sum up

These all scenarios are easily solved with Flows. And by easy I mean few lines of code following easy-to-understand logic with a short development cycle.

But there are hundreds of other use cases that our customers think of every day and amaze us with how innovative their projects turn out to be. Don’t be afraid to experiment and think big, because high chances are you can use Flows to turn your idea into reality.

If you want to read more about Flows, we have an excellent reference for Flows in our API reference. We have also created some guides you can follow on how to use Flows in a specific use case, like customizing your product, creating a blog or a wish list.

If you wish to discuss a specific scenario and are not sure if it can be solved with Flows, reach out to our Moltin team, we would happily help you out!

From Our Blog

24 Jun 2019

Cross-functional impact of open commerce architecture

Implementing open commerce architecture Implementing an open commerce architecture has a profound impact on every function within a business. Unless these impacts are considered on a cross-functional...

Read More
author
Matt Foyle
in Industry News | eCommerce
21 Jun 2019

Magento’s TCO (Total cost of ownership) Analysis: How “Free” is Free?

“Magento Community Edition is a free, open Source eCommerce platform which provides businesses with a flexible, digital commerce solution to successfully sell online.” You might be thinking you’d...

Read More
author
Shaneil Lafayette
in Magento Migration
20 Jun 2019

Analytics for your Moltin store

Today we’re going to take a look at how to use best-in-class data warehousing and analytics solutions on top of Moltin, specifically in relation to orders and order items.

Read More
author
Matt Foyle
9 min. read in Developer