Custom Fields let you extend your product data by attaching additional, structured information to each Product Definition in your account. A Product Definition in our system represents an item - similar to a SKU - and typically includes basic details like the product name and description. However, many businesses need to track more specific attributes to support workflows, reporting, or integration with other systems. That’s where Custom Fields come in.
With Custom Fields, you can define your own data points - such as size, certification status, or a product URL - and associate them with your Product Definitions. This allows for greater flexibility and customization in how you setup and manage your data within RFIDLinked.
Data Types
Custom Fields support four data types:
-
Text Free-form text, up to 128 characters including alpha-numeric characters and special characters.
-
Number Any numeric value, including decimals.
-
URL Valid web addresses, beginning with
http://orhttps://. -
Boolean Represents True/false values.
Here are some common scenarios for using each Custom Field type:
Text
Use this when you need to store short descriptive or identifier-based data.
-
Example:
"Allergen Info"for a food product ("Contains peanuts") -
Example:
"Material Type"for apparel ("100% Cotton")
Number
Best suited for measurable values, quantities, or identifiers that must be numeric.
-
Example:
"Size (ml)"for a hot sauce bottle (150) -
Example:
"Shelf Life (days)"for perishable goods (365) - Example
"Price"for perishable goods (1.99)
URL
Use when you want to link to external resources such as documentation, images, or product pages.
-
Example:
"Spec Sheet URL"for an electronics item (https://example.com/specs) -
Example:
"Marketing Page"for a consumer product (https://example.com/hotsauce)
Boolean
Ideal for simple yes/no flags or status indicators.
-
Example:
"Is Organic"for produce items (trueorfalse) -
Example:
"Discontinued"to mark inactive products (trueif no longer sold)
Example Use Case
Suppose you're selling a range of hot sauces. Each variation, say, a
150ml bottle and a 250ml bottle, can be defined as separate Product
Definitions. To store the bottle size, you can create a Number-type custom field called "Size (ml)"
and link it to each product. This keeps your product data consistent
and easily accessible throughout the application, whether for scanning,
printing, or auditing.
Custom Fields give you the flexibility to track exactly what you need, tailored to your unique inventory or business logic.