Loading

Prepare and approve a product release

Use this process to establish the stable technical revision that production batches, physical instances, and applicable passport mappings will consume. The result is an approved Product Release, with its intended composition and exact supporting document revisions where relevant.

A release captures the concrete product's approved category and effective template. Do not start by entering the same nominal product characteristics into each batch or instance. Those records refer to the release and add facts about actual production or one physical item.

Responsibilities

Responsibility Usual company role
Prepare technical product data and the draft release Product Editor, Product Governance Manager, or Company Administrator
Prepare intended composition and supporting evidence An authorized product-data contributor
Approve the exact technical revision Product Governance Manager or Company Administrator with release-approval authority
Use the released revision to register production Production Manager or Company Administrator with production authority

An accepted operational delegation can authorize an appropriate partner within a defined scope. A production responsibility alone does not authorize technical approval. Select the company that administers the release; being an Application Admin is not a substitute for that company's authority.

1. Check the product source

Choose a product-level category associated with the current company as Manufacturer or Brand Owner in Product Overview's preparation workspace. Browse the company's Published concrete products using search, paging and category attribute filters, then use Select items. Review the selected product's approved effective template, attributes, units, identifiers and documents; complete normal product publication first if it is not eligible.

For variants, prepare the exact concrete variant to be manufactured. Keep a variant group for organizing related choices. Do not manufacture a group or use a commercial multipack as an assembly definition.

2. Capture a draft release

  1. Open Logistic → Definitions → Product Release.
  2. Search the existing revisions for the product to avoid a duplicate.
  3. Select Create new product release for the selected Published product. If a product has not been selected, use the Product Overview selection action; do not search the entire product database in a small autocomplete.
  4. Enter a meaningful Revision, such as the company's approved design revision.
  5. For an update, choose the earlier Predecessor and describe the Change Reason.
  6. Select Create new product release.

The draft captures technical information and retains associated document files. Inspect the captured revision, rather than assuming that its content matches an earlier review of the working product.

3. Prepare composition where applicable

Open Product Composition, select Create new composition, and choose the draft release. Save the header, then add and save its Composition entries. Identify released component products or material scheme/code, assembly positions, positive quantities, and known units.

Composition is the intended design. Actual component batches and installations are registered later through Component Use. Check for missing sources, unsupported units, self-inclusion, and component cycles before approval.

4. Review and release

The authorized reviewer opens the exact draft. Verify its technical capture, composition, predecessor, reason, and retained documents. In the decision area, select Release, enter the approval reason, and select Apply decision.

The product must still be approved and agree with the captured source. If product information changed, save the draft again to refresh its capture, inspect the refreshed information, and repeat the review. Composition changes also change the draft under review. Reload after concurrent changes instead of approving from an older page.

Successful release makes this revision available as an approved production source and approves its attached composition. It does not create a batch, assign serials, publish a passport, or submit catalog content.

5. Keep later changes explicit

Create a new release when the approved technical design changes. Link its predecessor and explain the change. Use Supersede or Withdraw, with the appropriate decision reason, when a previous release should no longer be the current source for new work.

Existing batches and instances keep their original manufacturing release. A passport update requires its own preparation and review; a new product release does not silently replace an earlier passport publication. External catalog publishing remains a separate workflow.