Managing Fulfillment Requests for Vendor Portal Suppliers

This guide explains why certain fulfillment request status transitions are restricted via API for suppliers using the Flxpoint Vendor Portal.

Status transition restrictions

Fulfillment requests (FRs) associated with suppliers configured to use the Flxpoint Vendor Portal follow a specific workflow that differs from standard FRs. Because these requests are managed directly within the portal environment, the API endpoints used to manually advance statuses to Processing or Processed are restricted.

Restricted endpoints

The following endpoints will return errors when called for a Vendor Portal-sourced fulfillment request:

POST /fulfillment-requests/{fulfillmentRequestId}/processing
POST /fulfillment-requests/{fulfillmentRequestId}/processed

Note: These restrictions ensure data integrity by requiring that status changes occur through the intended Vendor Portal workflow rather than external API overrides.

Expected error responses

If you attempt to transition a Vendor Portal FR via the API, the system will return the following error messages based on the target status:

Endpoint	Error Message
/processing	This Fulfillment Request's supplier is configured to send Fulfillment Requests from the Vendor Portal and cannot be transitioned to Processing.
/processed	Only Fulfillment Requests in Processing status can be transitioned to Processed.

Recommended workflow

To advance these fulfillment requests from Unprocessed to Processed, users should utilize the standard Vendor Portal interface. The API cannot be used to bypass the Unprocessed status for these specific suppliers. When a vendor interacts with the fulfillment request within the portal, the status will update automatically in Flxpoint to reflect their actions.