Operate > WebSphere Commerce Accelerator > Order management > Order flow process > B2B order flow process
Order flow process - B2B indirect supply model, supplier store
The order flow process in the B2B indirect supply business model is similar to that of the direct sales business model, in that an order is placed, payment is approved, and the order is released to fulfillment.
The primary differences in this business model are:
- The type of catalog that is used. The supplier hub and the hosted supplier stores use an aggregated catalog. An aggregated catalog is a shared catalog in which certain categories and products are loaded by the owner of the supplier hub, and other categories and products are uploaded by individual suppliers. A supplier hub exposes the aggregation of categories of products uploaded by all suppliers, and those loaded by the supplier hub owner.
- How the order is arrived at. In the supply model, orders are created by using a buy transaction or a request for price quotation.
- How orders are fulfilled. Orders are fulfilled by the individual supplier stores by using their own fulfillment centers. The supplier hub does not process or fulfill orders.
To illustrate, this is an example of the order flow process for a supplier store in the B2B indirect supply business model.
Some tasks that can be completed using the WebSphere Commerce Accelerator are indicated in the steps below.
- Place an order. A buyer registers and logs into the supplier hub and browses products in the aggregated catalog. Optionally, buyers with special arrangements (eMarketplace member buyers) can order directly from individual hosted supplier stores rather than by using the supplier hub.
- Select an offer. The buyer selects an offer from a particular supplier and adds it to the shopping cart. Orders (shopping carts) are created in the hosted supplier stores.
- Approve payment for the order. Payment authorization and capture are handled by the hosted supplier store.
- Release the order to fulfillment. Using the WebSphere Commerce Accelerator, the supplier can view and select orders for release. Unlike the reseller store/channel store model, the supplier hub does not fulfill orders or order items.
After the shopping cart is created in the supplier store, the order flow process is the same as for the direct sales model.
- Create a pick batch for all orders released to the specified fulfillment center. The WebSphere Commerce Accelerator can be used to generate the pick slips.
- View and print pick ticket. Using the WebSphere Commerce Accelerator, for each fulfillment center, batches are picked and pick tickets are printed.
- View and print packaging slip. Using the WebSphere Commerce Accelerator, for each fulfillment center, batches are picked and packing slips are printed.
- Pick and pack products specified in the pick ticket and packaging slip. Products specified in the pick ticket are then manually picked from the fulfillment center, and products are packed according to the instructions in the packing slips.
- Create package. The WebSphere Commerce Accelerator can be used to create package information.
- Ship goods. Ship the order to the buyer.
- Confirm shipment has been sent. Using the WebSphere Commerce Accelerator, for each fulfillment center, the shipment of the order can be confirmed. Shipment confirmation is possible only after the pick batch is created.