Process: Fulfill orders

 

Flow

Legend

 

Objective

Support the process of fulfilling orders by creating pick batches, pick lists, pack slips, and invoices.

 

Description

The support in this process is primarily targeted for integration with back-end systems through messaging to do the following:

• Create pick batches from releases that have been released to fulfillment but not yet fulfilled. See the Create pick batch process for more detail about this process. The implementation is a pull interface where the fulfillment center or its agent will request that a pick batch be generated and follow that request with a request to get the details, which contain the pick list and the pack slips.
• Allow for manifesting and shipment confirmation after a release has been packed and shipped.

The process supports generation of a pick list, pack slips, and an invoice in the form of XML documents. WebSphere Commerce Accelerator supports this process also, but it is not intended for high-volume usage.

 

Features

Integration with back-end systems for:

• Pick-batch generation
• Shipment confirmation

Pick-batch creation:

• Invoice XML generation
• Pick-list XML generation
• Pack-slip XML generation

Shipment confirmation:

• Capturing tracking information

 

Customization

May customize to integrate with fulfillment using a push protocol

 

Edition

Professional, Enterprise

 

Subprocesses

• Create pick batch
• Fulfill order externally

 

Tasks

Task	Description	Role
Capture Payment	This task supports the asynchronous nature of payments by performing the capture of payment for an order in a background process. The input to the process is all orders that have been shipped and have not had payment captured. On completion of the task, payment artifacts will be appropriately updated to reflect the capture and the order will be updated to reflect that payment has been captured. Communication with back-end payment systems may occur in this process depending on the payment type and the payment integration used. The definition of what happens during payment capture varies by payment type and by the implementation of that payment. Some examples are as follows: A credit card using batch processing for deposits: in this case, no financial transaction takes place at the time of capture; but rather, the captured amount is placed in a batch that will be settled at a later time. The purpose of using batches is to reduce transaction fees. A credit card not using batch processing: in this case, a settlement would occur as the result of the capture. A check: the implementation supporting BankServ ACH protocol supplied with WebSphere Commerce Payments deposits the check at authorization time. Therefore, capture payment in this case is actually a no-op. Other implementations may deposit the check at this point. Line of credit: the accounts receivable record would be added and the amount remaining on the line of credit would be updated accordingly. Offline payment method: the capture would be recorded and potentially placed in batch for later settlement if batches are supported.	System
Confirm shipment	This task performs shipment confirmation and sends the information to WebSphere Commerce. The following information is sent to cause a manifest to be created: DateShipped ShippingCosts OrderId OrdReleaseNumber PackageId Weight PickupRecordId Currency ShipModeId TrackingId WeightMeasure SerialNumber The manifest can optionally be indicated as released in the same step.	Shipping clerk
Obtain shipment tracking info (external)	Obtain the shipment tracking information. This may be done by scanning a shipment label or manually recording it.	Shipping clerk
Release manifest	Release the manifest. This can be invoked either with the ReleaseManifest Controller command or as part of the ReleaseShipConfirm Controller Command. In other words, it can be performed as a single step as part of shipment confirmation or as a separate step. Tools Controller Command ReleaseManifestCmd Task Command UpdateManifestStatusCmd	System
Release ship notify	Sends an e-mail notification message to the buyer for order release shipment.	System

 

Business artifacts

• Completed order
• Fulfilled orders
• Invoice(s)
• Manifest
• Manifested released
• Order releases
• Pack slip XML
• Partially shipped orders
• Pick list XML
• Release
• Released order
• Shipment confirmation notification
• Shipment confirmation message
• Shipped orders
• Target fulfillment center

Feedback

(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.