Fulfillment Request Strategy
June 26, 2026
Summary
Configuration rules that control auto-processing, FR number format, max number length, and what happens when number limits are exceeded set globally or per source.
What this covers
Auto Processing
Skip manual processing - FRs transmit to sources automatically on the next integration run.
Fulfillment Request # Strategy
Control whether the FR number uses the Flxpoint order ID or the channel reference number, plus suffixes for splits.
Max FR# length
Flag FRs whose number exceeds your source's character limit before they block processing.
Exceeds max length strategy
Define what happens - void or hold - when an FR# exceeds the configured limit.
Where to configure - global vs per source
| Level | Navigation path | When to use |
|---|---|---|
| Global | Settings → Orders → Fulfillment Request Strategy | Default for all sources. Any source without a source-level override inherits these settings. |
| Per source | Sources → [Source] → Workflows → Source Fulfillment Request Strategy | Override global settings for a specific source. Per-source setting always takes priority over global. |
Strategy settings - full reference
| Setting | What it controls | Default |
|---|---|---|
| Auto Processing | When enabled, FRs are automatically advanced from Unprocessed to Processing and transmitted to the source on the next Send FR integration run - no manual step required. Can be set globally or overridden per source. | Off (FRs require manual processing) |
| Fulfillment Request Number | Defines what the FR number is built from. Options: Flxpoint Order ID (internal ID) or Channel Reference # (the channel's order number). When one order generates multiple FRs, Flxpoint automatically appends -1, -2, -3 suffixes. |
Flxpoint Order ID |
| Max FR# Length | Maximum character count allowed for FR numbers on this source. When a generated FR number exceeds this limit, the FR is flagged with status Fulfillment Request # Exceeds Max Length and cannot be processed until resolved. The number is NOT trimmed automatically. | Not set (no limit) |
| Exceeds Max FR # Length Strategy | Defines what happens when an FR number exceeds the max length. Options: Void (removes the FR) or Hold (keeps it on hold for manual action). Configured directly below the Max FR# Length field. | Hold |
| Pass Order Custom Fields to Fulfillment Request | Forwards order-level custom fields (e.g. gift message, internal notes) to the FR so the source receives them as part of the fulfillment instruction. | Off |
| Pass Order Line Custom Fields to Fulfillment Request | Forwards per-line-item custom fields (e.g. engraving text, lot numbers) to the FR line items so the source receives per-item instructions. | Off |
Non-obvious failures
Max Length does NOT trim the FR number
Setting Max FR# Length to 10 does not shorten any FR number to 10 characters. It only flags FRs that exceed 10 characters with a blocking status. You must manually shorten the number via
Actions → Edit or adjust your Fulfillment Request Number format to produce shorter values inherently.Per-source strategy silently overrides global
If a source has a strategy configured, its settings override the global strategy completely for that source - including auto-processing. If you change the global strategy and a source isn't behaving as expected, check whether it has a source-level override that's taking precedence.
Multi-FR suffixes can push numbers over max length
When one order splits into 3 FRs, Flxpoint appends
-1, -2, -3 to the FR number. If your base FR number is already close to your Max FR# Length, the suffix pushes it over. Account for suffix characters when setting the max - e.g. if your base can be 12 chars and you expect up to 9 splits, set max to 14 (12 + 2 for -9).Enable auto-process only after full source validation
Auto-processing sends FRs to the source without any manual review. Enable it for a new source only after you've confirmed: correct FR# format, valid credentials, correct shipping method codes, and at least one successful manual FR roundtrip. Failed FRs from a bad config require manual recovery with the source.
Common issues
FRs showing "Fulfillment Request # Exceeds Max Length" status
▾The generated FR number is longer than the Max FR# Length configured for that source. To resolve individual FRs: go to the FR →
Actions → Edit → shorten the FR# manually to fit within the limit → save → then process. To prevent recurrence: review your Fulfillment Request Number format setting and set Max FR# Length to match what your source actually accepts. Use the Fulfillment Request Status filter "Fulfillment Request # Exceeds Max Length" to find all affected FRs at once.Source is rejecting FRs because the PO number format is wrong
▾Go to
Sources → [Source] → Workflows → Source Fulfillment Request Strategy → Fulfillment Request # Generation and confirm the number source (Flxpoint Order ID vs Channel Reference #) matches what your source expects. Also confirm Max FR# Length is set correctly and that any split suffixes (-1, -2) are acceptable to the source. Void the rejected FRs, correct the strategy, then regenerate.FAQs
Can I set auto-processing for most sources but keep it manual for one specific source?
Yes. Enable Auto Process Fulfillment Requests globally at
Settings → Orders → Fulfillment Request Strategy, then go to the specific source and set the per-source Override to Do NOT Auto Process. The source-level setting always wins over global.Does changing the Fulfillment Request Number setting affect existing FRs?
No. The Fulfillment Request Number setting applies only to FRs generated after the change. Existing FRs keep their original numbers. If you need to change the number on an existing Unprocessed FR, edit it manually via
Actions → Edit.What's the recommended setup for a new source before going live?
Set auto-processing to Off at the source level. Manually generate and process a few test FRs, confirm the source receives them correctly with the right FR# format and shipping codes, then enable auto-processing once validated.