XJDF Master Data Model

NowToPrint keeps master data as the single source of truth and exposes it through XJDF-native contracts. The platform does not treat XJDF as a loose export format. It uses XJDF 2.2 semantics to define how media, devices, sourcing and job snapshots are structured end to end.

---

The five-layer model

Every major master-data family follows the same layered model:

Layer	Purpose	Example
generic class	Neutral technical definition	70x100 4-color sheetfed offset
branded product	Market-facing product identity	Sappi Magno Satin 130 gsm 70x100
supplier/source	Commercial and supply truth	supplier, MOQ, lead time, validity window
organization override / installed asset	Tenant-specific reality	local machine options, local media price, local constraints
job snapshot	Immutable execution truth	exact source, unit, compatibility decision and assumptions used for the quote/order

This model is what lets /admin publish canonical truth and /dashboard apply controlled overrides without forking the shared taxonomy.

---

Core master-data families

Media

Media records are not stored as a flat paper list anymore. A complete media chain contains:

• generic media type
• branded media
• supplier/source validity
• organization override
• job-time resolved snapshot

Important attributes include:

• dimensions and available stock sizes
• weight and coating
• XJDF product identifiers
• reference price and raw price unit
• supplier availability, MOQ and lead time

Devices

Device truth is split between:

• generic device capability
• installed machine truth for each organization
• routing and costing snapshots at job time

Installed asset truth is now part of production decisions. Routing and costing are expected to look at the same real machine, not just the same machine family.

Finishing and consumables

Bindings, lamination, varnish, plates, labor and utilities follow the same canonical direction:

• canonical taxonomy in admin
• organization override where business reality differs
• immutable snapshot in quote/order/production

---

Compatibility matrix

The media-device compatibility matrix is a first-class part of the model.

It answers questions such as:

• can this substrate run on this specific press?
• is the match native, conditional or unsupported?
• which rule and notes justify the decision?

Compatibility is no longer a hidden advisory hint. It feeds:

• quote confidence
• routing decisions
• manual review gates
• operator review queue items

---

Supplier validity and inventory truth

Supplier/source records are used to decide whether a media option is commercially usable right now.

The platform tracks sourcing truth such as:

• available stock
• required quantity
• minimum order quantity
• lead time
• price validity window
• source status such as active, discontinued or not-yet-valid

If the system cannot prove that the source is usable, it must downgrade confidence or require manual review instead of pretending the quote is final.

---

Job snapshot discipline

Quotes and orders must carry the truth that was used at the time of calculation.

At snapshot time the platform preserves:

• resolved media and brand ids
• resolved supplier/source ids
• resolved machine or installed asset ids
• raw price unit and normalized price unit
• compatibility decision and notes
• manual review reasons
• imposition assumptions and waste plan

This is what makes pricing disputes, audits and production parity manageable later.

---

Where to use this guide

Use this page when you are:

• integrating XJDF master-data export/import
• designing admin or dashboard override behavior
• mapping external ERP/MIS data to NowToPrint
• reviewing snapshot and audit semantics

Use the other guides below when you need surface-specific details.