Ask - Test

You can always blacklist the modules, or remove the unwanted ones, e.g. from osgi/marketplace.

Liferay does not provide any downloadable bundles that do not contain Commerce functionality.  If you're a DXP subscriber I would recommend opening a Help Center ticket with any specific requirements or concerns.  If you're using Community Edition it might be possible to build a bundle from source that doesn't contain Commerce modules.  

To the best of my knowledge, the short answer is no but I will flag your concern to our Product Management team so that they can take it into consideration and correct my assumption if I am wrong.  

The long answer is that lumping all of the functionality provided in those modules under a single label called Commerce was probably too simplistic, but it helps us to market Liferay for customers looking for a traditional commerce solution.  

The reality is that those modules we have labeled Commerce include a variety of functionality that could be used to build solutions that don't sell products.  For example, Liferay Commerce originally introduced the concept of Accounts, intended to model external audiences.  In many cases, those external audiences are Customers, but in reality they could also be other business units within the same company or even employees.  Accounts are a critical concept that allow other features and functionality and have proved so useful for building a variety of solutions they've been adopted by DXP and are no longer strictly a Commerce feature.  

Additionally, our Order & Shipment Management feature would be useful to anyone building a solution that allows customers (or customer support reps) to look up order history or  shipment details regardless of where the sales are performed or which backend contains those details.  This has been very useful for customers with multiple legacy backend systems that are trying to unify these details and provide self-service access but who don't do any e-commerce at all.  

Similarly, our catalog capabilities could be used by any solution that helps end users discover and compare "products", even if those products aren't products that are for sale through the web site or even products in a traditional sense.  

I know it's not the exact same situation, but imagine that we had originally released our Document Library capabilities under a product called Document Collaboration.   Most of our customers that are using Liferay to build public facing marketing websites would probably assume that they don't need that product and would not want to include it in their solution.  However, without those capabilities they would be missing out on a very critical part of their solution.  

Hi Lee, is the root problem similar to what Ryan describes in LPS-105905?

Currently on Liferay.com we don't use a number of the modules/apps that show up in the control panel. This isn't a huge deal because its mainly the admin that see them, but it would be nice to be able hide or remove them.

Or is it some other issue that's a result of the Commerce modules being in the bundle and enabled by default? Just trying to better understand the issue you're facing.

Very good points raised by paying customers.

In our case we spent years learning Liferay on the premisse that it was and still is 'open source', that's actually a questionable statement as the code base is impossible to build a server from unless one dedicates a team of very skilled Java developers to work on that 100% of their time.

Then there was the OSGI migration, which seemed half hearted and not producing any real value for end users, the modularity may be burried inside the server but there is nothing modular about liferay from an end user perspective.

The final blow was this forced integration of a large feature set that not everyone needs, that's the Commerce set of features, they may or may not be useful for other use-cases but we didn't need them then (at around 7.3 GA3) and don't need them now.

So we decided to stop upgrading for a few releases and see how things progress.

Recently we're migrating from a private to a public cloud and thought now might be a good time fo an upgrade of fileray (amongst other servers), as we looked around we saw a few support threads, including this one, mentioning that the commerce module can be disabled using the `properties` file `enterprise.product.commerce.enabled`. We thought that's exactly what we need.

Our Docker instance has so far, not responded to this dirrective and the result is an install with the Commerce modules intact.

Are there any real solutions to this problem in Liferay 7.4.3.67 (latest as of this writing)?

Many thanks