Retail Pickup or Delivery Orders

Overview: Use the retail pickup or delivery options in the Order Broker Integration to receive and fulfill orders in CWSerenade that originated in an external retail location.

In this topic:

• Retail Pickup and Delivery Order Processing

• Building the Retail Pickup or Delivery Order

• Retail Pickup or Delivery Processing after Order Creation

• Reviewing Retail Pickup or Delivery Orders in Order Inquiry

• Things to Note about Retail Pickup and Delivery Orders

Retail Pickup and Delivery Order Processing

Poll for orders? If both the Order Type for Orders Brokered for Delivery (K91) and Order Type for Retail Pickup Orders Brokered to Serenade (K92) system control values specify order types, the BROKER process in Working with Integration Layer Processes (IJCT) periodically sends a fulfillment request message to Locate to poll for newly assigned orders. The polling interval is based on the Outbound delay time specified for the BROKER process.

Fulfillment request: Information in the fulfillment request message includes:

• requesting location: From the Locate Default Location (K51) if the Send Inventory by Warehouse to Locate (L06) system control value is unselected; otherwise, from the Locate location from each warehouse that has this field populated. The requesting location must match an existing location set up in Locate.

• message source and requesting system: From the Locate System (Serenade) (K50).

• destination: From the Locate Account (K49).

See the Fulfillment Request Message Sample (Retail Pickup or Delivery Orders) for an example.

The endpoint where CWSerenade sends the fulfillment request message is specified in Working with Customer Properties (PROP).

Create order? When the BROKER process receives an order in the fulfillment response message, it:

• Checks the setting of the Retain Backordered Lines Brokered to Serenade (K89) system control value. If this value is unselected and there is not a purchase order that might be able to fulfill the order expected within the Order Broker Due Date Threshold (K11), the process rejects the order. The process uses the Send Inventory by Warehouse to Locate (L06) system control value to determine whether to check a specific warehouse, or to check across all warehouses.

• Regardless of the setting of the Retain Backordered Lines Brokered to Serenade (K89) system control value, if the only item on the order is sold out, the process rejects the order.

Note:

• Drop ship items are eligible to be fulfilled on a retail pickup or delivery order regardless of whether any units are currently stocked in the warehouse, provided they are not flagged with a soldout control value.

• If a retail pickup or delivery order includes multiple order lines, and one of them is sold out, CWSerenade still accepts the order. To avoid this situation, have integrating systems submit each order line as a separate order.

Multiple order lines? MICROS recommends that an integrating system submit each ordered unit to the Order Broker as a separate order. Sending orders this way prevents any inconsistencies in order status that might occur if, for example, a multi-line order in CWSerenade included a soldout item, but the other order lines could still be shipped from the warehouse, or if a multi-unit line was split across different warehouses for fulfillment.

Building the Retail Pickup or Delivery Order

The processing to build a new retail pickup or delivery order from the contents of the fulfillment response message is similar to that used by the generic order API. In addition to the system (company) and location (warehouse) sent in the fulfillment request message, the information used to build the order includes:

Header information:

• order type: from the Order Type for Orders Brokered for Delivery (K91) or Order Type for Retail Pickup Orders Brokered to Serenade (K92) system control value. The transaction_type_id in the fulfillment response message indicates whether the order is a retail pickup or delivery order.

• order channel (Internet order): set to C. The transaction_channel specified in the fulfillment response message is not used.

• alternate order number: from the order number in the originating system, passed as the order_id from the fulfillment response (the external system’s order number).

• order date: the current date.

• entered date: the current date.

• source code:

• from the source_code passed in the fulfillment response message, if any; otherwise,

• from the Source code specified for the store location through Work with Store Cross Reference (WSCR), if any; otherwise,

• from the Order Broker Source Code (K93) system control value.

• customer number:

• if the customer_no passed in the fulfillment response is a valid customer number, or customer number plus individual number (separated by a hyphen), then use this customer. For example, a customer_no of 13827-9,000013827-009, or 13827-009 indicates sold-to customer 13827, individual 9. Zero-filling the customer number or individual number is optional, and the individual number is required only if the sold-to customer uses individuals. Otherwise,

• if the customer_no passed is invalid, or if no customer_no was passed, then CWSerenade uses standard name and address matching. See Customer Sold To Selection, Creation and Update for more background. Note: If the customer_no is invalid, the error is logged in CWSerenade’s APP.log file, even though the order can still be created successfully using the name and address information in the message.

Note: If the Sold to Email Update for Orders Brokered to Serenade (K96) or Sold to Address Update for Orders Brokered to Serenade (K97) system control values are selected, CWSerenade updates the existing customer record with any changed information; however, if you use the Relate Customer Integration, the customer update is not sent to Relate to update the linked Relate customer. As a result, the customer information in CWSerenade is overwritten if you retrieve the Relate customer record when searching for the customer.

• sold-to name and address: the information passed in the fulfillment response message is used to create or update the customer; however, if the customer number passed in the fulfillment response is valid and the Sold to Address Update for Orders Brokered to Serenade (K97) system control value is unselected, the process does not update the customer information.

Note: The information passed in the fourth address line is not used.

• email address updated? The Sold to Email Update for Orders Brokered to Serenade (K96) system control value indicates whether to update the customer’s email address with the email address passed for the order.

• sold-to phone numbers: the phone1 passed updates the customer’s daytime phone number and the phone2 passed updates the customer’s evening phone number if the Sold to Address Update for Orders Brokered to Serenade (K97) system control value is selected. Any non-numeric characters passed in the phone numbers are stripped out.

Ship-to Information:

• ship complete? from the ship_complete setting passed in the fulfillment response message, available when the version specified in Working with Customer Properties (PROP) is 5.0 or higher; otherwise, from the Ship Complete for Orders Brokered to Serenade (L01) system control value.

• ship via: from the Order Broker Ship Via (K94) system control value if there is not a valid, numeric ship_via passed in the fulfillment response message. If the Order Broker Ship Via (K94) is blank, the Default Ship Via (A77) applies.

• gift order? from the Gift Flag for Orders Brokered to Serenade (L03). This system control value overrides the setting passed in the fulfillment response message.

• freight charges: from the freight_amount specified in the fulfillment response message, if any; otherwise, CWSerenade calculates freight. If an additional freight charge is specified for the ship via, CWSerenade adds it to the order.

• tax: the total of the detail-level tax amount passed in the fulfillment response message for each item, plus any tax calculated based on freight and handling charges. The order-level tax amount passed in the message is not used to build the order.

• freight tax override: from the freight_tax setting passed in the fulfillment response message, available when the version specified in Working with Customer Properties (PROP) is 5.0 or higher; otherwise, no freight tax override.

• purchase order number: from the ref_transaction_no passed in the fulfillment response message. Displayed at the Display Order Properties Screen in standard order inquiry and at the Third Streamlined Order Inquiry Screen (Order Summary). If the Verify Duplicate PO Numbers for A/R Orders (D80) system control value is selected and the originating system submits multiple order lines from a single order to the Order Broker as individual orders, then CWSerenade puts each related order after the first submitted order into error status.

• warehouse: If the Send Inventory by Warehouse to Locate (L06) system control value is selected, this is based on the Locate location for the warehouse sending the fulfillment request message.

• delivery type (retail pickup or delivery): from the transaction_type_id specified in the fulfillment response message.

• ship-to name and address: from the ship_to information for the first item on the order; the ship-to information for any additional item(s) is not used. Creates an Order Ship To Address record, which you can review at the Display Alternate Address Screen. The one-time ship-to phone number is from the phone1, if any, for the first item. If no phone1 is passed for the first item, then the phone2 for the first item is used. For a retail pickup order, the ship-to name and address should specify the name and address of the originating store location. The process creates a one-time ship-to address.

Detail information: The process creates an order detail line for each item passed in the fulfillment response message. Also:

• price: the unit_price from the fulfillment response message. CWSerenade does not recalculate the price.

• price override reason code: from the Order Broker Price Override (K95) system control value.

• requesting system line number: from the requesting_system_line_no passed in the fulfillment response message. Identifies the line number in the originating system.

• quantity: the qty from the fulfillment response message.

• gift wrap: from the order_line_gift_wrap flag setting passed in the fulfillment response message, available when the version specified in Working with Customer Properties (PROP) is 5.0 or higher; otherwise, no gift wrap flag is applied. The gift wrap charge specified in the Item Offer, multiplied by the unit quantity, is included in the Handling bucket.

• order line messages: from the order_line_message passed in the fulfillment response message:

• Available when the version specified in Working with Customer Properties (PROP) is 5.0 or higher.

• If the message passed exceeds the field length of 60 positions, the message is continued on an additional message line.

• The Print flag for the message lines is set to B (both invoices and pick slips).

• customization: customization is created for an order line only if:

• the Item Offer associated with the source code on the order header specifies an additional charge code for a custom special handling format that includes a single line of customization instructions, and

• the customizations element in the message specifies a customization_code and customization_message, and

• the version specified in Working with Customer Properties (PROP) is 5.0 or higher

If:

• there is no custom special handling format specified for the Item Offer, the information from the customization_code and customization_message are saved as Order Line Messages, with a Print flag of P (Picks), and the order is not suspended with an error.

• the special handing format detail specifies any valid responses, and the customization message passed is not one of the responses, the order is suspended with an error of Input not valid response

• the special handling format detail specifies a Max # characters, and the customization message passed exceeds this length, the order is suspended with an error of Exceeds max character

Note:

• CWSerenade does not validate that the customization_code matches the Field label for the special handling format detail.

• Custom special handling formats that include more than one detail line are not currently supported for retail pickup and delivery orders received from Locate.

• Regardless of whether CWSerenade creates custom special handling for an order line, any order_line_customization_charge is still applied to the Handling bucket on the order.

• The Evaluate Special Handling Charges by Order Line (D67) system control value determines whether to multiply the customization charge passed in the message by the unit quantity.

• Tax amount: from the tax amount passed for the item in the fulfillment response message. CWSerenade does not recalculate tax for items.

Note: Only the tax amounts passed at the detail level are added to the order in CWSerenade; the transaction_tax from the fulfillment response message header level is not used.

Payment information:

• pay type: from the Order Broker Payment Type (K98).

• credit card number: From the description of this pay type.

• suppress deposit flag: set to Y.

• suppress refund flag: set to Y.

Note: The tender information, if any, passed in the fulfillment response message is not used.

Order messages:

• originating store location: written as an Order Message, for example: Originating Store: 317.

• request ID: written as an Order Message, for example: Locate Request ID: 123456. This information is also saved in the Order Broker record.

• special instructions: the special_instructions at the Order level from the fulfillments response message are written as an Order Message in capital letters, for example: ADD MONOGRAM HEB. If the special_instructions tag in the fulfillment response message contains the initial tag <Certificates>, CWSerenade creates a record in the Order Rewards Certificate table and writes an Order Message containing the certificate information; see Rewards Certificates on Retail Pickup and Delivery Orders.

• additional order messages: the order_message is written as one or more Order Message lines:

• Available when the version specified in Working with Customer Properties (PROP) is 5.0 or higher.

• If the message passed exceeds the field length of 60 positions, the message is continued on an additional message line.

• The Print flag for the message lines is set to B (both invoices and pick slips).

Note: Special instructions passed at the item level in the fulfillments response message are not retained.

See the Fulfillment Response Message Sample for an example.

If any of the information passed in the fulfillment response message exceeds the maximum field length in CWSerenade, the information is truncated.

Not mapped: The following information is not mapped from Locate when creating the order in CWSerenade:

• order additional freight charges

• order additional charges

• the setting of the Under Review flag

• order line extended freight

• the setting of the order line Ship Alone flag

• order line ship weight

• item UPC or EAN codes

Response messages: After receiving the fulfillment response message, depending on whether it was able to create the order successfully:

• order creation successful: The BROKER process sends a status update message with a status of Accepted.

• order in error: If the Re-Polling for Orders Brokered to Serenade (L04) system control value is:

• selected: the BROKER process sends a status update message with a status of polled

• unselected: the BROKER process does not send a status update message

Also, if the order is in error, it is assigned to the Order Broker Error Batch Number (K90).

• order cannot be created: If the BROKER process cannot create the order in CWSerenade, it sends a status update with a status of Rejected.

Order Broker record: The process creates an Order Broker record regardless of whether the order is in error. The initial status of the Order Broker record is New if there are any errors; otherwise, it is In process.

Changing the order in batch order entry: If the order is suspended or in error, you can use batch order entry to make changes to the order, although you cannot add an order line. Once the order is in held or open status, the restrictions described under Maintaining Retail Pickup or Delivery Orders from the Order Broker apply.

Retail Pickup or Delivery Processing after Order Creation

Checking for canceled retail pickup or delivery orders during pick slip generation: PIck slip generation sends an inquiry to Locate for all retail pickup and delivery orders eligible for pick slips based on their current status, item availability, and the pick slip selection criteria, to determine whether an eligible order has been canceled in the originating system.

When the response includes an order in canceled status, the program does not generate a pick slip for the order; instead, it puts the order on hold using the Order Broker Hold Reason (Cancel) (L02) system control value.

Otherwise, if the order has not been canceled, CWSerenade puts the Order Broker record into Picking status when the pick slip is printed and sends a status update message to the Order Broker indicating that the order or line is in Picked status.

Which status request message? Pick slip generation sends the status list request, inquiring on multiple eligible orders, if the Use Locate Status Inquiry List Web Service (M05) system control is selected and the current Message Version Number specified in Working with Customer Properties (PROP) is 5.0 or higher. If this system control value is unselected or if the message version number is not 5.0 or higher, pick slip generation sends the status inquiry request for each individual order instead.

Up to 2000 orders at a time: If there are more than 2000 retail pickup and delivery orders eligible for pick slip generation, the program sends the first 2000 orders at a time in the status list request message, and then generates an additional message for the next group of up to 2000 orders until it has requested status for all eligible retail pickup and delivery orders.

Streamlined allocation? If there are any retail pickup or delivery orders eligible for pick slip generation, the program can use streamlined allocation only when it uses the status list request. See Use Streamlined Allocation (L63) for background.

Sample messages: See:

• Status List Request Message Sample (Retail Pickup or Delivery)

• Status List Response Message Sample (Retail Pickup or Delivery)

• Status Request Message Sample

• Status Response Message Sample

Shipment confirmation: Once the shipment is confirmed, the Order Broker record status changes to Intransit for a retail pickup order, or Completed for a delivery order. The corresponding statuses for the orders in Locate are Intransit and Fulfilled.

Status updates after shipment of a retail pickup order: Once the Order Broker record for a retail pickup is in Intransit status, the order status in CWSerenade is X (completed); however the requesting store location still needs to receive the order, notify the customer, and have the customer pick up the order.

Deactivating the payment method: When you ship a retail pickup or delivery order, the billing async job deactivates the payment method. Once the payment method is deactivated, you cannot process a refund against the order unless you add a new payment method.

Sending the ship via and tracking number to Locate: When you confirm shipment, the BROKER process sends a message to the Order Broker. The information includes the description of the ship via used (even if it is different from the ship via on the order) and the tracking number, if available.

This information is available for review in Locate at the Order screen. The actual ship via used and tracking number used are displayed on the History tab.

Status inquiry: The BROKER process sends status inquiry requests for shipped retail pickup orders just once a day. The Order Broker record might be put in any of the following statuses:

• Received: indicates that the originating store has received the transfer

• Completed: indicates that the customer has picked up the order

• Partially fulfilled: indicates that the customer has picked up part of the order

See Setting the Daily Status Inquiry Time Window (all versions) for more information.

Other status updates after order creation:

The Order Broker integration supports a business process in which only the originating store cancels a retail pickup or delivery order, since the customer is not necessarily aware that the distribution center can be involved in order fulfillment. As a result:

• Sell out: If you sell out an order line, either in order maintenance or through the Process Auto Soldouts option, CWSerenade sends a status update to the Order Broker indicating the order or order line (based on whether you split orders) was Rejected. The Order Broker then attempts to reassign the order or line to another location for fulfillment. The Order Broker record’s status in CWSerenade changes to Rejected.

• Cancel: If you cancel an order or order line, CWSerenade changes the Order Broker record’s status to Canceled and sends a status inquiry request to the Order Broker. If the order’s status in Locate is:

• Canceled: CWSerenade does not send a status update to Locate; otherwise,

• If the order’s status in Locate is anything but Canceled, CWSerenade sends a status update to Locate indicating the order was Rejected. In this situation, if Locate is configured to “reshop” the order and there are any other possible fulfilling locations, the Order Broker reassigns the order to the next possible location based on the fulfillment rules set up in Locate, and the order returns to new order status; otherwise, if Locate cannot “reshop” the order, the order is assigned to the Locate Default Location Code/Unfulfillable (K56), and the order status is unfulfillable.

You cannot cancel a partial quantity of an order line on a retail pickup or delivery order.

Note: Although CWSerenade does not prevent you from cancelling a retail pickup or delivery order, some business processes require that only the originating location can cancel an order. In this situation, if the customer contacts the call center to cancel the order, the operator notifies the originating store location and requests that the store perform the cancellation and trigger the status update to Locate. Using this process, CWSerenade receives notification of the cancellation the next time it sends a periodic status inquiry on the order to Locate, and then holds the entire order (even if only one line was canceled) using the Order Broker Hold Reason (Cancel) (L02).

• Voiding a pick slip for a retail pickup or delivery order: If the Cancel Reason (Pick In) (L86) system control value specifies a valid cancel reason and you use the generic pick in API to void a pick slip for a retail pickup or delivery order, then CWSerenade cancels the order and sends a status update to Locate to reject the order. Otherwise, if the system control value is blank, you need to use order maintenance to cancel the order and send the status update to Locate.

• Rejecting the order: If you reject a batch that includes a retail pickup or delivery order, the BROKER process sends a status update rejecting the order; also, it deletes the related Order Broker and Order Broker History records.

Cancel reason sent? The status update message to reject a retail pickup or delivery order includes a cancel reason code and description if you:

• cancel the order in order maintenance: the entered cancel reason is sent

• void the pick slip: the Cancel Reason (Pick In) (L86) system control value is sent

• reject the batch that includes the retail pickup or delivery order: no cancel reason is sent

For more information: See the Status Update Sample (Retail Pickup, Delivery, or Ship-to-Store Orders) for a sample of the information sent to Locate when you cancel a retail pickup or delivery order.

 

Reviewing Retail Pickup or Delivery Orders in Order Inquiry

In addition to reviewing information through the Working with Order Broker (WOBR) menu option, you can also use standard order inquiry. Your options include:

• Finding the order number: Use the Order cross ref # at the Order Inquiry Scan Screen to find a retail pickup or delivery order based on the order number in the originating system. This number is also displayed as the Alt ord number at the Display Order Properties Screen

• Broker detail and history: Use the Display Order Broker Details Screen to review Order Broker Detail and Order Broker History, as well as other information such as the delivery type and the request ID.

• Identifying the Order Broker type: In addition to the Display Order Broker Details Screen, you can also review the Broker delivery type at the Display Order Properties Screen and the Display Order Broker Details Screen to determine whether the order originated as a Retail Pickup or Delivery order.

• Originating store, request ID, and special instructions: The originating store number and request ID are available for review at the Work with Order Messages Screen, for example:

Originating Store: 317

Locate Request ID: 70122

Also, if any special instructions were passed for the order, this information is also available for review at this screen.

• Order history: The Display Order History Screen displays activity related to sending status updates to and from the Order Broker, such as:

• Ln#: 1 Ready for Fulfillment: Written for each line received on a retail pickup or delivery order when the order is accepted and put into Open or Held status.

• Ln#: 1 Selected for Fulfillment: Written for each line printed on a pick slip.

• Ln#: 1 Fulfilled: Written for each delivery order line when you confirm shipment.

• Ln#: 1 In Transit: Written for each retail pickup order line when you confirm shipment.

Note: After you ship a retail pickup order, CWSerenade checks for status updates on a daily basis, and writes a single Order Transaction History message for each status change until the order is fulfilled. See Setting the Daily Status Inquiry Time Window (all versions) for setup information.

• Ln#: 1 Store Received: Written after the originating store location has received a retail pickup order.

• Ln#: 1 Customer Partial Pick Up: Written after the customer has picked up part of a retail pickup order.

• Ln#: 1 Customer Picked Up: Written after the customer has picked up all units of a retail pickup order.

• Ln#: 1 Cancel Acknowledged by Broker: Written when you cancel an order line in order maintenance or through Working with Backorders Pending Cancellation (WBPC).

• Ln#: 1 Rejected for Fulfillment: Written when CWSerenade rejects an order line because the item is soldout or backordered; if you reject the order when it is suspended; or when you sell out a line afterward in order maintenance or through Processing Auto Soldout Cancellations (MASO).

• Order held - line[s] canceled in Locate: Written if Locate responds to a status inquiry indicating that any of the lines on the order were canceled. In this situation, CWSerenade puts the order on hold using the Order Broker Hold Reason (Cancel) (L02).

Things to Note about Retail Pickup and Delivery Orders

Both system control values required: You need to complete both the Order Type for Orders Brokered for Delivery (K91) and the Order Type for Retail Pickup Orders Brokered to Serenade (K92) system control values in order for CWSerenade to request new orders from Locate, even if you do not process both order types.

Discounts: If the customer is eligible for a discount, such as one from a loyalty membership, CWSerenade still applies the discount to a retail pickup or delivery order.’

Additional freight: If the ship via on the order is subject to additional freight charges, these charges are added to the order.

Gift flag: The setting of the Gift Flag for Orders Brokered to Serenade (L03) system control value overrides the setting of the gift flag passed in the fulfillment response message.

Outbound invoice message: If you generate the CWInvoiceOut message, the message is generated for retail pickup or delivery orders unless excluded based on trigger rules (for example, not including these order types).

Tax: The tax amount for each order detail line is passed as a tax override amount.

Customer matching: If the fulfillment response message from the Order Broker does not specify a valid sold-to customer number, CWSerenade uses its standard customer name and address matching to either select an existing customer or create a new customer.

Relate customer integration: If you use the Relate Customer Integration, CWSerenade also creates new customer records in Relate as part of creating retail pickup and delivery orders. However, regardless of the settings of the Sold to Email Update for Orders Brokered to Serenade (K96) and Sold to Address Update for Orders Brokered to Serenade (K97) system control values, CWSerenade does not send customer updates you receive on retail pickup or delivery orders to the linked Relate customer records; as a result, the updated customer information in CWSerenade is overwritten the next time CWSerenade retrieves the customer record from Relate.

Order maintenance: The Maintain Brokered Fulfillment Orders (B20) secured feature controls the ability to maintain a retail pickup or delivery order. Even if you have authority under this secured feature, your ability to maintain the order is limited. For example, you cannot add or change an order line. See Maintaining Retail Pickup or Delivery Orders from the Order Broker for a discussion.

Processing returns: If the Suppress Returns for Retail Pickup/Delivery (L88) system control value is:

• selected: You cannot process a return against a retail pickup or delivery order, or create a return authorization

• unselected: You can process a return against a retail pickup or delivery order or create a return authorization; however, the Order Broker Payment Type (K98) is deactivated when you ship a retail pickup or delivery order. As a result, in order to process a return against the order, you need to add a new payment method.

Note: Regardless of the setting of the Suppress Returns for Retail Pickup/Delivery (L88) system control value, you cannot process an exchange against a retail pickup or delivery order, enter an item with a negative quantity, enter a negative additional charge, or apply a discount to a shipped order line.

CWSerenade does not send a status update to the Order Broker when you process a return against a retail pickup or delivery order.

Membership items: You should not set up your Order Broker integration to include membership items on retail pickup or delivery orders, since the customer membership would not be created correctly in CWSerenade. To prevent CWSerenade from sending membership items to Locate as part of Locate’s Product Import Process, do not flag them as Locate eligible.

Voiding or reprinting pick slips:

• If you use Reprinting and Voiding Pick Slips (WVRP or WSVP) to void or reprint a pick slip for a retail pickup or delivery order, this activity does not produce a status update to the Order Broker.

• If you use the Generic Pick In API (Shipments, Voids, and Backorders) to void a pick slip for a retail pickup or delivery order and the Cancel Reason (Pick In) (L86) system control value specifies a cancel reason code, CWSerenade cancels the order using the specified cancel reason and sends a status update rejecting the order to the Order Broker, including the cancel reason from the system control value.

Important: To prevent inconsistent updates to Locate for retail pickup and delivery orders:

• Prevent CWSerenade from generating multiple pick slips for a single retail pickup or delivery order:

• Select the Ship Complete for Orders Brokered to Serenade (L01) system control value.

• Do not create retail pickup or delivery orders for ship-alone items.

• Do not select the Retain Backordered Lines Brokered to Serenade (K89) system control value.

• Do not process void/unreserve transactions or partial backorders for these orders through the Generic Pick In API (Shipments, Voids, and Backorders); confirm or void the entire pick slip.

Note: Retail pickup and delivery orders that originate in Xstore include a single item.

Documents for store receiving: In order to support store receiving, you can generate the Pick Message from CWSerenade (CWPickOut) or the PO Download XML Message (CWPurchaseOrderOut). Each of these messages includes details on the order, including the Locate request ID, the order number in the originating system, and the delivery type. See the Generic Pick Out API and the Generic Outbound Purchase Order API for more information.