The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
Use the WebSphere Commerce Accelerator to maintain online stores.
A typical order includes one or more products, billing and shipping addresses, payment details, and the total cost (including shipping charges and taxes, as applicable). Comments or price adjustments can also be included in an order.
Creating a custom implementation of a WebSphere Commerce store requires a significant amount of planning. From gathering client needs, to deploying the live solution, much work is needed to successfully deploy a custom client store. Use the resources in here to help you plan every phase of store creation.
Review the following sections for information about installing the WebSphere Commerce product, associated maintenance, and WebSphere Commerce enhancements.
Before you migrate to WebSphere Commerce Version 8.0, review this information to help plan and execute your migration.
The topics in this section describe how to publish stores to either a test or production environment, and how to deploy customized code.
The IBM Management Center for WebSphere Commerce, or Management Center, is a suite of tools to support store management, merchandising, and marketing tasks for business users (Sellers, Marketing Managers, Product Managers, Catalog Managers, and others).
The WebSphere Commerce Accelerator interface consists of several notebooks, wizards, dialogs, and lists to help you complete your tasks.
Use WebSphere Commerce Accelerator to maintain online stores by completing various store operations such as creating and maintaining orders and tracking store activities.
If you have the appropriate authority, you can change the WebSphere Commerce logon password for a WebSphere Commerce user or for yourself from any of these tools.
The Seller sets up store-level functions within the site. The Seller can access all menu items under the Store menu.
If customers register with the store, you can maintain their registration profiles to track information. Maintain information such as the customer's logon ID, logon password, authentication information, store account status, title, name, preferred language, or currency.
Order processing refers to managing the order after it is captured and until it is fulfilled. A store can be implemented with or without Available-to-Promise (ATP) inventory capabilities.
An order passes various states (sometimes referred to as status) from the time it is created until it is closed or canceled. The state of order items within an order might not match the order states. For example, a single order might contain order items in state C and other order items in state R.
C
R
The order flow process varies depending on the business model and payment processing system.
Use the Order Management tools to create an order, create a billing address, or create a shipping address.
Use the WebSphere Commerce Accelerator to find customer orders.
Use WebSphere Commerce Accelerator to change order details such as the quantity of products, or the total price.
A customer can call a Customer Service Representative (CSR) and request to cancel an order. The CSR then performs the cancel order function. A customer who wants to cancel an order before it is submitted can invoke the OrderCancelCmd command.
Use WebSphere Commerce Accelerator to place an order on behalf of a business user.
A product might have associated personalized attributes if it is part of an RFQ request for a B2B model. For example, a customer can specify a particular color combination for uniforms for a basketball team.
Use WebSphere Commerce Accelerator to view the products that are released to a shopping cart created in the channel store site.
Pending payments occur typically when you use the SimpleOffline payment plug-in and the payment method's configuration in SimpleOfflinePlugin.xml has the keepPendingStatus attribute set to true. Background tasks are provided in WebSphere Commerce to periodically clean unfinished orders, including those associated with Payment rules. These cleanup tasks must be scheduled to handle orders remaining in a stale or incomplete state. For example, orders can become stale if merchandise is no longer available because the product is never restocked. Or, an order can be blocked indefinitely if a failed payment operation prevents the order from completing normally. The scheduled tasks clean these orders by putting them in a canceled or finalized state.
Pending credits occur typically when you use the SimpleOffline payment plug-in and the payment method's configuration in SimpleOfflinePlugin.xml has the keepPendingStatus attribute set to true.
To edit extended data for a payment processed by using a payment plug-in, follow these steps. Your user ID must be assigned to one of the following roles: CSR, Seller, Customer Service Supervisor, Sales Manager, Operation Manager or Logistics Manager.
You can add or send additional protocol data required by a plug-in to perform a payment or credit transaction with a payment back-end system.
Refunds typically require an associated inventory return. However, you can perform a refund without such a return when necessary.
Inventory includes anything that can be physically accounted for in a fulfillment center such as items, products, SKUs, bundles, and prebuilt kits.
Customers return products to a fulfillment center for many different reasons. Returned inventory might be reintegrated into the pool of inventory available for order, or it might be discarded. This process is called disposition.
A return is a record of a customer's request for a refund, to return merchandise, or both. The term is used whether an RMA is issued in advance of merchandise receipt or the transaction is begun at the time of merchandise receipt. You can use the return merchandise authorization (RMA) function in both available to promise (ATP) and non-ATP inventory-enabled stores.
A buyer can create a Request for Quote (RFQ), by using the WebSphere Commerce Accelerator, for unique variations of goods and services that are offered in a catalog. If buyers cannot find a product or category that match their needs within a catalog, they can select attributes from the personalized dictionary to precisely define the product specifications. A buyer can also create an RFQ by using the contents in their shopping cart, or add a shopping cart to an existing RFQ.
To customize what a customer can do in a store use the business relationship management system. By using this system, you can entitle customers to various aspects of a store such as what products they can purchase, the price they pay, and what payment methods a store accepts.
Topics in the Integrating category highlight the tasks that are commonly performed for using WebSphere Commerce in combination with other products.
WebSphere Commerce provides many tutorials to help you customize and understand your WebSphere Commerce instance and stores.
The topics in the Developing section describe tasks performed by an application developer.
The following section describes how you can leverage WebSphere Commerce features and functionality to help your site be compliant with different privacy and security standards.
These topics describe the security features of WebSphere Commerce and how to configure these features.