Updates
Guides
Blog
Studios
Partners
Company

TWICE Studios > Shorts >

Dynamic Asset Attributes with Formulas: Calculate Custom Residual Value

Description

Transcript

Dynamic asset attributes in TWICE Commerce

TWICE Commerce lets you store any data you need per asset and create calculated attributes that derive values from other fields. Example: compute residual value from usage hours and purchase price, or standardize a recommended resale price from condition and lifecycle data.

  • Unlimited custom fields per serialized asset
  • Calculated attributes for residual value, pricing, and maintenance KPIs
  • Track usage hours for rentals and condition grades for resale
  • Flexible but referable fields usable across catalog, orders, and listings
  • Power rule-based workflows, availability checks, and pricing logic

Why this matters for recommerce

  • Rentals: log usage hours, auto-calculate residual value, schedule maintenance
  • Resale: normalize condition and compute recommended resale prices
  • Subscriptions: maintain lifecycle data and cost-to-serve per item

TWICE Commerce is the Recommerce OS for resale, rental, and subscription businesses. Run inventory and catalog management, order management, online payments with security deposits, CRM, and a white-label online store—while modeling granular asset data that keeps storefront experiences simple and clear.

Clip from TWICE Commerce 2.0: From Software to Operating System podcast episode.

Tuomo: You can store whatever data you want per asset, even doing things like calculated attributes where the value of the attribute—for example, residual value for a used item—is calculated based on other attributes like usage hours or purchase price. This kind of flexibility has been built into TWICE and it depends on you how you want to use it.

Tuomo: If you're a rental store, you might use them for usage hour tracking or residual value tracking. If you're a resale operator, you might utilize them for storing recommended resale prices based on condition and other factors.

Tuomo: The key thing here is that it's very dynamic. Even though it's unstructured in the sense that you can store whatever you want, it's still structured so that other parts of your system can refer to those fields very easily.