+1 --
Best Regards, Ratnesh Upadhyay On Fri, 19 Jun 2026 at 16:13, Divesh Dutta <[email protected]> wrote: > Hi Arun, > > I agree with all your points. > > +1 for removing this plugin. > > Thanks > -- > Divesh Dutta > www.hotwaxsystems.com > > On Fri, Jun 19, 2026 at 2:36 PM Arun Patidar <[email protected]> > wrote: > > > Hi all, > > > > I would like to propose discussing the deprecation of the WebPOS plugin. > > > > https://github.com/apache/ofbiz-plugins/tree/trunk/webpos > > > > This proposal is not based on the relevance of POS systems. POS solutions > > remain an important part of retail operations. However, the current > WebPOS > > implementation appears to be based on an architectural approach that is > no > > longer aligned with modern POS development practices. > > > > Some observations: > > > > - > > > > Modern POS solutions are increasingly built as mobile applications, > > PWAs, or API-driven frontends. > > - > > > > OFBiz already provides backend capabilities such as catalog > management, > > pricing, inventory, order management, and accounting, which can be > > exposed > > through APIs. > > - > > > > Maintaining a dedicated POS frontend within OFBiz may not provide > > significant value compared to allowing specialized frontend > > applications to > > consume OFBiz services. > > - > > > > Modern POS requirements often include offline capabilities, mobile > > device support, hardware integrations, and rich user experiences that > > are > > difficult to achieve within the current WebPOS architecture. > > - > > > > There are many mature frontend technologies available today (React, > Vue, > > Flutter, React Native, Ionic, etc.) that can be used to build POS > > applications on top of OFBiz APIs. > > - > > > > The plugin appears to have limited community activity and maintenance > > compared to other areas of OFBiz. > > > > Instead of continuing to maintain WebPOS, the community could focus on > > strengthening API capabilities and integration patterns, enabling > > developers to build modern POS applications using the frontend technology > > of their choice. > > > > As a first step, we could consider: > > > > 1. > > > > Evaluating current WebPOS adoption. > > 2. > > > > Identifying active maintainers and users. > > 3. > > > > Deprecating the plugin if community interest is low. > > 4. > > > > Eventually archiving or removing the plugin if no active maintenance > > exists. > > > > I would be interested in hearing feedback from current users and > > maintainers before moving forward with any decision. > > > > > > Thanks > > -- > > Arun Patidar > > >
