Introduction
SKU data allows manufacturers to define variant-specific information for each product they make. While most data is inherited from the product level, SKUs can override fields where variants differ. This guide explains how SKU data works and how it fits into managing product information in Scannable.
Product vs SKU Data
Inherited Data
All SKUs within a Product will inherit any data entered at the Product level.
Reminder: Data fields are determined by the product category (e.g., ropes, helmets, harnesses).
SKU-Specific Data
You only need to set data at the SKU level when a variant differs from the rest.
Examples:
Colour
Length
Presence of a splice or other assembly components
This allows you to maintain a clean product template, while each SKU reflects its unique attributes.
Composite and Assembly SKUs
Some SKUs are made up of multiple parts—for example, a rope length plus a splice.
We refer to these data models as:
Rope Lengths
Assemblies
Scannable displays these component parts when viewing SKU data, making it clear how each variant is constructed.
Importing Product & SKU Data
When onboarding a manufacturer, Scannable imports their product and variant information. The source may be:
A direct export from the manufacturer
A Product Information Management system (PIM/PIMs)
Product catalogues, price lists, or publicly available data
Manual uploads from the manufacturer
We consider our Product/SKUs module a PPE Specific PIM. Today, this product data can be used for:
Publishing your products to our ‘Global Equipment Database’
Connecting the product data to your serial numbers & NFC tags, for Smart PPE™ production
Sending to label printers & laser markers in production
Printing packaging
It is our intention to let this PPE-specific PIM also:
Integrate with e-commerce sites for populating web shops
Integrate with e-commerce sites for distributing your range to resellers
From Products to Items (Serialization)
Products and SKUs act as ‘templates’.
Think of Scannable as a ‘serial number engine’ that sits on top of your ERP.
When you raise a PO with your suppliers or an internal works order/batch, Scannable can be used to create a unique serial number for each manufactured item.
Examples:
100 ropes produced in a batch
Each rope receives its own serial number
Scannable also creates a ‘digital serial number’ which is a unique web address (URL) alongside each ‘analogue’ serial number
Each item/serial number can be linked to one or many NFC tags.
You may hear these referred to as:
Serialised Items
Serials
Items or Inventory items (once they’re in customer inventories)
Serial Number Formats
Manufacturers can define their own serial number formats using components such as:
A prefix
Date of manufacture
An incrementing number to ensure uniqueness
These formats control how serials are generated when creating items.