Brokered Backorders

Purpose: You can use the Order Broker Integration to send order lines to the Order Broker for fulfillment if the items are backordered in the warehouse. The Order Broker finds store locations that have sufficient inventory to ship the items directly to the customer.

In this topic:

• Brokered Backorder Processing Overview

• Brokered Backorder Fulfillment: Initial Order Creation

• Brokered Backorder Fulfillment Process: After Order Creation and Status Updates

• Rules for Submitting Backorders to the Order Broker

• BROKER Periodic Function

• Brokering Items with Soldout Control Codes

• Things to Note About Brokered Backorders

Brokered Backorder Processing Overview

Order Broker assignment: Assigning a backordered item to the Order Broker can occur through:

• order entry or order API: When you create an order that includes a backordered line, CWSerenade assigns the line, if eligible, to the Order Broker for fulfillment, and withholds it from normal fulfillment processing within CWSerenade.

• batch process: A periodic function finds eligible backordered lines and assign them to the Order Broker.

Eligibility rules: CWSerenade determines whether an order line is eligible for Order Broker fulfillment based on certain basic criteria, such as whether it is fully backordered and authorized; also, you can use related system control values to further restrict Order Broker assignment based on your business rules, such as omitting gift orders or items you are due to receive soon on open purchase orders. Also, the item must be flagged as Locate eligible. See Rules for Submitting Backorders to the Order Broker for details.

Does each line create a separate order in Locate? Each eligible backordered line on an order is sent to the Order Broker:

• as a separate order if the Use Split Order (L56) system control value is unselected. In this case, the fulfillment of each line is tracked individually. The Order Broker does not attempt to assign multiple order lines from the same fulfilling location.

• as part of a single order if the Use Split Order (L56) system control value is selected. In this case, the Order Broker attempts to assign all lines on the same order to the same fulfilling location; however, it notifies CWSerenade about multiple assigned fulfilling locations if the order or lines are split. If a single backordered item is unfulfillable through the Order Broker, that line returns to standard backorder processing, but additional lines on the order can still be fulfilled through the Order Broker.

What information is sent to the Order Broker? CWSerenade sends the sold-to and ship-to customers’ names and addresses, as well as details on the requested item. It does not send payment information, although only fully paid and authorized items are eligible for Order Broker fulfillment. For more information on the information sent to the Order Broker, see Sample Order Broker Messages.

Brokered Backorder Fulfillment: Initial Order Creation

1.	The process begins when you create an order in CWSerenade that includes a backordered line. The order creation can occur through interactive order entry, batch order entry, or the order API. You can also use the BROKER periodic function to submit existing backordered lines to the Order Broker for fulfillment; see Additional Locate Setup in CWSerenade for more information.
2.	If the order line meets the Rules for Submitting Backorders to the Order Broker, CWSerenade generates a request message to the Order Broker and creates an Order Broker record. Note: Order lines that meet the Rules for Submitting Backorders to the Order Broker do not sell out initially, even if the items are flagged with soldout control codes. See Brokering Items with Soldout Control Codes for more information. If the order includes multiple backordered lines and the Use Split Order (L56) system control value is selected, the request message includes all eligible backordered lines; otherwise, each backordered item is submitted as a separate order. Each Order Broker record has a status of R (ready) at creation. Also, the order line is updated to restrict it from standard backorder processing in CWSerenade: • the Drop ship flag is set to D • the Printed quantity is updated to the ordered quantity • An order line that is assigned to the Order Broker for fulfillment displays a status of OBR in standard order inquiry. • the quantity to be brokered does not update the Backordered quantity for the Item Warehouse. Note: Order Broker status is not displayed in Streamlined Order Inquiry (DORI).
3.	If the BROKER process in Working with Integration Layer Processes (IJCT) is active, it immediately generates the submit order request message to Locate to request order creation and assignment in the Order Broker. At this time, it also: • changes each Order Broker record’s status to W (waiting) • creates an Order Broker History record for each line to track the order submission (A - Send Order Request) • writes an Order Transaction History message indicating that each order line was submitted to the Order Broker (for example, Ln#: 2 Submitted To Broker) See the Brokered Backorder Submit Order Request Message Sample.
4.	The Order Broker module in Locate receives the submit order message. If CWSerenade sent each line separately, Locate creates each order line as a separate order in its database; otherwise, if you use the split order option, Locate creates a single order including all of the order lines that were eligible for submission as brokered backorders. The Order Broker assigns each order or line to a location for fulfillment based on inventory availability and the business rules you have defined in Locate. At this point, the order status in the Locate database is new_order.
5.	When the message version is 3.0 or 3.1: If the order is: • assigned to a single fulfilling location, Locate sends a response message to CWSerenade indicating the assigned fulfilling location and the unique request ID it uses to identify each order. See the Submit Order Response Message Sample: Single Location (Message Version 3.1 or 3.0). • split across multiple fulfilling locations, Locate sends a response message indicating that the order was assigned to multiple locations, and providing the unique request ID it uses to identify each order. See the Submit Order Response Message Sample: Multiple Locations (Message Version 3.1 or 3.0). If the order is split, CWSerenade immediately sends a status inquiry message so that it can determine the assigned fulfilling locations for each item on the order. See the Status Response Message Sample. When the message version is 5.0 or higher: Locate sends a response message to CWSerenade indicating each assigned fulfilling location and the unique request ID it uses to identify each order. See the Submit Order Response Message Sample: Message Version 5.0 or higher. The message version is specified in the Locate Properties.
6.	If the Order Broker successfully created an order and assigned it to one or more fulfilling locations, CWSerenade: • updates each Order Broker record with: • the fulfilling location, using the description set up through the Work with Store Cross Reference (WSCR) option • the request ID • a status of A (acknowledged) • writes an Order Transaction History message indicating that the order line was acknowledged by the Order Broker (for example, Ln#: 2 Acknowledged by Broker) • creates an Order Broker History record (B - Receive Order Response)

Split line? If the Allow Split Line? preference in Locate is selected, the Order Broker might split the quantity of a single brokered backorder line across more than one fulfilling location. For example, you create an order for item AB100 with a quantity of 10. There is no single location that has a quantity of 10 available. The Order Broker assigns 8 units to location 100, and 2 units to location 200.

The Order Broker splits order lines or line quantities only if you have selected the Allow Split Order? and Allow Split Line? preferences in Locate, and if there is not a single location that can fulfill the entire order or line quantity. See the Use Split Order (L56) system control value for examples, and see the Locate Operations Guide or online help for background.

If the assigned fulfilling location rejects the order: The location assigned to fulfill an order or line can reject it if, for example, it does not have sufficient inventory. In this situation, the Order Broker uses the rules set up at the Preferences screen in Locate to select another location to fulfill the order. If the location where the order is currently assigned changes, CWSerenade updates this information the next time it sends a status inquiry to Locate, typically through pick slip generation, and receives the new information in the response.

Note: An order normally remains in Rejected status in Locate only for a moment. If for any reason Locate receives a status inquiry request when the order’s status is Rejected, CWSerenade does not update the order until the next time it sends a periodic status inquiry.

What if the Order Broker cannot find a location to fulfill the order or line? In some cases, the Order Broker cannot assign an order to a location because there are no locations with sufficient inventory that are eligible based on the business rules set up in Locate at the Preferences screen. In this situation, the Order Broker assigns the order to the Default Unfulfillable Location specified in Locate, which should match the setting of the Locate Default Location Code/Unfulfillable (K56) system control value. When CWSerenade receives a response message indicating that the order was assigned to the unfulfillable location and has a status of Unfulfillable, it:

• clears the Drop ship flag and the Printed quantity on the Order Detail line

• changes the status of the Order Broker record to U (unfulfillable)

• writes an Order Transaction History record (for example, Ln#: 2 Unfulfillable by Broker)

• returns the line to standard backorder or soldout processing, including updating the Backorder quantity for the Item Warehouse and updating the PO Layering record

An order might be flagged as unfulfillable when the Order Broker first receives the request message, or after one or more locations have rejected the order for fulfillment; in this case, CWSerenade receives notification the next time it sends a periodic status inquiry, as described below.

Note: Prior to Locate 5.3, the Default Unfulfillable Location is labeled the Default Shipping Location at the Preferences screen.

Notifying the customer of fulfillment through the Order Broker: The order confirmation email indicate a status of Store Ship for order lines assigned to the Order Broker. See the Order Confirmation Email Sample and Contents for more information.

Brokered Backorder Fulfillment Process: After Order Creation and Status Updates

Status inquiry and response process: The BROKER process in Working with Integration Layer Processes (IJCT) sends periodic status inquiry requests to the Order Broker. You use the Order Broker Status Update Interval (K10) system control value to define how many minutes CWSerenade should wait before sending status inquiry requests.

Activity	Status in Locate	Status in CWSerenade	Additional Updates to Order Broker Record and Order Transaction History
CWSerenade sends the submit order message to Locate and restricts the order line from standard backorder processing in CWSerenade by setting the Drop ship flag and the Printed quantity.	not yet created	Waiting (W)	• creates an Order Broker History record to track the order submission (A - Send Order Request) • writes an Order Transaction History message indicating that the order line was submitted to the Order Broker (for example, Ln#: 2 Submitted To Broker)
CWSerenade receives the submit order response from Locate	new_order	Acknowledged (K)	If there is a single fulfilling location: • creates an Order Broker History record to track the response (B - Receive Order Response) • updates the Order Broker record with the assigned fulfilling location • writes an Order Transaction History message (for example, Ln#: 1 Acknowledged by Broker) Otherwise, if there are multiple fulfilling locations, CWSerenade sends a status inquiry request to Locate and performs the above activities when it receives the response.
Polling: Each fulfilling location, typically a store location in a point-of-sale system such as Xstore, is responsible for polling the Order Broker periodically to check for new orders. Once the Order Broker receives a polling request from a location, it sends a polling response, listing the details of all new orders assigned to the location for fulfillment.	polled	Polled (P) (after receiving status inquiry response)	• creates an Order Broker History record (D - Receive Status Response) • writes an Order Transaction History message (for example, Ln#: 1 Polled by Broker)
Order accepted? If the assigned location can fulfill the order or line, it sends a status update message accepting the order or line to the Order Broker.	accepted	Accepted (A) (after receiving status inquiry response)	• creates an Order Broker History record (D - Receive Status Response) • writes an Order Transaction History message (for example, Ln#: 1 Accepted by Broker)
Order rejected? If the assigned location cannot fulfill the order or line, it sends a status update rejecting the order or line to the Order Broker. The Order Broker then:
• Attempts to find another location, subject to the rules you have set up in Locate. If it finds another location, the Order Broker updates the record in its database and changes the order status back to new_order. Then the process begins again as the Order Broker waits until the newly-assigned location polls for orders.	new_order	Acknowledged (K) (after receiving status inquiry response)	• creates an Order Broker History record (D - Receive Status Response) • writes an Order Transaction History message (for example, Ln#: 1 Acknowledged by Broker)
• If the Order Broker does not find another fulfilling location, it flags the order or line as unfulfillable by assigning it to the Default Unfulfillable Location you have set up in Locate (matching the Locate Default Location Code/Unfulfillable (K56) in CWSerenade). When CWSerenade receives the status inquiry update indicating a fulfilling location that matches the Locate Default Location Code/Unfulfillable (K56), it flags the order or line as unfulfillable and returns the line to standard backorder or soldout processing, clearing the Drop ship flag and the Printed quantity for the order line. Note: Prior to Locate 5.3, the Default Unfulfillable Location is labeled the Default Shipping Location at the Preferences screen.	new_order	unfulfillable (U) (after receiving status inquiry response)	• creates an Order Broker History record (D - Receive Status Response) • writes an Order Transaction History message (for example, Ln#: 5 Unfulfillable by Broker)
Order shipped? Once the fulfilling location has shipped the order or line, it sends a status update message to the Order Broker, providing the ship via and tracking number if available. The Order Broker changes the status to fulfilled and stores the ship via and tracking number so that it can send this information to CWSerenade. When CWSerenade receives notification, it clears the Drop ship flag and the Printed quantity, and submits the order line to billing. If the Order Broker provides a valid ship via code and a tracking number, the tracking number is a live link in the shipment confirmation email.	fulfilled	completed (X) (after receiving status inquiry response)	• creates an Order Broker History record (D - Receive Status Response) • writes an Order Transaction History message (for example, Ln#: 2 Shipped by Broker) • writes Order Transaction History messages indicating the ship via and the tracking number passed from the Order Broker (for example, ----VIA: UPS and ----TRK#: ABCDEFG1234567890)
Order status changes? If the Send Held Orders to Locate (M18) system control value is selected, CWSerenade sends held brokered backorders to Locate, but with the Under Review flag set to Y; also, CWSerenade sends an order update to Locate if the order’s status changes from held to open, or vice versa.	no change	no change	• when the change occurs after initial order creation and submission, writes an Order Transaction History message (for example, Request ID: 78390 Under Review: N)

Picked? If the assigned fulfilling location reports that a brokered backorder is in Picked status, the Working with Order Broker (WOBR) option indicates a status of Accepted.

Canceling a brokered backorder: See Canceling a Brokered Backorder Request for a discussion of the updates that take place when you cancel an Order Broker request at the Work with Order Broker Screen or in order maintenance.

Reviewing brokered backorders in order inquiry: You can use the Brokered Backorder Summary Screen to review the current status of all brokered backordered lines on a single order. Also, you can select D/S Status for a single brokered backorder line at the Order Inquiry Detail Screen to advance to the Display Order Broker Details Screen, where you can review a single brokered backorder line on the order.

Quantity not indicated in order transaction history messages: The order transaction history messages do not specify the quantity affected by the update; however, if you split orders and lines, the quantity affected may be less than the total order line quantity. For example, if the Order Broker splits an order line across two locations for fulfillment, and one of the locations fulfills its assigned quantity, the order transaction history message of Ln#: 2 Shipped by Broker does not indicate the fulfilled quantity.

Rules for Submitting Backorders to the Order Broker

To be eligible for submission to the Order Broker, the backordered item must have the Locate eligible flag selected. Also, the order line must be:

• fully backordered

• in open status

And must not:

• have a future arrival date or be flagged as a future order

• be flagged as a drop ship item

• be gift wrapped

• have any special handling

• be ineligible based on the trigger rules for the BROKER process in Working with Integration Layer Processes (IJCT)

• be a retail pickup or delivery order received from the Order Broker

• be a ship-to-store order

• be for a customer flagged to bypass reservation

• be a set master item or a set component

CWSerenade does not consider the item’s Projected returns quantity, if any, when determining whether the item is eligible for fulfillment through the Order Broker.

Also, the order must be:

• open, if the Send Held Orders to Locate (M18) system control value is unselected; otherwise, the order can be held. In this case, the order’s Under Review flag is selected. See the system control value for more information.

• fully paid and authorized

System control values: System control values also determine whether an order line is eligible if it is:

• for an item expected on an open purchase order line for the related warehouse with a due date within the Order Broker Due Date Threshold (K11)

• on an order flagged to ship complete, if the Order Broker Include Ship Complete Orders (K12) system control value is unselected

• coordinate grouped with other items, if the Order Broker Include Coordinate Grouped Orders (K13) system control value is unselected

• on a gift order, if the Order Broker Include Gift Orders (K14) is unselected

Sellout prevented: If an order line meets all of the criteria, it is brokered even if the item is flagged with a soldout control code. See Brokering Items with Soldout Control Codes for a discussion.

BROKER Periodic Function

The BROKER periodic function submits orders to the Order Broker if they were not eligible for submission when they were created. For example, the periodic function submits order lines if:

• your company was not configured to send brokered backorders to Locate when the order was created

• the order was in held status at initial creation and was subsequently released from hold, and the Send Held Orders to Locate (M18) system control value is unselected

• the order line was partially reserved, but then the reserved quantity was shipped and there is still a backordered quantity remaining on the order line. The order line is not eligible to be submitted to the Order Broker until any reserved quantity is printed and shipped.

Note: When the periodic function submits an order line as a brokered backorder, the function performs all the updates described under Brokered Backorder Fulfillment: Initial Order Creation, but also decreases the Backorder quantity for the Item Warehouse record, since this quantity had been increased when the line was created.

See Additional Locate Setup in CWSerenade for background on setting up the BROKER periodic function.

Brokering Items with Soldout Control Codes

Items that are Locate eligible and flagged with a S/O control code are still eligible for brokering rather than selling out, provided they meet the Rules for Submitting Backorders to the Order Broker. If the soldout control status is:

• sell out immediately: the item is eligible for brokering even if there is an available quantity in an allocatable warehouse.

• include on-order: the item is eligible for brokering if it is backordered, provided there is not an open purchase order that could fulfill the order that is due within the Order Broker Due Date Threshold (K11), if specified. If no Order Broker Due Date Threshold (K11) is specified, the item is eligible for brokering regardless of open purchase orders. The Projected returns quantity, if any, for the item is not evaluated; see Projected Returns for background on how you can use the Projected returns quantity to prevent selling out items in certain situations.

• exclude on-order: the item is eligible for brokering if it is backordered, regardless of whether there are any open purchase orders.

If the item is unfulfillable: If the Order Broker is unable to fulfill an order line, the line returns to standard backorder or soldout processing. The process flow is:

• An item is assigned a soldout control value and would be sold out on the order if the item were not locate eligible. CWSerenade submits the order line to the Order Broker, but there is no store location that can fulfill the item, so the Order Broker returns a status of Unfulfillable.

• When CWSerenade receives the status update from the Order Broker, it changes the order line status to sold out (S) if the order line is currently eligible to sell out based on the soldout control value and availability.

• The next time you use the Processing Auto Soldout Cancellations (MASO) option, the soldout line is listed on the Auto Soldout Register, even though it did not sell out through Process Auto Soldouts and even if it is not assigned a soldout control status of 1 (sell out immediately).

• The next time you use the Generating Soldout Notifications (MSON) option, CWSerenade generates a soldout notification.

The same processing occurs if the Order Broker returns an error for the brokered order line.

Gift wrap or special handling: Based on the Rules for Submitting Backorders to the Order Broker, an order line is not eligible for brokering if it is flagged for gift wrap or special handling. If the gift wrap or special handling applies to the item:

• when the order line is initially created, then the line does not broker; instead, it sells out or remains backordered, as if it were not flagged as locate eligible. This is the case when the order API or ecommerce interface creates the order.

• after the order line is initially created (for example, by selecting Special Handling for the line in order entry), then if the soldout control status is:

• sell out immediately: the line sells out the next time you use Processing Auto Soldout Cancellations (MASO).

• include on-order quantity or exclude on-order quantity: the line does not sell out automatically.

You can use a backorder report to identify order lines that could not be brokered because of gift wrap or special handling, and that did not sell out automatically. See Order Status and Activity Reports for more information.

Future orders: Since future orders are not eligible to be brokered based on the Rules for Submitting Backorders to the Order Broker, items flagged Locate eligible and assigned soldout control values sell out automatically on future orders, just as they would if they were not flagged Locate eligible. Once an order is no longer considered a future order, Locate eligible items on the order can be brokered through the BROKER periodic function if they meet the Rules for Submitting Backorders to the Order Broker.

If reserving against a non-allocatable warehouse: Based on the Reserve from Non-Allocatable Warehouse (J25) and Disregard Soldout Controls for Non-Allocatable Warehouses (J27) system control values, you can reserve inventory against a non-allocatable (retail) warehouse for a retail order, and disregard an item’s soldout control assignment. In this case, even if the item’s Locate eligible field is selected, the item reserves against the non-allocatable (retail) warehouse if the order type is associated with that warehouse and there is inventory in that warehouse.

Things to Note About Brokered Backorders

Canceling order lines: It is important to confirm that the remote store location assigned to fulfill the order line has not begun the shipment process before you cancel an order line or Order Broker request in CWSerenade. Depending on the Order Broker Status Update Interval (K10), the most current information about the Order Broker request in CWSerenade might be out of date.

Freight charges included? Freight charges for the order are included in the SubmitOrder message only if the Use Split Order (L56) system control value is selected.

Customer address updates: If you change the customer’s name or address in CWSerenade after generating the initial Order Broker request, the Order Broker integration does not send this updated information to the assigned fulfilling location.

Held orders submitted? When the Send Held Orders to Locate (M18) system control value is unselected, if an order is initially created in held status and then released from hold, CWSerenade does not automatically submit the order to the Order Broker. To submit the order, you can run the BROKER Periodic Function (program PFR0083). See Locate/CWSerenade Configuration (Order Broker) for background.

Order lines not resubmitted: If an order line has previously been submitted to the Order Broker and the Order Broker request was flagged as unfulfillable or put in error status, the BROKER periodic function does not resubmit the order line to the Order Broker for fulfillment.

Reserve quantity limit: If an order line exceeds the Reserve qty (Reserve quantity limit) specified for an item, CWSerenade still submits the order line to the Order Broker for fulfillment, provided the line is eligible based on the Rules for Submitting Backorders to the Order Broker.

Inventory transaction history: If the Create Item Transaction History for Non-Inventory Items (E39) system control value is selected, CWSerenade writes a NONINVISSU transaction record when the BROKER process receives a status update indicating that the assigned location has shipped the order or line. See that system control value for more information.

Backorder notices: The Generate Backorder Notices (GBOC) option does not generate backorder notices for an order line when it has an Order Broker request in process; however, if the status of the Order Broker request changes to unfulfillable (U) or error (E), or if you cancel the Order Broker request without canceling the order line itself, the order line returns to standard backorder processing and is eligible to have backorder notices generated.

Purchase order layering: The batch PO layering job does not decrease the quantity on open purchase order layers in the PO Layering table for lines assigned to the Order Broker as it does for any other backordered lines. However, if the Order Broker cannot fulfill the assigned order line, the line is then subject to regular PO layering. See Purchase Order Layering and Backorder Notifications for background.

Tracking numbers in shipment confirmation email: If the fulfilling location supplies information on the shipping agent and a tracking number, the Order Broker passes this information to CWSerenade. If the shipping agent matches a valid ship via code in CWSerenade, the shipment confirmation email lists the description of the ship via and the tracking number as a live link. Otherwise, if the shipping agent does not match a ship via set up in CWSerenade, then the shipment confirmation lists the shipping agent as it was passed from Locate, and the tracking number is plain text.

Note: If a brokered backorder ships on the same day as a warehouse shipment, the shipment confirmation email includes just the tracking number for the brokered backorder. This occurs regardless of whether you consolidate invoices.

See the Shipment Confirmation Email Sample and Contents for more information.

Tracking numbers in customer history API: If the Order Broker passes the shipping agent and a tracking number, the Detailed Order Inquiry Response XML Message (CWORDEROUT) includes this information provided CWSerenade can link the line number, shipping agent, and tracking number from the Order Transaction History messages to the invoice based on date.

Example:

The fulfilling location supplies information on the shipping agent and the tracking number to the Order Broker, and the Order Broker passes this information to CWSerenade. CWSerenade writes Order Transaction History records such as: SHIPMENT Ln#: 5 Shipped by Broker SHIPMENT ----VIA: DHL SHIPMENT ----TRK#: GHI123 The Order Transaction History records have the same date as the invoice. The CWORDEROUT message passed through the customer history API includes the tracking information, for example: <Shipment invoice_nbr="1240360" invoice_ship_quantity="1" invoice_ship_date="11292011" invoice_tracking_nbr="GHI123" invoice_ship_via_desc="DHL"/>

Note: If CWSerenade writes the Order Transaction History for the shipment of a brokered backorder on a date that differs from the invoice date, then no tracking information is included in the customer history response. This situation might occur if, for example, CWSerenade receives the status update of the shipment before midnight, but the billing async job does not create the invoice until after the job is automatically stopped and restarted, so that the next date is assigned to the invoice.

Other Order Broker orders not eligible: CWSerenade does not submit a backordered delivery, retail pickup, or ship-to-store order to Locate for fulfillment.

Line_locate_eligible flag in the CWORDEROUT message: If the Send B/O to Locate (K08) system control value is selected, the Detailed Order XML Response (CWORDEROUT) message used in the generic order API includes a flag for each order line to indicate whether the order line meets the Rules for Submitting Backorders to the Order Broker. Even if this flag is set to Y, it is possible that the line cannot be fulfilled as a brokered backorder if, for example, the Order Broker does not find a location that has the item available.

The Generic Customer History API also uses the CWORDEROUT message. The message includes the line_locate_eligible flag if the order line is still open. In the case of the generic customer history API, the line_locate_eligible flag might be set to Y even if, for example, the line was already submitted to the Order Broker, and then returned to normal backorder processing because the Order Broker did not find a location to fulfill it.

Order Broker requires postal code: If the shipping address on a brokered backorder does not include a postal code, the Locate Order Broker rejects it. The Require postal code? flag for the country determines whether a postal code is required. See Setting Up the Country Table (WCTY) for background.

Reviewing brokered backorders in order inquiry: You can use the Brokered Backorder Summary Screen to review the current status of all brokered backordered lines on a single order. Also, you can select D/S Status for a single brokered backorder line at the Order Inquiry Detail Screen to advance to the Display Order Broker Details Screen, where you can review a single brokered backorder line on the order.

The OBR status remains on each order line that is fully or partially fulfilled through Locate as a brokered backorder. This status is displayed on the Order Inquiry Detail Screen.

The original backorder reason remains on the order line after fulfillment through Locate as a brokered backorder. This reason is displayed on the Display Order Detail Screen (Reviewing Order Line Detail). Typically, the backorder warehouse also remains on the order line as well, and is displayed on the Display Order Detail Screen (Reviewing Order Line Detail); however, if a shipment from the warehouse follows the fulfillment through Locate, the backorder warehouse field is cleared.