Fulfillment Requests & Fulfillment Orders
June 26, 2026
Summary
What FRs and FOs are, how they're generated, every status and what it means, how to adjust or cancel, bulk operations, and bin location tracking.
What this covers
FR/FO generation
How an order becomes a fulfillment request - automatically via routing or manually created.
Processing lifecycle
All 8 statuses an FR passes through from Unprocessed to final state, including shipment statuses.
Adjusting FRs
Canceling items, rerouting to another source, or voiding and regenerating from scratch.
Bulk actions
Process, acknowledge, hold, cancel, or regenerate many FRs at once from the Orders or FR tab.
Bin locations
Track physical inventory location by SKU in internal warehouses, visible on the FR/FO record.
Complete FR / FO status reference
UNPROCESSED
Default state after generation. The FR exists in Flxpoint but has not been sent to the source. No action happens until this advances manually or via auto-processing.
PROCESSING
Flxpoint is transmitting the FR to the source on the next Send FR integration run. Triggered by Auto Processing or manually via
FR Actions → Process.PROCESSED
FR successfully sent; source has not yet confirmed receipt. Common for EDI, file-based, and email sources. Eligible to receive shipments. Can be manually advanced to Acknowledged once confirmed.
ACKNOWLEDGED
Source confirmed receipt - automatically (API sources) or manually in Flxpoint. Eligible to receive shipments. Normal operating state for API-integrated sources.
FAILED
Transmission attempt was rejected or errored. Check FR logs for the error message. Resolve the cause then Reprocess, or Void and regenerate.
CANCELED
FR was canceled after being sent to the source. Triggers a decision: reroute to another source, or cancel the order entirely.
VOIDED
FR was removed before being sent. Only possible on Unprocessed or Processing FRs. Use
FR Actions → Void. Different from Canceled - voided FRs were never transmitted.CROSS DOCKED
The original FR has been consolidated into a Transfer Order (Cross Dock PO). Line items were moved; the original FR is no longer active.
Shipment statuses appear once an FR is Processed or Acknowledged and shipments begin arriving:
AWAITING SHIPMENT
All quantities on the FR are pending - no shipments received yet.
PARTIALLY SHIPPED
Some quantities have shipped; others are still pending or were canceled.
FULLY SHIPPED
All non-canceled quantities have shipped. FR is complete.
Voided vs Canceled - key difference
| Action | When it applies | FR was sent to source? | How to trigger |
|---|---|---|---|
| Void | FR is Unprocessed or Processing - not yet transmitted | No | FR Actions → Void + reason note |
| Cancel | FR is Processed or Acknowledged - already sent to source | Yes - coordinate with source first | FR Actions → Adjust FR/FO |
Adjusting a fulfillment request
| Scenario | Action | What happens next |
|---|---|---|
| Cancel specific line items | FR Actions → Adjust FR/FO | Quantity marked unallocated. Choose: reroute to another source or cancel order. |
| Reroute to another source | Click Create Fulfillment Request, enter PO #, select Source, select Source Shipping Method, choose Yes or No for Suppress Shipments?, select the item(s) via checkbox, optionally enter a note, and click Create | New manual FR created for the new source. Original canceled line remains. |
| Void and start over (not yet sent) | FR Actions → Void → Reason (optional), then click Yes | FR removed. Use FR Actions → Re-Generate Fulfillment Requests to run routing again. |
| Stop Processing | FR Actions → Stop Processing | Returns FR from Processing back to Unprocessed for review before retransmission. |
| Manually acknowledge | FR must be Processed → FR Actions → Acknowledge | FR moves to Acknowledged and becomes eligible for shipment receipt. |
Bulk actions - by tab
Orders tab order-level
Place HoldRelease HoldGenerate / Re-Generate FR/FOCancel
Select orders → Action → choose → confirm in popup.
FR/FO tab FR-level
ProcessReprocessAcknowledge
Select FRs → Action → choose → confirm. Status eligibility applies: Acknowledge only works on Processed FRs.
Non-obvious failures
PO# Exceeds Max Length blocks processing
When a generated FR number exceeds the configured Max Length, Flxpoint flags the FR with status
Fulfillment Request # Exceeds Max Length and prevents processing. The number is NOT trimmed automatically. Fix by editing the FR number to a shorter value via FR Actions → Edit, or adjust the Max Length setting on the "Source Fulfillment Request Strategy".Duplicate FR number prevents creation
If you attempt to create an FR with a PO number that already exists for that source, Flxpoint blocks creation with a duplicate error. Use a unique FR number - typically the system-generated one - or adjust your FR# Strategy if duplicates are recurring.
Bulk actions skip ineligible FRs silently
Bulk Acknowledge only works on FRs in Processed status. FRs in other statuses are silently skipped. Flxpoint shows a warning if none qualify or if some are skipped - check this message to understand what was actually actioned.
Canceling an order auto-voids eligible FRs only
When you cancel a full order, Flxpoint automatically voids any Unprocessed FRs. FRs that are already Processed or Acknowledged are not voided - you must manually cancel each one after coordinating with the source.
Common issues
FR generated but source says they never received it
▾Check FR status: if Unprocessed, auto-processing is off for that source - enable it at
Sources → Workflows → Source Fulfillment Request Strategy → Override: Auto Processing - choose either Auto Process or Use Global Fulfillment Request Strategy based on your requirements and click Update - then manually process via FR Actions → Process. If status shows Processed or Acknowledged, open the order timeline and look for the FRs timeline to confirm the transmission timestamp and share it with the source as proof of delivery.FR stuck in Processing status
▾Processing means transmission is in flight. If it's stuck, the integration run likely errored silently. Check the order timeline's FRs timeline for error details - common causes: source API credentials expired, source endpoint is down, or FR# format rejected. Fix the cause then use
FR Actions → Reprocess or bulk Reprocess from the FR tab.Quantities added back to order after cancellation aren't fulfilling
▾After a partial cancellation, if quantities are added back to the order, Flxpoint does not automatically create a new FR for them. You must manually create a new FR for the re-added quantities via Create Fulfillment Request, or regenerate FRs via
FR Actions → Re-Generate Fulfillment Requests.Bin Location column not visible on FR/FO tab
▾Click the ⚙ icon in the top-right corner of the FR/FO tab to open column visibility settings and enable Bin Location. The column only populates for sources configured as internal warehouses with bin location tracking. It appears only after the FR is generated.
FAQs
What's the difference between a Fulfillment Request and a Fulfillment Order?
The terms are interchangeable in Flxpoint - FR and FO refer to the same object. The platform uses FR/FO throughout the UI.
Can one order have multiple FRs?
Yes. If items span multiple sources, Flxpoint splits the order into one FR per source. Each is tracked independently. You can review the split in the Order Routing Preview before generating.
My FR shows Processed but the source hasn't shipped - is that normal?
Processed means Flxpoint transmitted successfully, not that the source has acted on it. For sources that don't auto-acknowledge, the FR stays Processed until you manually acknowledge it or they return a shipment. Once confirmed, advance it via
FR Actions → Acknowledge.What happens to the order if I cancel a fulfillment request?
Canceling an FR marks the quantity as unallocated - it doesn't cancel the order itself. You then choose: create a new FR to another source, or cancel the order. Flxpoint does not push the cancellation back to the originating channel.