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.

Product	SKU	Score	Status

Product source record

Store verified data once and reuse it.

Product name

Model / type

Stable SKU / identifierUse an identifier that does not change when marketplace titles change.

Manufacturer

Manufacturer email

Manufacturer address

EU responsible person

EU RP email

EU RP address

Warnings / safety information

Market

Language

Workflow status

Last reviewed

Internal notes

Catalog

Select a product to edit.

Product	SKU	Market	Score

Readiness review

Find missing or stale source data.

Product

Recommended next actions

Economic operators

Shared records aggregated across the catalog.

Type	Name	Email	Products

Add evidence / source note

Product

Type

Date

Reference / note

Evidence log

Product	Type	Date	Reference

Marketplace outputs

Generate channel-specific text from one source record.

Product

Output

Choose a product and generate an output.

Change Impact Center

See which SKUs depend on a shared operator.

Operator

New email

New address

Affected products

Market & language matrix

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

Product	Market	Language	Warnings	Operator data	Review age	Status

CSV Import Wizard

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

Choose CSV file

CSV

Waiting for CSV data.

Bulk export

CSV columns: name, model, sku, manufacturer, manufacturer_email, manufacturer_address, eu_rp, eu_rp_email, eu_rp_address, warnings, market, language, status.

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?

Marketplace titles change. 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

Why evidence notes?

They let you reconstruct why a field or warning was used later, without relying on memory.

What the app does not do

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

Best workflow for many SKUs

Import → fix critical gaps → attach evidence → generate outputs → review shared changes → export backups regularly.