Product compliance workspace

Manage many SKUs, keep manufacturer and EU responsible-person data consistent, track evidence, detect missing fields and generate reusable product-safety outputs.

Recommended workflow: add/import products → fix critical gaps → attach source notes → generate outputs → review affected SKUs when shared operator details change.
Products0
Ready0
Needs review0
Evidence items0

What should I do today?

Highest-priority open actions.

Catalog readiness

Quick SKU overview.

ProductSKUScoreStatus

Product source record

Store verified data once and reuse it.

Catalog

Select a product to edit.

ProductSKUMarketScore

Readiness review

Find missing or stale source data.

Recommended next actions

Economic operators

Shared records aggregated across the catalog.

TypeNameEmailProducts

Add evidence / source note

Evidence log

ProductTypeDateReference

Marketplace outputs

Generate channel-specific text from one source record.

Choose a product and generate an output.

Change Impact Center

See which SKUs depend on a shared operator.

Affected products

Market & language matrix

Operational view of market, language, warning and operator completeness.

ProductMarketLanguageWarningsOperator dataReview ageStatus

CSV Import Wizard

Upload a CSV, preview rows, then import or update by SKU.

Waiting for CSV data.

Bulk export

Data management

Drop backup JSON here or click to choose

What should Ready mean?

Use Ready as an internal workflow state: required source fields are present and reviewed. It is not a legal certification.

Why one source record?

Stable SKUs and one verified source record reduce inconsistent manufacturer, RP and warning data.

When should you review?

  • Manufacturer or EU RP changes
  • Warnings or instructions change
  • New market/language added
  • SKU or model mapping changes

What the app does not do

It does not test products, perform legal assessments or guarantee compliance.

Delete all real Product Compliance data?