Base types and polymorphic types
Group related types under a base type so they share one spine of fields, then give each type the extra fields only it needs. A fabric and a trim can differ completely and still report together.
In the APIModel your data
Describe the things your business makes before you describe what happens to them.
Over twenty field types
Text, number, date, datetime, select, multi-select, boolean, currency, image, file, formula, entity reference and more. Each one validates on write, so bad data never lands.
In the APIField groups
Sort a long record into named, tabbed groups: identity, construction, compliance, whatever fits. Groups defined on a base type are inherited by every type under it.
Field defaults
Give a field a value that lands on every new record. Combine a default with a uniqueness rule and the field fills itself without ever colliding.
Part numbering
Generate the reference id on create from a pattern you control, per type. Numbers stay unique and readable without anyone keeping a spreadsheet of the last one used.
Catalogs and categories
Build typed classification trees and file records into them. One record can sit in several catalogs at once, so merchandising and engineering can each keep their own view.
In the APIEntity reference fields
Point one record at another and the link is real, not a copied string. Rename the target and every reference follows; delete it and the platform tells you what still depends on it.
Effectivity dating
Give a record an effective-from and effective-to window and read the catalog as of any date. A second axis covers build, order and batch ranges for structures that change mid-run.
Project templates
Start from a working model — Apparel PLM, CPG and formulation, robotics, manufacturer profiles — with types, fields and sample records already in place. Or start from an empty project.
Keep reading
Start free
Want this for your product data?
Spin up a workspace and start building. It only takes a few minutes.