Managing FRs: Auto & Manual

June 26, 2026

Summary

How to generate, process, preview, void, and regenerate FRs - covering both the automated path and every manual action available on an order.

What this covers

Auto-generate & auto-process

Two independent settings that together create a fully hands-off FR lifecycle from order import to source transmission.

Preview routing

See which source will be selected and any errors before generating an FR - no live impact.

Manual create

Bypass routing entirely and pick any source by hand - for broken links, testing, or urgent edge cases.

Void & regenerate

Remove an unprocessed FR cleanly and run routing again to pick a different source.

Auto-generate vs auto-process: two separate settings

Common confusion: Enabling auto-generate does NOT enable auto-process. Both settings must be on independently for a fully automated, hands-off flow.

Setting	What it does	Where to configure	Scope
Auto Generate FR on Import	Creates FR using routing priorities the moment an order imports from a channel. FR starts as Unprocessed.	`Channels → ⚙ → Settings → Auto Generate Fulfillment Request on Import`	Per channel
Auto-Process FR (Global)	Automatically advances all FRs from Unprocessed → Processing on the next integration run, sending them to sources.	`Settings → Orders → Fulfillment Request Strategy → Auto Process Fulfillment Requests`	All sources
Auto-Process FR (Per source)	Enables or overrides auto-processing for one specific source. Per-source setting always wins over global.	`Sources → ⚙ → Fulfillment Requests → Strategy → Override: Auto Processing`	Per source

Manual actions available on every order

Action	When to use it	What it does
Preview Order Routing	Before generating any FR - to validate routing config without risk	Shows which source routing will select, any warnings/errors per routing group, and a financial estimate. Read-only - nothing changes.
Generate FR (manual trigger)	Auto-generate is off, or FR needs to be created on demand	Runs the full routing process: selects source, attaches FR, applies FR strategies, logs everything.
Create Fulfillment Request (bypass routing)	Broken link orders, testing new sources, urgent re-routes	Lets you manually pick any source and shipping method, ignoring all routing rules. You are responsible for source eligibility.
Process	Auto-process is off, or you want to send a specific FR now	Marks the FR as Processing - it will transmit on the next Send FR integration run.
Re-Generate Fulfillment Requests	Routing produced the wrong source and FR is still Unprocessed	Runs routing again and creates a new FR. Previous unprocessed FR is voided.
Void	FR is Unprocessed or Processing - not yet sent - and you want to remove it	Removes the FR cleanly. Add a reason note. FR cannot be voided once Processed.

Non-obvious failures

Turning on auto-generate per channel, not globally

Auto-generate is channel-specific. Enabling it on one channel does not affect others. If you add a new channel and orders aren't auto-generating FRs, check whether the toggle is on for that specific channel at Channels → ⚙ → Settings.

Manual Create FR bypasses routing rules entirely

Using Create Fulfillment Request lets you select any source regardless of routing rules, inventory availability, or shipping policy. There is no validation - Flxpoint will create the FR even if the source doesn't carry the SKU. Use only when you've confirmed the source can fulfill.

Keep auto-process off when first configuring a source

Enable Auto Processing on a new source only after you've validated that the FR# format, shipping methods, and credentials are all correct. FRs sent with wrong configuration go to FAILED status and may require manual recovery with the source.

Generation logs are your first troubleshooting tool

Every FR generation - auto or manual - leaves a log capturing routing decisions, rate shopping results, strategy overrides, and errors. When something routes unexpectedly, open Generation Logs before contacting support. The logs show exactly which rule excluded or selected each source.

Manual order closure and FR states

When you manually close an order, Flxpoint automatically handles associated Fulfillment Requests based on their current status. FRs in Unprocessed, FR # exceeds max length, Additional info required, or Duplicated FR # states are automatically voided and their committed stock is released. However, FRs in Processed or Acknowledged states remain untouched while their committed stock is released. If an order has any FR in a Processing status, the system will block you from closing the order until the FR moves to a different state.

Committed stock behavior

Committed stock is released regardless of order status if an FR is in a Canceled or Voided state. For Partially Canceled FRs, stock is released only for the specific item quantity canceled. If an FR is in a Cross Docked state, committed stock is moved to a stub FR. You can find a tooltip explaining these behaviors next to the committed stock setting in your account.

Bulk actions and reopening

You can now reopen orders in bulk from the order listing page. When attempting to bulk close orders, if any selected order contains an FR in a Processing status, a modal will appear preventing the action and identifying the affected orders.

Common issues

Orders are importing but FRs are not being auto-generated

Auto-generate is per-channel. Go to Channels → ⚙ → Settings and confirm Auto Generate Fulfillment Request on Import is on for that channel. If the toggle is on but FRs still don't generate, open Generation Logs on an affected order - if routing failed to find an eligible source, FR creation is blocked even with auto-generate enabled.

FR was generated but not sent - sitting Unprocessed indefinitely

Auto-process is not enabled for that source (or globally). Check Settings → Orders → Fulfillment Request Strategy for the global toggle, and Sources → ⚙ → Fulfillment Requests → Strategy → Override: Auto Processing for source-level override. To unblock immediately, select the FR and use Actions → Process.

Re-Generate created an FR to the wrong source again

Re-Generate runs your existing routing configuration - if the same source wins again, the routing logic hasn't changed. Use Preview Order Routing first to identify why that source is winning (check routing group priorities, source inventory availability, estimated costs). Adjust the routing group, then re-generate.

Shipping label purchase page shows an infinite loading icon?

This typically occurs when a fulfillment routing (FR) strategy is missing for the source. Flxpoint now automatically creates default FR strategies for all new sources and has backfilled them for existing accounts. If you still encounter this, navigate to Sources → ⚙ → Fulfillment Requests → Strategy and ensure a strategy is saved for that source.

FulfillmentRequestProcessingEvent webhook is not firing for auto-generated FRs?

There is a known issue where the FulfillmentRequestProcessingEvent webhook does not trigger for orders that are auto-routed and have fulfillment requests auto-generated. This occurs because the system check for webhook eligibility happens before the internal status ID is fully assigned to the purchase order. If your workflow relies on this webhook for automation, you may need to monitor fulfillment request statuses manually or use a manual process trigger until a platform update resolves the timing of this event check.

FAQs

When should I manually create a FR instead of generating through routing?

Two main cases: (1) the order has a broken link - a product not matched to a source inventory SKU - so routing can't select a source; (2) you're testing a new source or channel setup before enabling automation. Manual creation bypasses all routing rules and requires you to select the source yourself.

Does previewing an order affect anything?

Not entirely - Order Routing Preview lets you edit the routing group and apply changes to the current routing logic. Aside from that, it's read-only: it evaluates routing logic and shows results without reserving inventory, creating FRs, or communicating with sources. Nothing changes until you click Generate.

Can I void an FR after it's been processed?

No. Void is only available for Unprocessed or Processing FRs. Once an FR has been sent (Processed or Acknowledged), you must use Actions → Adjust FR/FO to cancel it - and you should coordinate with the source first since they've already received the order.

Back to Fulfillment Requests