O2VEND SKU Rule Configuration for Advanced Inventory Control

The SKU Rule module in the O2VEND Back Office enables structured and automated generation of Stock Keeping Units (SKUs) using configurable logic. It ensures consistency, traceability, and scalability across large product catalogs, including those with multiple categories, brands, and suppliers.

This document serves as a technical reference for configuring SKU Rules using standardized tokens and structured templates available in the Create SKU Rule interface.

Through structured templates, rolling numbers, and intelligent token usage, the SKU Rule module provides a reliable framework for scalable and automated SKU management, supporting enterprise-grade inventory control and improved operational efficiency within O2VEND environments.

System Navigation

Access the SKU Rule configuration module through the following path:

O2VEND Back Office → Catalog → SKU Rule

This navigation opens the configuration panel where SKU templates and rules are defined for generating SKUs for both base products and their variations.

Purpose of SKU Rules

SKU Rules operate as a governing framework for:

  • Standardized product identification
  • Automated SKU generation
  • Structured handling of product variations
  • Category, brand, and supplier traceability
  • Enhanced inventory reporting accuracy

A well-defined SKU structure eliminates duplication, improves search efficiency, and strengthens integration with external systems such as ERP and POS platforms.

SKU Template Composition

SKU generation is based on a combination of static values and dynamic tokens. These tokens extract attribute data and construct a unified SKU string at runtime.

Example Template Structure

<O:1> <A:1> <O:1>

This structure ensures that every generated SKU is:

  • Unique
  • Systematically ordered
  • Human-readable
  • Logically segmented

Token Reference

Date & Time Tokens

Used to embed formatted date values within SKUs:

  • DD – Day (01–31)
  • MM – Month (01–12)
  • MMM – Month abbreviation (Jan, Feb, Apr)
  • YYYY – Full year (2025)
  • YY – Short year (25)

Example Output:
PRD-APR-2025-0012

Dynamic Attribute Tokens

Token Description
<CategoryCode> Code assigned to the product category
<BrandCode> Code representing the brand
<SupplierCode> Supplier identifier
<NormalizedName> System-formatted and cleaned product name
<RollingNumber> Sequential numeric counter
<A:1> Alphabetical sequence increment
<O:1> Ordered or fixed identifier prefix

Create SKU Rule – Field-Level Explanation

This section explains each configurable field in the Create SKU Rule interface.

1. Template

Defines the core format and structure of the SKU.

Accepts:

  • Static text (fixed characters)
  • Dynamic tokens

Example Syntax: <O:1>

Purpose:

  • Controls SKU structure standardization
  • Determines component placement
  • Enables dynamic token replacement

2. Category

Optional selector to limit rule application to a specific category.

  • Selected → Rule applies only to that category
  • Blank → Rule applies globally

Purpose:

  • Category-based SKU assignment
  • Differentiated structure by product type

3. Brand

Defines the brand scope of the SKU rule.

  • Automatically injects <BrandCode> when defined in the template.

Purpose:

  • Brand-level identification
  • Structured inventory classification

4. Supplier

Links SKU rule to a specific supplier.

Essential for environments with multiple vendors.

Purpose:

  • Supplier-level SKU segregation
  • Prevents overlap across vendors

Rolling Number Configuration

Ensures SKU uniqueness through sequential numbering logic.

5. Number

Defines the starting value of the rolling sequence.

Example: Total Length = 5

Output: 00001, 00002, 00003

7. Padding Character

Defines the character used to fill unused digits.

Common:

  • 0 (recommended)
  • 1

Example:
Padding Character = 0 → Output: 00012

8. Padding Position (0-left / 1-right)

Defines where the padding is applied.

  • 0 = Left Padding → 00025
  • 1 = Right Padding → 25000

9. Use New Number For Variation

Controls sequence behavior for product variations.

  • Enabled → Each variation gets a unique rolling number
  • Disabled → Variations share the parent SKU base

Purpose:

  • Prevents parent-child SKU duplication
  • Maintains variation-level uniqueness

Field Interaction Summary

Field Functional Role
Template Defines SKU structure
Category Category-level restriction
Brand Brand scope application
Supplier Supplier-based segmentation
Number Rolling number starting point
Total Length Digit consistency control
Padding Character Number formatting filler
Padding Position Direction of numeric padding
Use New Number For Variation Variation SKU uniqueness logic

Practical Configuration Example

Configuration

  • Template: <CategoryCode>-<BrandCode>-<RollingNumber>
  • Number: 1
  • Total Length: 4
  • Padding Character: 0
  • Padding Position: 0

Output

ELEC-SAM-0001 ELEC-SAM-0002 ELEC-SAM-0003

Advanced SKU Pattern Examples

Pattern 1 – Standard

CAT-BRD-SUP-NAME-0001

Pattern 2 – Date-Integrated

--MMM-YYYY-

Pattern 3 – Enterprise Format

<O:1>

  • Maintain standardized codes for categories and brands
  • Avoid excessive SKU length
  • Use fixed-length rolling numbers
  • Apply NormalizedName for contextual clarity
  • Use alphabetic tokens only when required
  • Ensure consistency across all SKU rules

Operational Flow

  1. System identifies the assigned SKU Rule
  2. Tokens are dynamically replaced with real-time values
  3. Rolling number increments automatically
  4. SKU is generated and stored

This workflow guarantees accuracy, consistency, and scalability.

Business Impact

Optimized SKU Rule configuration results in:

  • Controlled inventory management
  • Reduced manual intervention
  • Improved reporting accuracy
  • Faster warehouse processing
  • Enhanced system interoperability

For more insights on inventory management, check out this blog:
How to Design Your SKU Based on Various Parameters for Easy Inventory Management

Questions and support

Additional assistance required or unresolved queries?

This documentation covers the core functionality of the O2VEND Back Office platform. Technical assistance is provided through the official O2VEND Support Desk, and most platform-related queries are already addressed within the knowledge base.

To extend For advanced support or custom implementation, connect with an authorised expert O2VEND Support Desk .

If the required information is not available, feedback can be provided using the buttons below.