Deploying the Service
Read this description of how a typical deployment is implemented.
This topic will describe a simplified version of a typical deployment. We are not considering further integrations with Vertex O Series (Cloud) (OSC) Connectors, for example.
It assumes that the customer is new to both Vertex for Marketplaces and OSC.
Note
It is the customers' responsibility to implement the tax outcomes that they deem suitable for their business. This is done after consultation with tax professionals. The settings that impact taxability need to be made with the supervision of tax professionals.
Implementation Steps
A typical deployment consists of the steps in the following diagram. These are performed by the Integration Engineer (IE), the customer and the customer's chosen tax advisors and experts. Before they begin, these parties assess their needs and agree on a planned deployment. The settings that impact taxability need to be made with the supervision of the tax experts.

Implementation Steps
The steps are:
- A sandbox instance of Vertex for Marketplaces is deployed.
- OSC is deployed. See Vertex O Series (Cloud) Integration.
- Marketplace-level settings can be decided. Countries are defined. These functions are integrated with the customers applications using the Marketplace API. See Marketplace Settings Overview. User and roles are created. See Users and Roles.
- Sellers can be modelled. If using non-virtual sellers, the seller records and settings are created. See Seller Settings Overview.
- Next, the Transaction API is used to integrate with the customers checkouts and other applications. See Transaction Modeling.
- The integration is tested using the sandbox.
- The integration is moved to production and it goes live.
Updated 16 days ago