生物资产

声明永远不会完成。产品发生变化。供应商发生变化。法规发生变化。静态 PDF 在您发送之日就已过时——只要您的市场需要，Sustalium 资产就保持正确、在线且可验证。

Products change. Suppliers change. Regulations change.

Your REACH declaration reflects the materials in your products today — not last year's formulation. Your Digital Product Passport must reflect this year's carbon footprint, not the one from your launch. A supplier switch, a new batch of raw material, or an amended regulation all make yesterday's PDF wrong.

This is why Sustalium assets are designed as living records. When a material changes, you update the declaration and re-publish. The people who already received your QR code — printed on packaging, labels, or buyer portals — automatically see the current version. No re-sending, no new print run, no orphaned files.

When a regulation is amended — like the expanding requirements of CS3D or CSRD — Sustalium flags the frameworks you publish under, so nothing quietly expires. You review, update, and re-verify with evidence that stays linked underneath.

What gets updated — concrete examples

Every data point in a Sustalium asset can be updated the moment reality changes. Here is what that looks like in practice across the three entity types the platform structures: your company, your services, and your products.

Company

Company-level data is the foundation every asset is built on. When it changes, every published asset that references it updates in one place:

• Registered office or legal name change — re-issues company-level declarations and buyer-facing pages with the new entity details, while the URL and QR code stay the same.
• New responsible person or signatory — updates authorisation and sign-off fields across published assets, with every approval recorded in the audit trail.
• Certificate renewals — when an ISO 9001 or ISO 14001 certificate is renewed or lapses, the linked asset updates and the expiry flag refreshes, so you never present stale credentials to a buyer.
• Licences and registrations — food registration numbers, trade licences, and EUID numbers re-publish instantly when they are renewed.

Services

If you sell services rather than — or alongside — products, the same living mechanism keeps service declarations accurate:

• Scope of service changes — adding or removing a service line updates service-level declarations and GDPR processing descriptions in a single edit.
• Subcontractor or partner changes — a new logistics or subcontracting partner updates your due diligence declarations with the current chain of custody, from CS3D to UFLPA supplier audits.
• Policy revisions — updated terms, privacy policies, or codes of conduct replace the previous version while keeping the same public URL and full version history.

Products

Product data changes most often — materials, formulations, suppliers, and batch details. Each change flows into every asset that references the product:

• Material or formulation change — updates your REACH declaration and Digital Product Passport with the new composition and carbon footprint, without invalidating the QR code already printed on your packaging.
• Supplier or origin change — refreshes country-of-origin statements and FSMA 204 traceability evidence with the current batch records.
• Packaging changes — new packaging material data flows into recycling, circularity, and CSRD-relevant declarations.
• Regulation amendments — when a framework itself changes, Sustalium flags every affected asset, carries your data forward, and you re-publish in minutes instead of starting over.

What every living asset includes

这就是 Sustalium 定价按月的原因：您不是在购买文件，而是在保持正确、托管且可验证的动态资产，只要您的市场需要即可。

How updates stay verifiable

Every re-published version keeps the same public URL and QR code, secured by a new hashcode. Anyone can verify the asset independently — checking that it is genuine, current, and untouched since the last approved update. Buyers see one canonical asset; auditors see the full version history, approval trail, and linked evidence.

Because the URL never changes, your customers' records never go stale: the same link that proved compliance at the first order still proves compliance on the fifth.

Frequently asked questions