We are impressed and grateful for the work done by Frappe and the rest of the community dedicated to building ERP Next into a truly remarkable and enabling platform for organizations worldwide.
We are building a new, custom ERPN/Frappe application to deliver a one-page shopping cart/checkout experience to Web users with ERPN-backed ecommerce sites. In addition we have been building an associated Payment Gateway Setup application to make deploying payment gateways a bit easier.
At DigiThinkIT (Headquarterd in Orlando, Florida, USA) we believe “a rising tide raises all ships” and we want to make solid and valuable contributions to the Community with the intention that some or all of this work may be used to enhance this great platform for all who use it.
After a lot of research, we believe we have identified the following limitations to the default Shopping Cart application which we intend on addressing with a new application:
- it does not allow more than one payment gateway per system instance
- it does not support complex product configurations where a user has to configure its almost unique product item’s look and feel based on the set of pre-defined manufacturing options/features (this would typically map the unique configured product to a Quote and Sales order with multiple line items on ERP Next backend side etc.)
- it has less than efficient multi-page and multi-step UI/UX for check-out flow (ideally, the one-page checkout experience is captivating to the end users)
- it does not allow estimated shipping costs to the quote at the shopping/cart based on real time apis from various shippers
- it does not facilitate the scenario where a user places a preliminary (or “Saved Cart”) order to the system, without immediate online payment performed (in which case the system will ideally map such a preliminary order to a Quote Document in ERP Next rather than creates a new Sales Order)
- when a guest user without an ERPN account shops on the site and is prompted to create an account in the system (to make the first purchase), the system does not return a user to the cart after login (this is a little confusing to less than savvy users)
- it doesn’t allow for multiple payment options (PayPal, CC, Amazon Pmts, Apple Pay, eCheck)
Our intention is to build a few new apps that address most of the limitations above.
The purpose of this post is to share our general architecture/implementation plan, report our progress, discoveries and challenges as we also get feedback from the community on:
- Feasibility of the proposed approach/possible limitations and drawbacks
- Additional features that may be useful
- Any other relevant feedback on the solution proposed
Lastly, we are hiring and always looking for talented developers who are passionate about using their talent to empower others with great tools. If you are interested in finding a home with a dynamic, driven team that likes to solve complex challenges in software, feel free to contact us.
The proposed solution architecture is highlighted in the diagram below:
In an ideal world, we envision extending ERPN following the current modular architecture with an extensible system for plugging new payment gateways to the proposed infrastructure. We are going to try it by developing the new payment gateway for Aurothize.net for Credit Cards and eCheck and direct ACH, PayPal, and others and stacking it there, together with the existing core app for Paypal-ERPN integration.
We appreciate any feedback/critique/suggestions on our proposed solution. We will work to provide periodic updates regularly in this thread for this project and will provide GitHub access soon.
on behalf of ERP Next team at DTI (www.digithinkit.com)