The Proposals Wiki has been deprecated in favor of creating Feature Requests in JIRA. If you wish to propose a new idea for a feature, visit the Community Ideas Dashboard and read the Feature Requests Wiki page for more information about submitting your proposal.
« Zurück zu FrontPage

Liferay as an e-commerce platform

Introduction #

Improvements for the shopping portlet and other general improvements that would be needed to make it easier for users to create online shops with Liferay

Discussion have been held in the following forum threads: 

Proposals #

  • Integrate shop products in the asset system - this will provide the shop with tagging, categorization, comments, links, social equity, ratings, custom fields...
  • Integrate the shopping process with the workflow system
  • Separate the shopping in several portlets (back-office and front-office)
  • Improve shipping cost calculus with geogrphic and weight information about the products and customers
  • Billing: develop a very simple ERP and an ERP integration framework
  • Manage stock refunds in the stock section
  • Import/export products from other systems
  • Reports and statistics tools integration for data analysis (Jasper-iReport/Pentaho...)
  • Payment system integration made easier for developers to add new payment modules
  • Multiple shops per instance (one shop per community/organization)
  • Support for multi-language sites (everything should be localized)
  • Enhace social experience (features such as "those who have bought this product also bought this" or dependencies to make up and do cross-selling)
  • My orders & history (by default in control panel) something like my account in classical e-shop
  • Search scoped to shopping items
  • HTML editor for categories and for product description
  • Creation of PDF invoices
  • Possibility to assign image also for category, more images for one product (i.e. sets of small-medium-full images) with lightbox-style gallery
  • Possibility to specify template for list/detail of product and replace functionality (e.g. replace PDF Invoice generation with custom implementation)
  • Support for multiple shipping carriers (with different payment for different countries)
0 Anhänge
39026 Angesehen
Durchschnitt (4 Stimmen)
Die durchschnittliche Bewertung ist 5.0 von max. 5 Sternen.
Antworten im Thread Autor Datum
Great list. In South Africa we need to show ... chris Rowse 29. August 2011 01:34
Privacy Issue - Following the hacking and... chris Rowse 29. August 2011 03:09

Great list.
In South Africa we need to show
- VAT and Company registration of both buyer and seller
- Unique, sequential VAT invoice numbers (Receiver of Revenue requires this)
- The Words 'VAT INVOICE' or 'Copy VAT INVOICE', VAT INVOICE can only occur once

Buyer address info should be pre-filled from control panel addresses
Registration, VAT, Tax etc should come from the Organization that owns the shop
Gepostet am 29.08.11 01:34.
Privacy Issue - Following the hacking and privacy issues recently experienced by some large corporations, I, personally, don't like to store Credit card and other details on my Liferay database.

Wherever possible, I do not even want credit card information captured in my forms.

I prefer the payment stream to capture and maintain this information for me. I access and use information from their secure database as and when I require it. I don't need credit cards details, just a handle to the transaction n which I play the supplier role.

Paypal go some way in this and can give me shipping information for a completed transaction. From what I can see, they do not yet (Aug 2011) enable me to send some detail (e.g. name and address) through to their API without also sending credit card details.
Gepostet am 29.08.11 03:09 als Antwort auf chris Rowse.