Fulfillment Request Statuses
Summary
A glossary of the additional fulfillment request/order statuses and error states beyond the standard processing lifecycle, and what to do about each.
Beyond the main Unprocessed → Acknowledged lifecycle, fulfillment requests can show several additional statuses and error states. Use this as a quick glossary when a fulfillment request is not in one of the standard states.
| Status | What it means |
|---|---|
| Transferred | The original fulfillment request/order was transitioned to a Transfer Order. Transfer Orders copy line items from multiple Unprocessed fulfillment requests going to a single source and set the delivery address to a facility (such as an internal warehouse) that receives bulk orders. |
| Voided | A fulfillment request that has not been sent to the source yet (Unprocessed or Processing) can be voided. |
| Canceled | A fulfillment request that has already been sent (Processed or Acknowledged) can be canceled. |
| Cross Docked | The fulfillment request was added to a Cross Dock PO and is fulfilled through that consolidated purchase order. |
“Fulfillment Request # Exceeds Max Length” appears in place of the status
The generated fulfillment request number is longer than the Max FR/FO # Length configured for the source, which blocks processing (and auto processing). Open the fulfillment request, Actions → Edit, and shorten the number to fit. See FR/FO Strategies to set or adjust the max length and the Exceeds strategy.
“Duplicate PO/FR #” when creating a fulfillment request
This appears when you try to create a fulfillment request using an FR/FO number that already exists. Use a unique FR/FO number for the new request.
“Processing Error” on a fulfillment request
A Processing Error means the fulfillment request failed to send to the source. Review the fulfillment request for the specific error returned by the source, correct the cause (credentials, mapping, or source availability), and reprocess.
Limited recent ticket data covers these specific status errors; the entries above reflect the documented behavior and the error wording shown in the app.