This article will introduce what product specification templates are, as well as the creation process and usage scenarios of specification templates.
Terms and Explanations
|
Product Specification Template | is a reusable configuration tool for Partners to manage product specifications & sales modules. Its core value lies in: Specification standardization serves as a unified interface for managing specifications, simplifying the product listing process. Specifications are reusable, support referencing by multiple products, and reduce redundant configuration work. Specification flexibility allows modifications to propagate to all products after changes, enhancing modification efficiency. Addresses complex needs such as free selection of multiple sales items, combined ordering, consolidated payment, and simultaneous deployment. The template includes: specifications, sales modules. | - |
Specifications | Specifications are used to differentiate product variations, serving as the "selectable options" on product detail pages and acting as a "bridge" between products and SKUs. Different specification combinations ultimately form specific purchasable units (that is, SKUs). Specifications need to be associated with products. | Edition (Standard Edition, Premium Edition) Number of Seats (100 seats, 500 seats) |
Sales Module | A standalone purchasable module (or sub-product) derived from the same product, typically representing "feature groups" or "service components" that constitute the complete product. Sales Module needs to be associated with products. | - |
The relationship between the product specification template, product, and installation package is as follows:
When products are listed and installation packages are created, it is necessary to associate them with the corresponding product specification templates.
Template Use Cases
When a product is created, each product must be associated with a product specification template.
Please confirm what information needs to be filled in the template based on the product's sales strategy.
Standalone Sales Module Scenario
Only need to define the specification, no need to define the Sales Module.
Because the product specification template has already defined the product specifications, therefore when a product is created, it is necessary to associate the template where the specifications are located. After association, there is no need to fill in the specifications again; simply select the specifications applicable to this product by checking them (multiple selections allowed).
Multiple Sales Items Scenario
Need to define specifications and Sales Module.
Since the product specification template has already defined the specifications and Sales Modules, therefore when a product is created, it is necessary to associate the template containing the specifications and Sales Modules. After association, there is no need to fill in the specifications and Sales Modules here; simply select the specifications and Sales Modules applicable to this product (multiple selections allowed for both).
Note:
A product can only be associated with one template. Ensure that the specifications and Sales Module are in the same template.
Creating a Template
Template Information
Template name: Must not exceed 20 characters; supports Chinese/English characters and numbers. The template name is not visible to customers.
Template description: Must not exceed 500 characters; supports Chinese/English characters, numbers, and special characters. The template description is not visible to customers.
The product specification template needs to be associated when the product is created.
Specification information
Specification information refers to the product attributes defined by partners based on customers' purchasing needs. Customers can select specific specifications set by partners on the purchase page.
Specification types are divided into two categories, as shown in the table below:
|
enum | Refers to specifications that are finite and quantifiable, suitable for scenarios with limited specification values. For example: product editions such as Basic Edition, Advanced Edition, and Premium Edition. | For example: the specification is "Edition", and the specification values are "Basic Edition", "Advanced Edition". | |
numeric range type | Refers to specifications with a large range that cannot be exhaustively enumerated, suitable for unquantifiable specification values. For example: number of users ranging from 1 to 100. | Partners need to fill in the minimum value, maximum value, and step size. Integers within the range of 1 to 999,999 are supported. Step size refers to the spacing between purchasable quantities. For example: if the minimum quantity is 1 and the step size is 5, customers can only purchase quantities such as 1, 6, 11, and so on. | The customer can enter the quantity to purchase. |
Note:
Add up to 20 specifications and 20 specification values, please ensure there is at least one enumeration-type specification.
Specifications created in all templates can be selected during the product creation phase.
Specification parameters and specification value parameters will be used in the installation package's License.
After a customer orders the software, the system will automatically issue a License containing this value. The process verification of the software License must recognize this value.
Note:
Specification parameters and specification value parameters filling suggestions should be coordinated with the R&D team.
Sales Module (Optional)
Sales module is optional, please partners evaluate and add based on the actual sales scenario of the software.
What scenarios are suitable for adding a Sales Module?
When a product involves multiple sub-products that need to be sold as a bundle, multiple sales modules can be added. Each module represents one sub-product.
For example: The partner's software is a marketing platform that offers multiple sub-products such as data analytics, private domain marketing, and task distribution. These sub-products can be sold independently or as a bundle.
Thus, partners can add "Data Analytics", "Private Domain Marketing", and "Task Distribution" as multiple sales modules. When placing orders, customers can freely select and combine them for payment based on their needs, and complete simultaneous deployment.
Module name: Must not exceed 20 characters, supports Chinese/English characters and numbers; visible to customers.
Module identifier: Must not exceed 50 characters, supports English only; not visible to customers.
Editing a Template
Edit Template Name and Template Description
Template names and descriptions are not displayed to customers, so after editing is performed, saving will take effect immediately.
Edit Specification Information
Once a specification is associated with a product, the specification type cannot be modified, specifications cannot be deleted, and specification values cannot be removed. Only adjustments to specification names, spec parameters, specification value names, and specification value parameters are permitted.
To modify any specification, first unlink it from the product.
Note:
After modification of specification information is made, the changes do not take effect immediately in products by default. The system will notify you which specific products reference this specification. Be sure to go to the product page to synchronize the latest specification information and submit for review.
If the specification parameters or specification value parameters are modified, you must synchronize these changes in the installation package and submit for review.
Edit Module Information
Once a module is associated with a product, its name and identifier cannot be modified.
To modify any information, first unlink the module from the product.
Note:
After modifying module information, the changes do not take effect immediately in products by default. The system will notify you which specific products reference this module. Be sure to go to the product page to synchronize the latest module information and submit for review.
If the module parameters are modified, you must synchronize the changes in the installation package and submit for review.