Understanding Trustana data

A key step prior to uploading and distributing your data is normalising it in a database.

Updated over a week ago

Data administrators must understand Trustana Product data structure or schema to import, maintain and distribute your product information.

Overview of Account Objects

Product

What is a product?

Generally understood as a Stock-Keepig Unit (SKU), it constitutes a physical article or substance that is manufactured or refined for sale.

In Trustana, each product has a unique identifier TRSKU_ID, which is an internal system-generated identifier. It is created every time a new product is created on our platform, either by single creation or batch creation.

Merchants are also able to assign a SKU_ID based on their own naming convention which may be used by multiple systems, such as a warehouse system, accounting system, point of sale system, order management system, and third-party e-commerce platforms.

Attribute

An attribute is a quality or feature regarded as a characteristic or inherent part of someone or something. In the case of products, an attribute is used to describe one or more features to further define their use.

The objective of the system is to manage attributes in an organised way in a database, following a validated data type (number, text, date-time, boolean).

Examples of attributes: Name, Description, Price, Recommended Retail price, Barcode, Color, Storage capacity, Screen size, Resolution, Flavour, etc.

Attribute schema

Products of different categories require different attributes to store and highlight their features.

The data relevant to a Laptop, for example, is completely different to the data needed to present a bag of potato chips. Under the system, however, both are products with their unique SKUs.


The attributes used for one product to the other will have a common ground (such as name, description, price, barcode, SKU) but they also will require category-specific attributes.

Example of Computing attributes

Screen Size, Warranty time, Hard drive type, Storage Capacity, RAM, Graphics cards, Processor, Operating System, etc.

Example Food and beverage attributes

Flavour, Shelf Life, Net Weight, Packaging type, Minimum Order Quantity, Ingredients, etc.

Attribute data type

The data stored for each attribute will use different logical formats.

For example:

  • Expiry Date - Date format YYYY/MM/DD: 2024/05/25

  • Product name - Text format: Pork Dumplings

  • Shelf Life - Integer Number (in months): 18

  • Description - Text format: A delicious food item....

  • Barcode - Integer Number format: 12345678910

  • Flavour - Dropdown list: Spicy, Natural, Onion & Garlic

  • Screen size - Text format: 13 inches

You may want to review Product Schema: Common Attributes.


Custom Attributes

Trustana understands that our customers require flexibility to create and maintain attributes specific to their use cases.

Trustana's robust database allows our customers to create custom attributes of their choice in the following data types:

  • Text

  • Number

  • Date

  • Date-time

  • Barcode

  • Dropdown (specifying values)

  • Currency (specifying currency code)

Variants

Manufacturers often make several versions of the same product to address different user needs.

A variant is a form or version of something that differs in some respect from other forms of the same thing or from a standard.

  • In Food and beverage products, the most common variants are flavour or packaging size.

    The same Coca Cola Zero soft drink may come in a 500ml or 1L bottle. They have the same product, but due to their presentation size, they have different SKU numbers and different prices. Their purpose is also different, a 500ml is more convenient for one person only, while a 1L bottle may be best to share with more people.

  • In Fashion, the same dress can come in different colors or materials.

  • In Beauty, the same product can come in different colors to match different skin tones.

  • In Computing, the same laptop model (MacBook Air) can come with different CPU and GPU units.

Master Product and Locale


Trustana holds Product Information at the master level, but it allows users to have an loosely dependant local version of the same information.

It is related to the master product in a parent-child relationship, but it is not updated every time the master data is updated.

It is meant to hold a version of the master data either translated to another language or converted in terms of currency and or unit of measurement.

Users can select the locale they want to translate their product information and save it as a combination of Region and Language, using ISO 639-1:2002 for languages and ISO 3166 for country codes.

Read more about AI Translations here.

Currency

A currency is applied to a "Currency" attribute type, often used for Price or Cost type of data.

Example of use cases:

  • Unit Cost

  • Unit Price

  • Recommended Retail Price

  • Wholesale Price

  • Promotional Price

The numeric value will be followed by the preconfigured 3-digit currency code.

Available currencies are:

  • USD - United States Dollar

  • SGD - Singapore Dollar

  • MYR - Malaysian Ringgit

  • THB - Thai Baht

  • CNY - Chinese Yuan

  • JPY - Japanese Yen

  • KRW - Korean Won

  • EUR - Euro

Unit of Measurement

This is a suffix used to specify the metric represented by the numeric prefix.

For example, 8 litres and 8 millilitres are not the same. They are both describing volume on a specific product, yet the measurement is greatly different even if the numerator is 8 in both cases.

Supported Units of Measurement (UOM):

  • KG - Kilogram (Metric measurement system)

  • G - Gram (Metric measurement system)

  • LB - Pounds (Imperial measurement system)

  • OZ - Ounce

Trustana does not convert numerators when changing the Unit of Measurement.

Asset Management

  • An asset can represent an image or a video or a file (i.e PNG)

  • An asset is a structure with asset attributes like filename and URL.

  • An asset is associated with a single product.

Did this answer your question?