Help centre · Products and validation
Classification, gaps and compliance status
What the compliance engine does after an upload: classification, the status buckets, clarification questions, the gap list per product, harmonised standards, and the five-phase flow on the dashboard.
What classification does
After an upload, every product is classified: the engine reads the description and the other mapped fields, assigns an HS code, and matches the product against the regulations that apply in the destination markets of your compliance profile. The result is a list of compliance areas per product — toy safety, RoHS, packaging — each with the requirements it brings. Products in a variant group inherit the classification from the group representative, so you answer once per group.
Status buckets
The Products table filters on a status per product:
- Not started — uploaded, classification not yet run.
- Classifying — the engine is working; nothing to do.
- Awaiting clarification — the data does not answer a question the classifier needs (see below).
- Standards pending — classified; the harmonised-standards evaluation is still running or waiting for answers.
- Compliant — every requirement is fulfilled with evidence.
- Non-compliant — at least one requirement has a gap.
- Failed — the classification hit an error. Reset the product to run it again, or enrich the description first.
The dashboard’s ledger shows the totals for the active collection: products classified, documents analysed, obligations fulfilled and documents expiring within 30 days.
Clarification questions
When the description is ambiguous — toy or decorative item, battery or not — the product stops in Awaiting clarification and asks. Open the product and answer the numbered questions; classification continues immediately. The dashboard step “Answer clarification requests” pins the table to that bucket so you can work through the queue, and a “Clarification requested” notification is sent.
The Compliance tab — the gap list
Open a product and choose Compliance. Each applicable regulation is listed with its requirements (checkpoints), and for every requirement you see what is still owed:
- documents missing (a test report, a Declaration of Conformity),
- attributes empty (a value the rule needs, such as a substance content),
- marking artwork missing.
Requirements are ticked as evidence lands: link a document, fill the attribute, upload the artwork. You can comment on a requirement, and “Read more” opens the relevant regulation page. A requirement removed by a rule update stays visible until you untick it, so nothing disappears silently.
Standards
The Standards tab lists the harmonised standards that apply, derived from the compliance areas. Some depend on details the engine cannot know (voltage, age group, material) and are asked as questions; until they are answered the list is provisional. Coverage shown here is evidence that a document says a standard was tested — never a verification by Conphora.
Attributes and documents
The Attributes tab shows how many required values are filled and lets you fill them by hand, from the product data or from documents. The Documents tab lists linked documents and the required-document slots; see Upload documents and AI extraction.
The five phases on the dashboard
“Recommended actions” on the dashboard walks a collection through five phases: confirm destination markets → upload documents → review what documents and product data already cover → collect what is still missing → run the final checks. Done steps stay clickable so you can revisit them; new products or documents reopen only the steps they affect.
When the status changes later
Rules change. When a regulation update affects a product, the dashboard’s regulatory feed says which products are affected, and a “Product no longer compliant” or “Product back to compliant” notification is sent when a status flips. Re-evaluate a product from its Compliance tab after you have changed its data.
If a product is stuck in Classifying or Failed after a reset, send a request with the product identifier.
Was this helpful?
Thanks — your feedback helps us improve this article.