Managing Fulfillment Requests
Summary
How to generate, process, void, and re-generate fulfillment requests either automatically through routing or manually step by step, and where each setting lives.
Once an order is imported, the next step is creating the fulfillment request (FR). You can let Flxpoint handle generation and processing automatically, or manage each step manually when automation is not the right fit.
| Method | When to use |
|---|---|
| Automated | Flxpoint generates and (optionally) processes the FR on import, using your routing priorities. Best once a source is fully configured and tested. |
| Manual | You preview, create, generate, process, or void FRs yourself. Useful for broken-link orders, validating routing on a new source, or one-off fixes. |
Auto generation creates the FR on order import based on your current routing rules and available sources. It does not automatically process the FR unless auto processing is also enabled.
| To do this | Go here |
|---|---|
| Auto-generate FRs on import | Channels → gear icon next to the channel → Settings → enable Auto Generate Fulfillment Request on Import |
| Auto-process for one source | Sources → gear icon → Fulfillment Requests → Strategy → set Override: Auto Processing to Auto Process |
| Auto-process for all sources | Settings → Orders → Fulfillment Request Strategy → enable Auto Process Fulfillment Requests → Update |
Manual actions live on the order under the fulfillment request and the Actions menu.
| Action | How |
|---|---|
| Preview | Preview routing before an FR is created to see how routing groups apply and catch errors early. |
| Create | On the order, click + Create Fulfillment Request, key in the PO#, choose source and source shipping method, select items, then Create PO. This bypasses your routing priorities. |
| Generate | On the FR click Generate, or use order Actions → Generate Fulfillment Requests to run the full routing-based generation. |
| Process | On the FR, Actions → Process to queue it for the next Send FR run. |
| Void | Actions → Void, add a reason, confirm. You can only void an FR that has not been sent (Unprocessed or Processing). |
| Re-Generate | Order Actions → Re-Generate Fulfillment Requests creates a new unprocessed FR. |
New source: FR generated but nothing was sent. Auto generation and auto processing are separate. Generating an FR does not send it. Turn on auto processing (per source or globally) or manually process the FR so it is queued for the next Send FR run.
Manually created FR went to the wrong source. A manually created FR uses the source you selected in the Create Fulfillment Request dialog and ignores routing priorities. If you want routing to choose, use Generate instead of Create.
Cannot void a fulfillment request. Void is only available while the FR is Unprocessed or Processing. If the Void option is missing, the FR has already been Processed or Acknowledged (sent to the source); cancel it instead, then re-generate if you need a fresh FR.
Re-generating created a duplicate-looking FR. Re-Generate produces a new Unprocessed FR and leaves the prior one in place. Void the old FR (if it was not sent) so only the intended FR remains before processing.
When should I create a fulfillment request manually? Two common cases: an order has a broken link because the product is not on your sales channel and you want to send an FR without delay, or you set up a new channel or source and want to validate your routing rules and workflows before automating.
What is the difference between generating and processing? Generating creates and attaches the FR (running routing). Processing sends the FR to the source on the next Send FR integration run. An FR must be generated first, then processed (manually or automatically).
Do I have to choose Option 1 or Option 2 when generating manually? You only need one. You can click Generate directly on the FR, or use order Actions → Generate Fulfillment Requests. Both run the same generation process.
Can I preview routing before committing? Yes. Preview a fulfillment request before it is generated or created to see how routing groups affect it and surface potential errors or roadblocks first.
