Hello all,

This has been done. Below are details:

*Issue*: https://issues.apache.org/jira/browse/OFBIZ-13445
*PR*: https://github.com/apache/ofbiz-plugins/pull/304
*OFBiz Attic *-
https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Attic

Thanks Jacques, Chandan, Mridul, Ratnesh, Divesh for your support.

Thanks
--
Arun Patidar



On Fri, Jun 19, 2026 at 6:02 PM Arun Patidar <[email protected]> wrote:

> Ok, I'm sharing the same details with user ML and will wait a week.
>
> Created Jira ticket for the same:
> https://issues.apache.org/jira/browse/OFBIZ-13445
>
>
>
> Thanks
> --
> Arun Patidar
>
>
>
> On Fri, Jun 19, 2026 at 5:13 PM Jacques Le Roux via dev <
> [email protected]> wrote:
>
>> Hi Chandan,
>>
>> I agree that a precautionary principle can't hurt.
>>
>> Then we should share this thread with user ML and wait a bit. Without
>> answers (in few weeks?), I guess we can assume nobody is longer interested.
>>
>> Thanks
>>
>> Jacques
>>
>> Le 19/06/2026 à 12:10, Chandan Khandelwal a écrit :
>> > Hi Arun,
>> >
>> > I agree with this proposal. It would be good to review the current usage
>> > and maintenance status of WebPOS and get feedback from active users
>> before
>> > making a decision.
>> >
>> > Kind Regards,
>> > Chandan Khandelwal
>> >
>> > On Fri, Jun 19, 2026 at 3:23 PM Jacques Le Roux via dev <
>> > [email protected]> wrote:
>> >
>> >> Hi Arun,
>> >>
>> >> As the maintainer of the years deprecated, and now removed original POS
>> >> (not WebPOS) I tend to agree.
>> >>
>> >> +1
>> >>
>> >> Jacques
>> >>
>> >> Le 19/06/2026 à 11:05, Arun Patidar a écrit :
>> >>> 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
>>
>

Reply via email to