Kobo 101: Understanding Your PLM Platform
A complete guide to how Kobo organizes and manages your product development data — from concept through production.
Just like organizing files or a spreadsheet, KOBO uses a data model to keep everything connected and accessible. This guide helps you understand how that structure works so you can get the most out of your PLM system.
A data model is a structure that defines how information is stored and related. KOBO's model is purpose-built for fashion and apparel development, helping teams track every detail — from concept through production.
Overview
KOBO's data model is made up of four core building blocks. Understanding these helps you navigate the platform and set up your data correctly from the start.
What You Can Do with KOBO
KOBO is built for fashion and apparel teams who need to manage the full product development journey. Here's everything you can do in one place:
Lifecycle Status
Every style in KOBO has a Lifecycle Status that controls visibility and what actions are available. This is one of the most important fields to understand.
| Status | What It Means | Key Behavior |
|---|---|---|
| Draft | Style is being set up internally | Suppliers cannot see it. Not available for purchase orders. |
| Requested | Style has been sent to supplier | Supplier can now view and respond to the request. |
| Confirmed | Supplier has confirmed the style | Ready to proceed with sampling or production. |
| Shipped | Goods have been dispatched | Order is in transit from supplier. |
| Received | Goods have arrived | Delivery complete. Ready for inventory check-in. |
| Cancelled | Style has been cancelled | No longer active. Kept for historical reference. |
How Data is Organized
KOBO's data model is made up of four key parts: Objects, Attributes, Records, and Relationships. Think of it as a well-organized filing system designed specifically for fashion product development.
| Building Block | Description | Example |
|---|---|---|
| Object | A category of information (like a spreadsheet tab) | Styles, Components, Suppliers |
| Attribute | A field within an object (like a column header) | Style Code, Season, Lifecycle |
| Record | A single item (like one row) | "Classic Denim Jacket" as one Style |
| Relationship | How different objects connect | A Style has many Variants and SKUs |
Product Development Workflow
Every product in KOBO follows a structured journey from initial concept to final delivery. Understanding this workflow helps you know where each style is in its development.
Enter core details (name, code, season, category). Your style starts in Draft status — only visible internally.
Create color/material options. Add your Bill of Materials and measurement specs.
Send specs to your supplier. Create sample purchase orders.
Log feedback and notes. Approve or request revisions.
Approved styles move to Production status. Place bulk orders.
Receive goods, update quantities, and monitor stock by SKU.
Other Status Fields
Beyond Lifecycle Status, KOBO uses additional status fields to provide more detail about where a product is in development:
| Status Type | What It Tracks | Example Values |
|---|---|---|
| Design Status | Is the design work complete? | In Progress · Completed |
| Production Status | Is it being manufactured? | Sampling · Production |
| Supplier Stage | Communication with factory | Inquiry · Sampling · Costing · Prototyping · Production · Shipped · Delivered |
Active vs Inactive Styles
A style is Active when it's part of your current work — being developed, sampled, or in production. Inactive styles are archived, cancelled, or discontinued. They stay in the system for reference but don't clutter your daily workspace.
In Development · Sampling · In Production · Selling
Archived · Discontinued · Cancelled · Past Seasons
Variant vs Color
These two terms are often confused, but they serve different purposes:
Color — is a reusable library entry (e.g., "Navy Blue #1A2B3C") that you define once
Variant — is a specific color/material applied to a style (e.g., "Classic Tee — Navy Blue")
One Color entry can be used across multiple Variants and Styles. This keeps your color library consistent and easy to manage.
Version vs Variant
Another common point of confusion — here's the difference:
| Concept | What It Tracks | Example |
|---|---|---|
| Version | Sample stage in development | 1st Proto · Salesman Sample · Pre-Production Sample |
| Variant | Colourways or different fabrications | Indigo Denim · Black Denim · Light Wash |
Points of Measurement (POM)
POMs standardize how garments are measured. By defining exactly where and how to measure, every factory produces consistent results.
| Measurement | How to Measure | Tolerance |
|---|---|---|
| Chest Width | Measured 1" below armhole | ±0.5cm |
| Body Length | Measured from HPS to hem | ±0.5cm |
| Sleeve Length | Shoulder seam to cuff | ±0.3cm |
Tags & Filtering
Tags let you group and filter styles in flexible ways — beyond the standard fields. Use them to organize your work however makes sense for your team.
Bestsellers — track your top performers
Sustainable — flag eco-friendly products
Limited Edition — mark special releases
Reorder — identify styles for restocking
Trade Show — group styles for specific events
SKUs
A SKU (Stock Keeping Unit) identifies a specific size-color combination. They're used for barcodes, inventory tracking, and warehouse operations.
Compliance Fields
These fields are required for shipping and customs. Keep them updated to avoid delays at the border.
| Field | What It Is | Example |
|---|---|---|
| COO | Country of Origin — where it's made | Made in Vietnam |
| HS Code | Customs classification code | 6203.42.40 (Men's Cotton Jacket) |
| MID Code | Factory identifier | VN-001 |
Styles
Styles are the heart of your PLM. Each style represents one product design moving through development.
| Field | Description |
|---|---|
| Style Code | Unique identifier (e.g., GJK-001) |
| Style Name | Descriptive product name |
| Season | Collection or release (e.g., Spring 2025) |
| Category | Product type (outerwear, tops, etc.) |
| Lifecycle Status | Draft · Requested · Confirmed · Shipped · Received · Cancelled |
| Supplier | Assigned manufacturer |
Variants
A Variant is a color or material version of a style. One style can have multiple variants, each with its own Bill of Materials, color specs, and SKUs.
Components
Components are your building blocks — fabrics, trims, labels, zippers, buttons, and more. Build a library of components to reuse across styles.
| Field | Description |
|---|---|
| Reference | Component identifier |
| Color | Color option (e.g., Navy #001) |
| Supplier | Where you source it from |
| Category | Type (fabric, trim, label, etc.) |
| Unit Cost | Cost per unit |
Purchase Orders
Purchase Orders (POs) track orders placed with your suppliers — for samples or production.
| Field | Description |
|---|---|
| PO Number | Unique identifier (e.g., PO-045) |
| Supplier | Factory or partner |
| Status | Draft, Confirmed, or Cancelled |
| Payment Status | Unpaid, Partially Paid, Paid |
| Delivery Date | Expected arrival |
| Line Items | Styles and quantities ordered |
Best Practices
Quick Reference
| Category | Common Values |
|---|---|
| Lifecycle Status | Draft · Requested · Confirmed · Shipped · Received · Cancelled |
| Design Status | In Progress · Completed |
| Production Status | Sampling · Production |
| Supplier Stage | Inquiry · Sampling · Costing · Patternmaking · Prototyping · Production · Shipped · Delivered |
| Purchase Order Status | Draft · Confirmed · Cancelled |
| Payment Status | Unpaid · Partially Paid · Paid |
Glossary
Getting Help
Help Center — visit for detailed guides
Contact Support — for technical questions
Search — find styles, components, or orders quickly
Understanding your PLM's data model is the foundation for efficient product development. Once you know how the pieces fit together, everything from sample tracking to production planning becomes intuitive.
Joe Lauder — Founder, KōbōRelated Articles
Ready to streamline your product development?
Kobo connects your styles, materials, suppliers, and production data in one system — so your team always works from a single source of truth.
Book a Discovery Call