Fulfillment requests represent product orders that are originated from Provider’s commerce system and sent to Vendor. Fulfillment requests are also interconnected with subscriptions and stored in the Subscriptions module. Thus, for instance, purchase requests create subscriptions, while cancel requests terminate them.
To process fulfillment requests, Vendors require information not only relative to their product, but also about the customer, supply chain, marketplaces, etc. Therefore, the Connect platform displays such data via fulfillment request details within each request. Access fulfillment request details via the user interface (as described below) or via the Connect API.
The following describes fulfillment request types, request statuses, how to access request details and how approve, inquire or reject a request.
Each request is assigned to one of the following types:
With each type summarized in the following table:
|#||Type||Description||Requests : Subscriptions|
|1||Purchase||Initial purchase of specified items that creates a request and a subscription.||1:1|
|2||Change||Adjustments of included items and item unit quantity in a subscription.||any number of requests per a subscription|
|3||Suspend||Requests that are switched to the administrative hold state.||any number of requests per a subscription|
|4||Resume||Requests that are switched back from the administrative hold state.||any number of requests per a subscription|
|5||Cancel||Cancellation of a request and a subscription. In case a cancel request is submitted and not approved, associated subscription will be switched to “terminating” state.||1:1|
Each request status represents a particular stage in the fulfillment processing. Request statuses usually correlate with a particular subscription status. The following table covers all request statuses and provides their description:
|1||Inquiring||Transient state of a request in case additional / corrected information is required.||Processing|
|2||Tiers Setup||Transient state of a request in case tier setup is required.||Processing/Draft|
|3||Pending||Transient state assigned to a request when product fulfillment is pending. Depending on Vendor actions, a request can be switched to the “Inquiring” state, to the “Approved” state, or to the “Failed” state in case of an error.||Processing|
|4||Approved||Terminal state assigned to a request in case a Vendor approved this request.||Active|
|5||Failed||Terminal state assigned to a request in case a Vendor rejected this request. It is recommended to reject a request only in case of unrecoverable errors.||Terminated|
|6||Draft||Optional transient state that can be used by a Provider to indicate temporal state while processing the order.||–|
Click on a request ID from the Fulfillment tab to access fulfillment request details screen.
The fulfillment request details screen provides general information like associated product, marketplace, subscription, and status.
Furthermore, this screen contains various data within the following tabs:
The fulfillment request details screen enables Vendors to process requests via the following buttons on the user interface:
Click on the Not Assigned field to assign the fulfillment request to a specific user account.
In case a request is approved and not assigned, the system will assign this fulfillment request automatically.