Model financial fields

Given the specificity of financial services, your product content type will include additional fields to store specific financial information, such as:

• Annual % Rate
• Interest Rate
• Taxonomy (Currencies)
• Taxonomy (Regional availability).

These fields are consistent across all financial services on the website and provide a good case for using reusable field schemas.

Since every product content type will share these financial fields, it makes sense to define their values through another collection of reusable field schemas, as you can see in the image below.

Find out more about reusable field schemas in the documentation.

Add content-type specific financial fields

In real-world scenarios, you’ll define several different reusable Product content types. You’ve already seen that you can define reusable field schemas that editors will use to store the same kind of data for each product. At the same time, your solution will contain fields that will be specific per product type. You can use standard content type fields to store the product-specific data.

For example, the Kbank demo project contains four products - Product - Loan, Product - Account, Product - Insurance, and Product - Card. They each contain dedicated fields that relate only to the specific type, such as the following:

Product - Card:

• Maximum borrow amount
• Card floor limit
• Minimum repayment amount (monthly)

Product - Loan:

• Maximum loan amount
• Loan duration
• Is the loan renegotiable?
• Loan grace period
• Loan required collateral

The following image overviews dedicated product-related fields of different reusable products in the Kbank demo site.