Data modeling

Elevate plan

Data Modeling is the advanced settings area for custom business data. It lets you define tables, fields, rows, relations, and semantic mappings that Product Settings, Forecast, and purchase-order constraints can read.

What Data Modeling is for

Use Data Modeling when a simple product or variant attribute is not enough. Common examples:

Packaging profiles with multiple fields.
Purchase families or buying groups stored as reusable rows.
Supplier-specific commercial attributes.
Compliance or sourcing tables that several variants point to.
Constraint roles that should come from a Data Model field instead of a direct Product Settings attribute.

For one number or label directly on a product or variant, Settings -> Products -> Attribute Definitions is usually simpler.

Variant Extension Studio

Open Settings -> Data Modeling. The main surface is Variant Extension Studio:

The canvas defines tables and fields.
The inspector edits table names, field names, field types, and constraint roles.
The row editor creates and updates custom records.
The value grid fills field values for custom records.

The page can be explored on lower plans, but saving changes requires Elevate.

Entities, fields, rows, and values

Data Modeling uses four building blocks:

Building block	Merchant meaning
Entity	A custom table, such as Packaging Profile or Purchase Family.
Field	A column on that table. Fields can be text, number, date, boolean, list-like values, or linked data depending on the table setup.
Record	A row in the table, such as `carton-65` or `family-core-denim`.
Value	The value stored for one field on one row.

Rows have a stable key and a label. If you do not provide a key, Logistified generates one from the label. Duplicate row keys in the same table are rejected.

Semantic mappings for constraints

A semantic mapping tells Logistified, “this Data Model field means Unit CBM” or “this field means Purchase family.” Constraint Studio then treats that field like a mapped Product Settings attribute.

Supported constraint roles are:

Group key
Unit CBM
Unit weight
Case size
Pallet quantity
Purchase family
Product MOQ

The field type must match the role. Number roles require numeric fields; text/list roles require text-like fields. Duplicate active mappings for the same role are replaced by the newest saved mapping from the studio.

Managed Product Settings attributes

When a Data Model table needs to be selected from a product or variant, Logistified can create a managed Linked table row attribute in Product Settings. These managed attributes:

Appear on Settings -> Products -> Attribute Definitions.
Are marked as managed.
Are read-only there.
Cannot be deleted from Product Settings.
Must be changed from Data Modeling.

This keeps Product Settings and Data Modeling connected without letting the generated link get edited from the wrong place.

Save and stale-edit protection

Data Modeling saves the schema, rows, and values together. If another tab saves a newer revision first, Logistified rejects the stale save and asks you to reload. This protects entities, semantic mappings, and row values from being overwritten by an older browser tab.

Partial failures are shown on the page. If a save fails, reload before making more structural changes so the canvas matches the server state.

When to use Product Settings instead

Use Product & variant attributes instead of Data Modeling when:

You only need one product or variant value.
The value can be edited directly on the product/variant.
You only need a constraint role such as Product MOQ or Unit CBM.
You do not need a reusable table of rows.

Use Data Modeling when the data has structure: rows, relations, linked table references, or values shared by many products/variants.