Seller Modeling

Sellers are agents who sell goods in a marketplace. You can use their settings to do the following:

• Enter seller master data like identification and contact details.
• Configure settings for taxes and invoicing.
• Configure settings for the seller in all regions and countries or for specific regions and countries.

The same settings can be applied to either type using the JSON attached to the requests. For more information, see Settings Introduction.

You can create sellers in one of two ways:

• Virtual Sellers (Transaction API): You can use the requests that are sent to the Transactions API to send seller information in the same request as the transaction. These are known as virtual sellers. For more information, see Virtual Sellers.
• Non-Virtual Sellers (Sellers API): You can also use the Sellers API to create sellers in individual requests. You can use the generated seller_code to reference these sellers in the transactions. You also might use these to create a UI for seller creation, for example. The information is stored in a dedicated seller database. For more information, see Non-Virtual Sellers.

Restrictions

The following restrictions apply:

• You cannot use the Sellers API with virtual sellers. Non-virtual sellers can be accessed using the dedicated API. For more information, see Sellers Requests Reference (Sellers API).
• Non-virtual sellers' settings are stored in an immutable database where they can be easily accessed for troubleshooting or auditability. Virtual seller's details are stored with the transactions. It can be less easy to track changes over time.
• Virtual sellers cannot access the dashboard. Non-virtual sellers can access the dashboard. To do so, they need a UI user. For more information see Create Credentials.

Troubleshooting Transaction Size

There is a finite limit on the size of transactions. In rare circumstances, this may result in a general-persistence-error being returned. If this occurs, using non-virtual sellers should solve the issue.