Process: Process order end to end
Flow
Legend

Objective
Process an order from the time of the taking of the order until the order is
shipped and received by the customer.
Description
Shoppers create shopping carts containing items to be purchased. The shopper
submits the order, after which the system takes the order through its life
cycle until it is shipped to its destination.
There are several sub-processes that make up this process:
- Capture the order
- This process describes a generic model for capturing an order. Each store
model could potentially have its own variation of this process. The process
begins when a shopper decides to add something to a shopping cart. The process
ends with a submitted order. In between, the shopper can add additional items
to the shopping cart. A shipping address and method for each item can be
specified. Availability of the requested items and quantity can be checked, and
an estimated availability date can be obtained when the requested quantity of
items is not in stock. The order is prepared, and prices are calculated for the
order line items. Taxes, shipping charges, and shipping taxes are also
calculated. Adjustments can be made to the order total. Coupons can be applied
as a discount. The payment method is selected and all the relevant information
provided. Lastly, the shopper checks out. This results in the order being
submitted for processing.
Note: Pricing is not described here. Pricing is described in a separated
business-process model and documentation.
- Process the order
- This process takes a submitted order and gets it ready to be released to
fulfillment. It handles order quotation expiration, performs inventory
allocation, recalculates shipping and shipping taxes if necessary, and handles
order approval by customer. Checks are made in WebSphere Commerce Business
Edition to check that the order was not previously submitted, that all the
trading agreements are active, and that the billing address is updated from the
terms and conditions if a billing address exists for it.
- Release to fulfillment
- This process groups those order line items in an order that are being
shipped to the same address, on the same day, by the same carrier, and from the
same fulfillment center. Items that have a product attribute of "release
separately" will be put into a release by themselves.
Before creating releases for an order, the order payment status is checked
to verify that the payment authorization has been obtained and is still
valid.
- Fulfill orders
- The process supports the generation of pick batches for releases that have
been released to fulfillment but not yet included in a pick batch. Creation of
a pick batch includes the creation of a pick slip, a pack slip for releases,
and an invoice.
- Process shipped orders
- The process supports capturing payment for orders that have shipped.
- Process pending payment auths
- The process supports checking for payment authorizations that are pending
and updating order status appropriately when the payment authorization
operation successfully completes. This process will also handle payment
authorizations that have expired by requesting a new authorization. This
process is important in that it updates orders to have the correct payment
status and works in conjunction with the Release to fulfillment process to
control the releasing of orders to fulfillment only when they have a valid
payment authorization.
Features
- Order entry
- Order process
- Payment
- Release to fulfillment
- Fulfillment
- Manifesting
- Available to promise
Customization
- Overall flow may be customized -- for example, skip orderPrepare
- Order arriving from a Buyer system
- Integration with back-end systems
Edition
Professional, Business Edition
Subprocesses
Feedback
(C) Copyright IBM Corporation 1996, 2004. All Rights
Reserved.