Edit a product
How you edit a product depends on its current publication status. Traceable handles draft and published products differently to ensure that publicly accessible DPPs are never silently changed without a deliberate republication step.
Editing a Draft Product
Products in Draft status are fully editable without restriction. All fields across all DPP sections can be modified freely, and changes are saved automatically via autosave.
To edit a draft product:
- Go to Products in the sidebar.
- Click the product name to open the product record.
- If the product is in Draft status, you are taken directly to the DPP editor. No additional steps are required.
- Make your changes. Autosave captures changes every 30 seconds, or press
Cmd+S/Ctrl+Sto save immediately.
There is no version history for draft products. The current draft represents the single working copy. If you need to preserve an intermediate draft state, consider exporting the product data before making significant changes.
Editing a Published Product
When you open a product in Published status and begin editing, Traceable automatically creates a new draft revision. This means:
- The currently published DPP remains live and publicly accessible at its existing URL.
- The draft revision is a complete copy of the published version, which you can freely edit.
- The QR code continues to resolve to the published version throughout the revision process.
- The product status changes to Draft (Revision) to indicate that an unpublished revision is in progress.
This approach ensures continuity of public access. Regulators, auditors, or supply chain partners scanning the QR code will always see the last published version, not an incomplete revision.
Starting a Revision
- Navigate to Products and click the published product.
- Click the Edit button in the top-right corner of the DPP viewer.
- A confirmation dialog appears: "Editing this published product will create a draft revision. The current published version will remain live until you republish." Click Start Revision to proceed.
- You are taken to the DPP editor with all fields pre-populated from the published version. A banner at the top of the editor shows: "You are editing a draft revision. Published version remains live."
Discarding a Revision
If you started a revision but want to abandon your changes and revert to the published state:
- Open the product.
- Click Discard Revision in the editor toolbar.
- Confirm the action. All unsaved changes to the draft revision are permanently discarded and the product returns to Published status with no draft revision.
This action cannot be undone. If you have made changes you want to preserve, export the product data before discarding.
Field-Level Change Tracking
For published products with a draft revision in progress, the DPP editor highlights fields that differ from the published version:
- Fields that have been modified are highlighted with an amber indicator and show the previous value as a tooltip when you hover over the field label.
- Fields that were empty in the published version but have been filled in the revision are marked with a green "New" badge.
- Fields that have been cleared (previously had a value, now empty) are marked with a red "Cleared" badge.
This visual diff makes it easy to review exactly what will change when you republish, and to catch accidental modifications before they go live.
You can also view a side-by-side comparison of the draft revision and the published version by clicking Compare with Published in the editor toolbar. This opens a full-page diff view that shows all field changes in a structured table.
What Triggers a Re-Verification Requirement
Some changes to a published product invalidate previous verification findings and require re-verification before the new version can be published. Traceable automatically evaluates changes against this rule set and flags re-verification requirements in the revision editor.
The following types of changes trigger a re-verification requirement:
| Change Type | Why Re-verification Is Required |
|---|---|
| Nominal capacity changed by more than 2% | Capacity is a fundamental performance claim that verifiers assess against test reports. A significant change may not be supported by existing documentation. |
| Nominal voltage changed | Voltage underpins energy calculations and safety assessments. Any change requires the verifier to confirm the supporting test evidence remains valid. |
| Battery chemistry changed | A change in electrochemical technology fundamentally alters the applicable test standards and safety requirements. All prior verification is void. |
| Manufacturer name or address changed | The identity of the manufacturing entity is a verified claim. Changing it requires the verifier to confirm the new entity relationship. |
| Carbon footprint values changed by more than 5% | Carbon footprint declarations are subject to third-party verification under Annex XIII. Material changes require re-verification. |
| State of health parameters changed | Performance class and cycle life claims require supporting test data. Changes must be verified against updated test reports. |
Changes to fields that are not in the table above — such as product description, marketing text, supplementary documents, or contact information — do not trigger a re-verification requirement.
When a re-verification requirement is triggered, a banner appears in the editor and the affected fields are marked with a blue verification badge. You can still save and republish the revision, but the account-level compliance score will reflect the reduction in verified coverage until a new verification task is completed and approved.
If you need to proceed to publication before re-verification is complete, consider whether the regulatory context permits this. For products already on the EU market, publishing an unverified material change may create a compliance gap. Review this with your compliance team before republishing.
Publishing a Revision
When your revision is complete, follow the standard publish workflow to make it live. See Publish a DPP for details. On republication, the revision becomes the new published version and the previous version is archived internally (it is no longer publicly accessible, but Traceable retains a snapshot of it in the audit trail).