Loading

Production Batches

A Production Batch records a quantity of a concrete product manufactured against one approved Product Release, by an identified manufacturer at an identified Facility. It answers: Which revision was made, where, when, and under which batch number?

For example, Battery Module M1 release R2 can have batch MAY-001 from Factory North and batch MAY-002 from Factory South. Both use R2, but their manufacturing periods, quantities, factory records, parameters, and evidence remain separate.

Read the relationships

Related record What it contributes
Product Model or concrete variant being manufactured.
Product Release Approved technical edition used for this batch.
Facility Actual site of manufacture recorded for this run.
Product Instance A particular physical item from the batch, identified by issuer and serial.
Digital Product Passport Reviewed publication for this exact batch or one of its individual items, according to the selected profile.

Batch number labels the manufacturing run. Revision labels its technical source. Serial number labels a physical item. The same model and revision can have several batch numbers and several factories. Opening a batch should let you check those relationships together before registering items or preparing a passport.

In the internal MIPEX example, MIPEX-QA-20261006-A belongs to MIPEX Internal QA Factory A and MIPEX-QA-20261006-B belongs to MIPEX Internal QA Factory B. Both refer to the release designation INTERNAL-QA-20261006-01. These records demonstrate the relationships and make no assertion about actual factory production or regulatory certification.

What a batch contains

The batch identifies its administering company, issuing company and batch number, approved release, actual manufacturer and factory, production period and date precision, quantity/unit, optional expiry, batch parameters, and retained documents. The batch number is unique within its issuer.

A batch is not a commercial package, warehouse balance, or variant group. Moving goods to a warehouse does not change their original manufacturer or factory.

Different concrete variants may share a production order or manufacturing run. In Actualog, register a separate batch for each concrete product release so that quantity, parameters, factory, evidence and item identities remain unambiguous. A variant group describes related models; it does not replace the manufactured product's identity. This is Actualog's current traceability model, rather than a universal rule imposed by DPP legislation.

Open a batch and its items

The Production Batch register lists batches. Select a batch number or choose Product instances in this batch from its action menu to open that batch's items. The item list appears before batch administration and supports Table, List and Grid views. Select an item to edit its permitted facts; the linked batch, release and factory show its manufacturing source.

For a Released batch, choose Create new product instance in that list to register an item with the batch already selected. The batch quantity can exceed the number of registered serialised items. Recording a batch quantity does not automatically create physical-item records.

Who maintains it

A Production Manager, Company Administrator, or user with accepted scoped production delegation creates and manages batches. A Product Governance Manager approves the release and product–facility assignment on which production depends. Being named as manufacturer, operator, or seller does not itself grant editing permission.

Create and release a batch

  1. Select the administering company and open Logistic → Production → Production Batch. Search and filter the register before choosing + Create new batch.
  2. Select the approved release, actual manufacturer, and factory by their displayed names. Set the issuer to the current administering company; the current workflow does not issue a batch number on behalf of another company. Enter its genuine batch number and positive quantity with its unit.
  3. Enter the known production period and Date Precision. Use Month or Year when the source does not establish an exact day. Add supported expiry when applicable.
  4. Select applicable retained revisions in Supporting documents and create the draft. In Batch parameters, use Add row, select an attribute and its typed value/unit, then Save. Parameters must belong to the approved template and use compatible types and units.
  5. In Lifecycle decision, select Release, enter the reason, and choose Apply decision.

Saving creates a Draft. Release checks the approved revision and applicable manufacturing relationship. Released batch facts are preserved; ordinary editing cannot silently rewrite them.

For Month precision, the current date input uses the first day of the known month at 00:00 as a period anchor. For Year precision, use January 1 at 00:00. The saved precision marks that value as a month or year, not an assertion that manufacture happened on that exact day.

States, blockers, and maintenance

Draft is preparation; Released permits normal instance registration; On Hold records a hold; Closed ends batch operations; Cancelled stops an unissued draft. Decisions are offered only for permitted state transitions.

An unreleased revision, duplicate number, expired facility approval, unsupported manufacturing relationship, invalid date, quantity or unit, or changed form version can block the operation. Correct the named source or reload before retrying. Do not fabricate a factory or precise date.

Complete parameters while the batch is Draft. Record later movements and service as lifecycle events and availability as warehouse stock reports. Use Manufacturing traceability for related inputs/outputs. Refresh and review affected passport drafts separately; existing publications remain unchanged.

Creating production batches · Product releases · Product instances · Facilities · Product lifecycle events