Model anything, no migration

Model the product line
you didn’t see coming — this afternoon.

A hierarchical part-type tree with dynamic attribute schemas. Define the attributes a new product needs yourself, in minutes — no schema migration, no engineering ticket, no waiting on IT. One trustworthy record for every part, variant, and revision.

Flatbed trailer · parametric

qty = ceil(length / 2′) + 1
Deck length 14′ 0″16′ 0″20′ 0″14′ 0″
Crossmembers 3″ channel 89118 ea
Deck boards 2×8 treated 14162014 ea
7k axle kit 2232 ea
LED marker lights 6686 ea
Rolled-up cost $4,180$4,590$5,480$4,180

What actually changes

Not “a better part database.” The end of waiting on a schema change to sell a new product — and the end of “which spreadsheet is current?”

Quarter → afternoon

Stand up a product line nobody anticipated this morning — new part type, new attributes, ready to quote — before the day is out.

0 IT tickets

Engineers add the exact attribute they need themselves. No migration, no backlog, no waiting on a developer to change a table.

1 record, no doubt

Every part, variant, and revision lives in one governed source. “Which spreadsheet is current?” stops being a question.

Dynamic schemas

Add the attribute you need, not the one IT had time for

A part type is more than a name — it carries its own attribute schema. Inspired by WordPress’s ACF, engineers define new fields for any node in the part-type tree on the spot. The catalog instantly grows filterable grids and dynamic forms for them — with zero database migration behind the scenes.

  • Hierarchical part-type tree — attributes inherit down the branches
  • Typed, dynamic attribute fields defined without a code change
  • Filterable catalog grids that adapt to whatever you modeled
  • Dynamic entry forms generated from each part type’s schema

Internal part

PT-3401 · 30A Receptacle

3 approved sources
Leviton · 7313-W ApprovedLeesville, LA
Hubbell · RR430F ApprovedTopeka, IN
Eaton · 5700N Under reviewSugarcreek, OH

Variants & revisions

Variants stop being copy-pasted parts

A part variant is a first-class item — its own SKU, its own cost, its own lifecycle status — not a duplicated row someone forgot to update. Pair that with full revisioning, and every part carries a complete, attributed history: who changed what, when, and why it’s built the way it is.

  • Variants are managed, costed items — each with its own SKU
  • Per-variant cost and lifecycle status, tracked independently
  • Full revision history on every part, variant, and attribute
  • Status lifecycle: wip → in review → approved → released → obsolete

Trustworthy data isn’t a snapshot — it’s every version, attributed and recoverable.

Change & audit trail

CO-2026-118
  1. just now Released rev C · effective on next build
  2. 2m ago Approved by J. Kowalski (Engineering)
  3. 1h ago Stud spacing 24″ → 16″ o.c.
  4. 1h ago Linked 2 BOMs · 1 design

Designs & documents

The CAD file lives with the part, not in someone’s inbox

Designs and documents — CAD files, drawings, spec sheets, certificates — attach polymorphically to the parts and BOMs they belong to. The artifact that defines a component travels with it everywhere, so the shop floor and sales are never working from a stale download.

  • Attach CAD and documents directly to any part or BOM
  • Polymorphic links keep artifacts with the item they describe
  • One backbone feeds sales, pricing, and the factory alike
Explore Designs & documents

Flatbed trailer · parametric

qty = ceil(length / 2′) + 1
Deck length 14′ 0″16′ 0″20′ 0″14′ 0″
Crossmembers 3″ channel 89118 ea
Deck boards 2×8 treated 14162014 ea
7k axle kit 2232 ea
LED marker lights 6686 ea
Rolled-up cost $4,180$4,590$5,480$4,180

How it works

From a brand-new idea to a governed, sellable part

  1. 1

    Place the part type

    Add a node to the hierarchical part-type tree — it inherits attributes from its branch and is ready to extend.

  2. 2

    Define attributes

    Add the typed fields this product needs, ACF-style, with no schema migration and no engineering ticket.

  3. 3

    Catalog parts & variants

    Create parts and first-class variants — each with its own SKU, cost, and lifecycle status — through dynamic forms.

  4. 4

    Revise & release

    Walk every item through wip → released with full revision history, designs and documents attached.

PLM Product Lifecycle Management

Product Lifecycle Management is the discipline of governing a product’s data — parts, attributes, variants, revisions, and documents — across its whole life. Classic PLM locks that data in a vault only engineers can open, far from the people who sell and build. Manufacts folds the PLM backbone straight into Configure-to-Manufacture, so the same trustworthy record drives sales, pricing, and the factory floor.

Learn the full spectrum

Under the hood

Everything the product-data backbone does

Hierarchical part-type tree

Organize part types into a tree where attribute schemas inherit down the branches.

Dynamic attribute schemas

Define typed attributes for any part type — ACF-inspired, with no database migration.

Filterable parts catalog

Grids that adapt to your attributes, with dynamic forms generated per part type.

First-class variants

Each variant carries its own SKU, cost, and lifecycle status — not a copy-pasted part.

Full revisioning

Complete, attributed revision history on every part, variant, and attribute.

Status lifecycle

wip → in review → approved → released → obsolete, enforced across the catalog.

Designs & documents

CAD files and artifacts attach polymorphically to the parts and BOMs they define.

One source of truth

The same governed record feeds the configurator, pricing, and the shop floor.

Bring the product line you can’t model today.

Show us the SKU your current system can’t represent — the one waiting on a schema change. We’ll model its part type, attributes, and variants live, and have it sellable in 30 minutes.

No rip-and-replace — Manufacts runs alongside your ERP and CAD. Prefer email? hello@manufacts.ai