Support

Bring the case reference. Keep the evidence attached.

Choose product, implementation, or application support and include the supplier, category, request, or decision involved.

REQUESTEVIDENCERISKDECISION
SUPPORT

Choose a path

Specific context gets a useful answer.

Never send a password, secret, or private key. An operating reference and the observed state are enough to begin.

Product

Does it fit the process?

Ask about qualification modules, role separation, evidence, risk review, and approval controls.

Ask a product question
Implementation

How should we start?

Get help framing categories, evidence standards, assessors, reviewers, and approvers.

Plan an implementation
Application

Why is this case blocked?

Get help with ERP.ai access, permissions, records, or qualification workflow behavior.

Request application support

Useful context

Send the smallest complete case.

Name the affected record and what should have happened. That preserves signal without copying the whole dossier.

IdentitySupplier name or code and the qualification-request title
StageRequest, questionnaire, assessment, document, risk review, or approval
Expected stateThe state or decision you expected and the role performing the action
Observed stateWhat happened instead, including any visible message

Does this website hold supplier records?

No. This is the public product website. Records, permissions, workflows, and decisions run inside ERP.ai.

Can a workflow approve a supplier silently?

No. Applying a qualification decision is consequential and must follow an explicit recorded approval.

Where should I report an access issue?

Email support@erp.ai with the organization and application name, but never include credentials.

Return to the case

Open Supplier Management in ERP.ai.

Sign up
Made with Proto