Commercial object types describe how a data product is priced, licensed, provided, and paid for. See Pricing, licensing, and data holders for the concepts. This group has four object types: Pricing plan, License, Data holder, and Payment gateway.
Pricing plan
A pricing plan describes the commercial terms of a data product: the price, the currency, and how consumers are billed.
This object type belongs to the Commercial group of the Data Product Standard application. It comes from the Open Data Product Specification (ODPS), which adds a commercial layer on top of a product’s technical description.
Use a pricing plan to make the cost of a product explicit before anyone requests access. Each plan sets a billing period, such as month or year, and a pricing model in the Pricing Unit field, such as recurring or pay_per_use. One data product can carry several plans at once.
For example, the “Customer 360” data product is offered on a recurring plan billed each month. The price is set in euros with VAT included. Consumers review the plan in the Data Market before requesting access.
Pricing plan attributes
| Attribute | Description |
|---|---|
| Plan Name | Name of the pricing plan. |
| Price | Base price. |
| Currency | Currency the price is expressed in. |
| Billing Duration | Billing period: instant, day, week, month, or year. |
| Pricing Unit | Pricing model, such as one_time_payment, pay_per_use, recurring, revenue_sharing, freemium, or open_data. |
| Valid From | Start of the plan’s validity. |
| Valid To | End of the plan’s validity. |
| VAT Included | Whether VAT is included in the price. |
| Notes | Rich-text notes about the plan. |
License
A license defines what a consumer is legally allowed to do with a data product. It states both the rights granted and the limits placed on them.
This object type belongs to the Commercial group of the Data Product Standard application. It comes from the Open Data Product Specification (ODPS), which pairs a product’s technical description with clear terms of use.
Use a license so the provider and the consumer agree on what is allowed before access is granted. A license records granted rights, such as display or distribution, along with restrictions, the geographical area, and the governing law. It also marks whether the terms are permanent and whether they are exclusive to one consumer.
For example, the “Customer 360” product carries a license that grants display and distribution rights within the EU. The license is non-exclusive. Consumers can read it in the Data Market before they commit to the product.
License attributes
| Attribute | Description |
|---|---|
| License Definition | Rich-text license terms. |
| Rights | Granted rights, such as reproduction, display, distribution, adaptation, reselling, transferring, or sublicensing. |
| Restrictions | Limits on how the consumer may use the data. |
| Geographical Area | Region the license applies to. |
| Permanent | Whether the license is permanent. |
| Exclusive | Whether the license is exclusive. |
| Notice Period | Notice period for termination, in days. |
| Applicable Laws | Governing law for the license. |
Data holder
A data holder is the organization that provides a data product to its consumers. It tells consumers who provides the product and how to reach them.
This object type belongs to the Commercial group of the Data Product Standard application. It comes from the Open Data Product Specification (ODPS), which names an accountable provider for every product.
Use a data holder to record who stands behind a product and how to reach them. It holds the registered legal name, a business identifier, a VAT ID, and a location (city and country). Each data product is provided by exactly one data holder.
For example, the “Customer 360” product is provided by “Contoso Ltd”. The data holder records Contoso’s legal name, its VAT ID, and a contact email for access questions.
Data holder attributes
| Attribute | Description |
|---|---|
| Legal Name | Registered legal name of the organization. |
| Business ID | Business registration identifier. |
| Contact Name | Name of the primary contact. |
| Contact email address. | |
| VAT ID | VAT registration number. |
| Website URL | Organization website. |
| City | City of the registered address. |
| Country | Country of the registered address. |
Payment gateway
A payment gateway is the external service that collects payment for a data product. It connects a priced product to the system that processes the payment.
This object type belongs to the Commercial group of the Data Product Standard application. It comes from the Open Data Product Specification (ODPS), which describes how a product is paid for.
Use a payment gateway when a product is sold and needs a system to collect payment. It records the provider — stripe, axio, checkout, or custom — along with a version and a specification reference. A product given away for free needs no payment gateway.
For example, the “Customer 360” product collects payment through a stripe gateway. The gateway records its version and a link to its configuration.
Payment gateway attributes
| Attribute | Description |
|---|---|
| Gateway Type | Provider: stripe, axio, checkout, or custom. |
| Gateway Version | Version of the gateway integration. |
| Gateway Reference URL | Link to the gateway configuration. |
| Gateway Specification | Configuration details of the gateway integration. |
For the concepts behind these object types, see Pricing, licensing, and data holders. For how they connect to other object types, see Data product object types and attributes.