FR

Compliance limitations

Prooflet checks artwork. It does not make final regulatory decisions.

This page is intentionally direct. It protects the product from claims the backend, legal review, or external tooling cannot yet support.

Compliance aid only

Prooflet is designed as a compliance aid for Canadian cannabis packaging artwork workflows. It helps teams identify issues, create review evidence, and prepare export packages. It does not replace customer regulatory review, legal advice, printer/converter review, or distributor acceptance.

No regulator sign-off claim

Prooflet must not be described as having government sign-off. The safer wording is that artwork is checked or validated against a versioned rule pack and a named converter profile.

Health Canada source context

Health Canada publishes packaging guidance and cannabis health warning messages. Licence holders remain responsible for complying with the Cannabis Act, Cannabis Regulations, and any applicable provincial or territorial requirements.

PDF and print limitations

The open export path is best-effort PDF/X-4 with a conformance-gap report. Formal PDF/X validation, per-ink separation rendering, commercial trapping, and converter acceptance depend on external tools or converter-specific review.

Manual review states

Subjective, incomplete, or uncertain checks should surface as REVIEW or FAIL. They should not silently pass. Examples include youth appeal, lifestyle impression, flavour impression, container colour evidence, and converter acceptance.

Hosted and commercial gaps

  • Production-hosted account management, authentication hardening, session operations, and team invites.
  • Durable object storage, retention controls, and hosted export archives.
  • Queue-backed compilation capacity, retry handling, and production artifact delivery.
  • Native Illustrator ingestion remains outside the open compiler path and requires future commercial tooling before it can be offered.
  • Commercial PDF tooling, formal validation, licensed colour libraries, SSO, payments, and enterprise integrations.

Use of examples

All examples on this site are synthetic. They are included to demonstrate workflow shape and should not be treated as customer artwork, final label copy, or production-ready files.