Order Routing: Preview & Troubleshooting
June 26, 2026
Summary
Order Routing: Preview & Troubleshooting
What this does
Pre-generation preview
See exactly which source Flxpoint will select - and why - before a fulfillment request is created.
Financial estimation
Snapshot of estimated profit or loss - order revenue minus fulfillment cost - for each routing option.
Routing logs
Three log types - Generation, FR Logs, Order Status History - to trace exactly what happened after routing.
Re-generate FRs
If routing produced unexpected results, you can re-generate FRs even after they've been processed or acknowledged - only closed orders block it. Re-generating a processed/acknowledged FR re-submits it to the source and can create duplicate order submissions.
Two ways to access the preview
| Access point | When it's available | What it shows |
|---|---|---|
| Order Routing Preview link | Before any fulfillment request has been generated | Which source will be selected, warnings and errors per routing group, financial estimation summary |
| Preview button | Before or after a fulfillment request is generated | Same as above, plus the ability to see how routing would differ under an alternative routing group |
Important - read before using preview
The preview tool allows you to edit an existing routing group inline. Any changes saved take effect immediately for all future orders - not just the order you're previewing. Test with a new group first if you're unsure about the change.
The profit/loss estimate uses the source inventory cost plus the estimated shipping and dropship fee workflows. If those values aren't configured on your sources, the estimate will be incomplete or zero - making the financial summary unreliable for routing decisions.
Re-generating a fulfillment request is possible even after it has been Processed or Acknowledged - it is only blocked once the order is Closed. Re-generating a Processed/Acknowledged FR re-submits it to the source, which can create a duplicate order submission - coordinate with the source before doing so.
The preview reads live source inventory at the moment you view it. If source inventory syncs in the interval between previewing and generating, the selected source could change. For high-velocity sources, generate immediately after previewing.
Financial estimation summary - how it's calculated
| Line | Order revenue source | Fulfillment cost source | Profit / loss |
|---|---|---|---|
| Subtotal | Channel invoice subtotal | Fulfillment request subtotal (source inventory cost) | Revenue subtotal − Cost subtotal |
| Shipping | Channel invoice shipping cost | Estimated shipping cost (from source workflow or rate shopping) | Revenue shipping − Cost shipping |
| Miscellaneous | Sum of channel invoice tax, dropship fee, discount | FR dropship fee | Revenue misc. − Cost misc. |
Three log tools for troubleshooting
1
Warnings & Generation Logs
Shows errors and warnings encountered when routing tried to generate FRs. Check this first when an order fails to route.
2
Fulfillment Request Logs
Full history of each FR - status changes, transmission attempts, errors from the source. Check this for post-generation issues.
3
Order Status History Logs
Timeline of every order status change with user attribution and notes. Check this to understand when a hold was placed and by what trigger.
All three tools are accessible from the order detail page under the Fulfillment Requests section. Use them in the order listed - Generation Logs first, FR Logs second, Order History third - to narrow down the failure point.
Common issues
Preview shows a warning but doesn't explain which rule failed
▾
Open Generation Logs directly below the preview panel - the warning message in the preview section is a summary, but the logs contain the specific rule and source that failed evaluation. Look for the rule name (e.g. "Single Fulfillment Request - Required: no single source has all SKUs") and use that to adjust your priority configuration.
Financial estimation shows $0 or incorrect profit
▾
The estimate depends on three data points all being present: source inventory cost, estimated shipping cost workflow, and estimated dropship fee workflow. Go to
Source → Workflows and confirm that both the Estimated Shipping Cost and Estimated Dropship Fee workflows are enabled and have rules configured. If either is missing, that part of the cost calculation is $0.Preview selected a different source than the one I expected
▾
Open the Generation Logs and find the routing decision trace - it shows which sources were eligible at each priority step and why a source was excluded or ranked lower. Common reasons: the expected source has the SKU at higher cost, a Required priority eliminated it, or source inventory hasn't synced recently. Check the source's last sync timestamp on its inventory page.
Cannot re-generate fulfillment request after a routing mistake
▾
Re-generation is available on Unprocessed, Processing, Processed, and Acknowledged FRs - it is only blocked once the order is Closed. If the FR has already been sent to or acknowledged by the source, re-generating will re-submit it and can create a duplicate order submission, so coordinate with the source first. To prevent this going forward, enable Routing Completed Workflow in the routing group to hold split or unexpected FRs in Unprocessed for review before they transmit.
FAQs
Does previewing an order affect inventory or trigger any actions?
No. Previewing is read-only - it evaluates routing logic and shows you results without reserving inventory, creating FRs, or communicating with sources. Nothing changes in the system until you click Generate.
Can I preview routing on an order that already has a fulfillment request?
Yes. The Preview button is available before and after FR generation. It's useful for comparing what a different routing group would have selected. This is also the recommended way to test routing group changes before applying them as your default.
Why does the Order Status History show a hold I didn't create manually?
System-generated holds appear in Order Status History with the trigger as the author (e.g. "Routing Engine" or "Automation Rule"). Common system hold reasons: no eligible source found, Required routing priority unmet, unmapped shipping method. The hold reason note in the history entry will specify which condition triggered it.