Updates
Guides
Blog
Studios
Partners
Company

TWICE Studios > Shorts >

Serialized and Aggregated Inventory Stock Items in TWICE Commerce 2.0

Description

Transcript

Mastering Inventory Structure: Serialized vs. Aggregated

Effective inventory management is the backbone of any successful rental or resale business. In TWICE Commerce 2.0, understanding how to structure your inventory rows—whether as single, serialized items or aggregated quantities—can significantly impact your operational efficiency and data tracking.

When to Use Serialized Inventory

For high-value assets, granular tracking is essential. In this video, we use the example of a car. When renting out vehicles, you need to track specific metrics like mileage, maintenance history, and individual usage for every single unit. TWICE allows you to assign unique stock codes to each row with a quantity of one, ensuring every asset is accounted for individually.

When to Use Aggregated Inventory

Conversely, for lower-value, high-volume items like ski poles or accessories, tracking each individual unit's history may not be necessary. Instead, you can utilize aggregated inventory records. By setting a quantity greater than one on a single row, you can track income, expenses, and availability on a category level without the administrative burden of managing thousands of unique IDs.

Key Takeaways:

  • Serialized Records: Best for high-value assets requiring individual history (e.g., electronics, vehicles).
  • Aggregated Records: Ideal for accessories and consumables where general availability matters more than specific unit tracking.
  • Flexibility: TWICE Commerce supports both methods within the same system to optimize your workflow.

Build a circular business that scales with TWICE Commerce—the Recommerce OS designed for the future of rental and resale.

Clip from podcast episode.

Tuomo: Let's imagine you have your inventory open in TWICE 2.0. In that table, every row can have a quantity and every row can have one or many unique stock codes that are used when reading barcodes and so on—that kind of references that inventory record.

The only difference is that if that row has a quantity above one, you kind of aggregate all of the information under that one inventory record. So for something like a car, you probably want to separate the actual mileage between two cars and the usage because they're such valuable assets.

Now, if you go to a category like, I don't know, skiing poles, where it's not necessarily as important to know which one of these poles actually gathered the usage, but you rather want to track income and expenses on an aggregated level, then you might have a quantity for that inventory record level.