In order to process asset requests of any type, vendors require information not only relative to the specific product but also about the buyer, supply chain, environment where that request has been originated, etc.
Some of this information may be considered generic, in other words, most of the Vendors require it and due to it, Connect provides it on each request. Additionally, vendors may define additional parameters that will be exclusive for a concrete product.
In this article we will be describing the generic information provided to vendors in a generic manner, this information will be available on fulfillment user interface and also available in the Assets API.
For additional parameters that vendor can define, there is an article for reference: Product Parameters
This article assumes that you are familiar with the assets module in Connect.
Each request is assigned one of the following types and workflow:
With each type summarized in the following table:
|#||Type||Icon||Description||Requests x Asset|
|1||Purchase||Initial purchase of the items that forms the asset object.||1|
|2||Change||Change of quantities of the items in the asset||0 … many|
|3||Vendor Billing||Billing of the item to the next period calculated by Connect on behalf of the Vendor||0 … many|
|4||Provider Billing||Billing of the item to the next period calculated by the systems of Provider||0 … many|
|5||Suspend||Switch of the asset into the administrative hold state||0 … many|
|6||Resume||Resume of the asset from the administrative hold state||0 … many|
|7||Cancel||Cancellation of the asset and its items||1|
Note that only Purchase request currently supports the inquiry status.
Where each status represents a particular stage in the fulfillment process:
Each request represents the following key data attributes and actions, as schematically summarized in the following screenshot:
Each request sent to vendor will contain:
The supplied contact information for either customer or any of the tiers will contain:
|Company name||No||Cool Enterprises||Company Name of the buyer of the asset if this defined as a Business type account on the commerce system, in case that is a personal account typically will contain the first name and last name of the buyer|
|Account ID||No||1000218||Unique account id that identifies the customer on the commerce system|
Postal Address information
|Street address||No||10 Hordon Street||Main address defined on the account on the commerce system|
|Extended address||Yes||Door 2A||This field may contain additional information about the address, the value may be blank|
|Locality||No||Wrights||Locality or city|
|Region||No||California||Region / State / Province of the account|
|Postal code||No||12345||Postal Code of the account|
|Country name||No||us||2 digit code of the country related with the account as defined in ISO 3166-1 alpha-2 |
Technical Contact information
|Given name||No||John||First name of the technical contact of the account|
|Family name||No||Doe||Family name or surname of the technical contact|
|Email||Nofirstname.lastname@example.org||Email address provided by commerce system relative to the technical contact|
|Telephone||No||+11234567890||Phone number where technical contact can be reached|
Provider is the owner of the commerce system that over the supply chain sold the asset to the end customer. Provider information is known by vendors due fact that they signed an agreement with them to distribute vendor’s product. Since vendors may have relation with more than one provider, minimal information is delivered on each individual request:
|ID||PA-425-033||Unique identifier of provider, this identifier is generated by Connect platform|
|Name||ServicePro||Name of provider account as defined in Connect platform|
|Hub||ServicePro||Hub name that represents the system that generated the request|
|Hub ID||HB-0309-9389||Unique identifier that represents such commerce system on the Connect platform|
Each commerce system will have at least a connection for a given product, vendors may identify this value with a contract between provider and them and from programmatically standpoint of view, a set of credentials to be used to complete the request on vendor’s systems. Each connection will be identified with:
|ID||CT-1234-5634||Unique identifier of the connection|
|Mode||Prod||Connection is identified with a type in order to understand if this request is from a real customer (production), a test customer or coming from a preview when vendors defines their product on vendor portal|
Each asset is identified in unique manner in Connect in order to let vendors have a mapping between all systems.
|Name||Product X Basic||Name that seller has set for assets that contains the product (and items) requested in the request|
|ID||AS-318-064-698-0||Unique identifier of the asset in the Connect platform, this identifier is unique globally|
|External ID||1000628||Unique identifier of the asset on the concrete HUB that originated the request, this identifier may not be unique in case that vendor has relation with more than one provider, or provider has more than one hub|
On each single request, apart from the generic information and the parameters defined by vendor for a concrete product, we can also find: