Key Concepts

Understanding nomenclature in Gocious

At Gocious we work to make features and concepts simple so you can focus on making better decisions. We have tried to make things as simple to understand as possible. Below are a few terms that you will see us use throughout the product.

Attributes and specifications

Attributes are properties that define the characteristics of a feature. You can assign an attribute to a feature family and every feature in that feature family will include that attribute as part of their definition. Attributes have different types such as a unit of measure, currency or text. Once part of a feature you can capture values against them to create feature specification list.

Specifications are attributes and their values.

Example:, if one of your Feature Families is "Color" an Attribute could be named "Paint Color”, the Specification against a Feature would be “Paint Color = Red”

Buildable combinations

Buildable combinations are the total number of valid product variants for each product in the product line. A valid product variant is the one that contains a complete set of features (one from each feature family in the product line) that can be available together on that product without violating any relationships.

 For example; if the Product Line contains two Feature Families each with Two Features with no restrictions then the number of buildable combinations will be four (two x two).

Features and feature families

Feature is an aspect of your product that customers value. Features are configured together to define your products. A Feature could be a specific tangible feature (for bicycles it could be “Knobby Off-road Tire”) or it could be a characteristic that your customers can relate to such as a Model Name (e.g. “Men’s Mountain Pro”). Features with similar characteristics that can be configured as mutually exclusive standard or optional on a product are grouped inside of a Feature Family.

Example: Features “Knobby Off-road Tire” and “Knobby Road Tire” could be Features of Feature Family of “Tires”. A product can be configured to have both as options but each product variant can have either Knobby Off-Road Tire or Knobby Road Tire but not both at the same time.

Note: To build a Product variant you need one Feature from every  Feature Family in the product line to be selected You can explicitly define a feature in the feature family that represents absence of selection such as “none” or “without tire” if you choose to provide the option for the product to be configured with features of that family being absent on the product. This is to help increase the accuracy of the product configuration model and to clearly communicate the absence of a feature as a requirement.


Packages can be created by you to bundle Features. The Package can then be made available similar to features on Products to pre-determine content for your customers to pick from.

Like Features inside a Feature Family Packages can be bundled in Families. Packages inside the same Package Family are mutually exclusive on a Product. If you want your Packages to not be mutually exclusive on your products then simply add them in separate Package Families.

When creating a package there are a few things that Gocious will do for you in the background.

  1. When you create a Package, Gocious will automatically create a ‘Without Package’. This less package condition will be automatically added to Products wherever you don’t make the Package you created standard fitment.
  2. When you add a Feature to a Package and make it available (either Standard or Optional) then Gocious will make every other Feature from the same Family that is not added to your Package unavailable.
  3. If you add a Feature to a Package to make it explicitly unavailable with the Package then Gocious will not change any of the other Features from that Feature Families pre-existing availability.

Products, product variants and product lines

A Product is something that is generally intended for sale to a customer. It is defined by the content of the features and packages available on it. It can consist of Standard Features, Optional Features and Packages

  • Standard Features will automatically be placed on the Product unless a customer chooses to replace it with an Optional Feature from the same Feature Family
  • Optional Features are choices offered to customers so that they may configure their own variants of the Product
  • Packages may be either Standard or Optional fitment to a Product and are typically used to bundle Features that you wish to offer to the customer to reduce the complexity of the Products made available

A Product Variant is a single unique buildable combination of Features (including Packages) that can be built based on the configuration of a Product

A Product Line is the list of all Products defined within the space. Usually the product line includes products that are related together against similar characteristics customers can identify.

Product or variant content

Features that makeup the product or a variant collectively are called content for that product or variant.

Relationships and Availability

Relationships determine the Availability of Features. Relationships are considered by the system in three simple manners. You can create Relationships directly to Products, between Features (from separate Feature Families) and when creating Packages.

When assessing what relationships to apply the system will apply a last relationship wins philosophy. This means the last relationship created will overwrite any previous relationships that came before.

The system will also apply the relationships in a hierarchy. For any given Feature, Feature to Product relationships will always be applied first. Any Feature to Feature relationships will then be applied over the top of the Feature to Product relationships. If the availability of a feature in a feature family are dependent on features in two or more feature families then in case of a conflict the last relationship on the list will win. Finally, any Feature to Package relationships will be applied last.

Variant and product score

Variant and product scores help determine how far your product is from your objective targets. It’s a 0 based 10 point score (0-10). The higher the score the closer the content of your product or variant is to meeting or exceeding your target values.

Each variant has a weighted score that is calculated by totaling each participating specification values of that variant, measuring its relative distance from the high or low targets, then calculating the weighted average of the relative distances.  If a feature does not have the specification or has a specification that its attribute is not a target for scoring, it will not be factored in the score.

The Product Score is the average scores of all the valid variants that the product can be configured as.

The Weighting of the target specifications are defaulted to 5. This value can be adjusted by you to any value between 1 and 10 for each Scoring Attribute and Product in the Product Line.