Skip to end of metadata
Go to start of metadata


In Compiere, the eCommerce capability provides a highly featured web presence for an organization. The information is shared with the standard application eliminating the need for synchronization or additional integration between the web store and the back end application. The web store components are based on cascading style sheets and can be readily customized to provide the required look and feel.


Users are able to view and search the product catalog. Product images and specifications are stored for each product and can be displayed on the web store at the user's discretion. The products available on the web may be restricted according to the Business Partners' access rights and once a user has logged into the web store products are ranged and priced according to pricing specific to the customer.

Hierarchies can be defined to limit product selection and productsmay be searched using Product Categories and/or Product Attributes.

To add a product to the Web Store, simply select the 'Featured in Web Store' check box. If selected, the product is displayed in the initial or any empty search.

To allow a product to be available under Self Service, select the 'Self Service' check box.

Note: the Self Service check box is also seen on other records like Sales Orders. In this context the flag indicates that this record was entered or created via Self-Service.


If a user is logged into the Web Store as a Business Partner Contact with a specific price list, the appropriate prices are shown; otherwise, the default price list is shown.


Compiere enables users to add items to the Shopping Basket via the Product Catalog or web form request. Item quantities can be changed and items can be removed from the shopping basket. It is mandatory to sign on with secure access to retrieve stored customer information. The payment information is then entered or confirmed. Currently, the PayFlowPro payment processor from PayPal is supported with others due to be supported in the future. Before submitting the payment for authorization, the credit card number can be verified for data entry errors. This ensures that transaction fees are minimized for rejected transactions resulting purely from erroneous data entry.

After receiving the payment confirmation, the order is created and the receipt is displayed together with the authorization code received from the payment gateway.

An email is sent to the person responsible for Web Orders to notify them of the order and affect further processing.


User Management

User information can be stored as cookies enabled to allow automatic detection and sign in functionality. Users are required to authorize their email address to reduce the possibility of fraudulent transactions.

Once a Business Partner logs into the web store, the Price list is based on the Business Partner Price List.

Customers have access to the Web basket and the Check out functions.

Customers can view and print Orders, Invoices, Shipments, Payments, and Assets.

Customers can also make payments on open orders or invoice. Customers can also cancel not shipped or paid orders.

A Sales Rep can view Customers, Customer Orders, Customer Invoices, Customer Shipments, Customer Requests, and Commission.

Note: You can restrict what any User associated with a Business Partner can see by setting the appropriate Business Partner Access in the Business Partner window. 


The system monitors all web requests, then collects web statistics to analyze web activity, and quickly identifies visitors to the site as well as click counts.

Info Requests

A web user 'Request' can be forwarded to one or more email addresses for action. A confirmation can also be sent to the requester. The Request becomes part of the Customer Relations Management information base.

A Sales Rep can view and Maintain assigned requests.


Setup the web store in Tenant. The default has /wstore as the context.

Note: You may need to rename the context of the GardenWorld web store.

The Run_setup deploys the web store with the default /wstore content.

Technical Aspects

The Run_setup creates and deploys the compiereWebStore.ear, which distributes the User Interface components.

You can customize the lib/compiereWebStore.war. The initial settings are in the WEB-INF/web.xml. If unmodified, the first Web Context is used. You can optionally set the #W_Store_ID explicitly.

You can update the style using the Styles Sheet standar.css. The UI aspects are available in *.jsp.

You can also customize the lib/compiereWebStore.xml. You can set the context to default /wstore.

Additional Web Stores

To have multiple web stores, Edit the lib/compiereWebStore.xml and the lib/compiereWebStore.war. Then use the Run_setup, which creates a new compiereWebStore.ear. Rename the compiereWebStore.ear and copy it to the deployment directory.

Setup Information

For the Tenant, setup the SMTP Host and Request Mail account. Request a confirmation Email and a web directory or Download base.

For the Web Store, load the web page images and components, as well as the email header and footer. Include the Warehouse, Sales Rep, and Price list.

A user should have an Email User Id and a password to access the web store. In order for the payment processor to work the bank information needs to be in place.

Mail Templates

Mail Templates are used for sending mail to interest groups and Business Partner Groups.

Mail Templates are also used for sending dunning, Asset Delivery, and Invoices.

  • None