67 public catalog checks
PROVEN uses a public catalog of 67 standard checks to identify observable problems without reducing the whole catalog to a synthetic score.
- Evidence tied to evaluated data
- Categories and severity
- Public check explorer
PROVEN public reference
This is the public reference for current PROVEN capabilities. Each capability declares its state, platform, evidence, and boundaries so availability is not silently extended beyond what is published.
Read availability per capability, per platform, and together with the published limitation.
The platform at a glance
Every domain below follows the same principles: explicit authority, observable evidence, verifiable state, and clear boundaries.
01 · Catalog Intelligence
Checks, evidence, and product context come first. PROVEN does not turn an ambiguous problem into an automatic change.
Know what is wrong before touching the catalog.PROVEN uses a public catalog of 67 standard checks to identify observable problems without reducing the whole catalog to a synthetic score.
A reported problem stays connected to the catalog state that produced it, so the merchant can see what was observed and why it matters.
Not every finding automatically has a remediation available.
Problems affecting the same product can be viewed together and grouped by the semantic target they affect, rather than only as isolated rows in a list.
02 · Review & Governance
Review, exceptions, and stale state remain distinct from remediation and publishing.
Decision stays separate from execution.Findings can be evaluated individually or in controlled selections, while the review decision stays separate from any catalog mutation.
If the product changed after an action was prepared, supported flows can stop the apply step instead of overwriting newer state.
03 · Remediation
Manual, assisted, deterministic, or AI-assisted — different methods with different authority and boundaries.
Rules first. AI where context is genuinely required.PROVEN does not send every problem to a model. When the result can be established safely, it uses deterministic remediation. When interpretation is required, the merchant decides.
For eligible product-title, SEO-title and SEO-description issues, PROVEN can generate a contextual proposal that remains a draft for review.
AI is not enabled for every target and does not publish automatically.
04 · Controlled Operations
PROVEN treats a change as a controlled process: revalidation, a target-scoped change, read-back, verification, and reconciliation.
The resulting catalog state matters, not only the endpoint response.On supported flows, PROVEN checks permission and current state, performs only the authorized target change, reads the platform state again, and confirms the result before treating it as verified.
The Shopify flow can process one bounded action of up to 200 findings through Prepare → Approve → Publish while preserving per-item outcomes.
This is the current Shopify flow limit, not an unlimited-bulk promise, and it does not apply to WooCommerce.
The Woo Merchant workspace can prepare and apply one bounded selection of up to 10 eligible items in strict sequence, using the exact approved preview for each change and preserving a per-item outcome.
This capability remains in controlled rollout while real-store validation at this ceiling is completed. Woo billing and webhook/monitoring parity are not included; rollback and image-file optimization have their own rollout boundaries and do not imply Shopify bulk parity.
For eligible product-title, description HTML, and media ALT changes, PROVEN can recheck current state, require explicit confirmation, restore the previous value, and verify the result again.
This is controlled rollback for supported PROVEN changes, not universal Undo. Woo billing and webhook/monitoring parity remain outside the current public state.
The new product flow keeps each prepared target separate, rechecks the plan before publishing, and can report applied, partial, failed, or blocked outcomes for the same plan.
The implementation is in controlled rollout; live Shopify certification for the new product-level apply surface is still pending closure.
05 · Monitoring & Recovery
Monitoring keeps findings aligned with relevant changes, while recovery keeps uncertain states explicit.
The catalog keeps changing. Control should continue too.PROVEN can recheck relevant catalog changes, including changes made outside PROVEN, so findings stay aligned with the current state.
Monitoring does not automatically start remediation or publish another change.
Controlled flows can distinguish stale, partial, retryable, unverified, or recovery-required outcomes instead of collapsing every failure into one generic state.
07 · Multi-store & Agencies
Agencies can work across multiple stores with roles, acces limitat și alocare, and audit kept separate per client.
One operating model, with clients kept separate.One agency can administer multiple stores with roles, store scope, controlled assignment, and contextual audit without merging client authority.
The authority and workspace model is launch-certified for operator-assisted onboarding. Production activation remains controlled for each agency/operator/store relationship; there is still no self-service signup, consolidated agency billing, or simultaneous multi-agency ownership of one store.
The merchant can see the active management relationship and support/dispute path without gaining assign, release, or reassign authority from that surface.
08 · Media Operations
ALT remediation and binary optimization have different authority, verification, and recovery. PROVEN keeps them separate.
Do not compress an image when the problem is ALT, and do not invent ALT when the factual information is missing.PROVEN keeps ALT metadata problems separate from image-file operations so each type of change preserves the correct permission boundary.
For supported Shopify sources, PROVEN can optimize JPEG, PNG and WebP, keeps the current source when the result is not smaller, and verifies replacement before finalizing the commercial operation.
The implemented flow includes preparation, controlled publication, read-back verification, recovery, and controlled restore of the original media association; the Merchant surface includes authority-backed progress and savings totals.
Cumulative real-store rollout is not yet closed for general availability. Restore works only when the original media association can still be verified; it is not a universal original-file re-upload promise and does not include Woo billing.
09 · AI & Commercial Control
Models, budgets, access rules, and paid operations are not hidden interface constants and do not decide by themselves what gets published.
AI is a tool. Authority stays in the system.Providers, models, budgets, and cancellation are managed separately from merchant permissions, while model output passes independent validation before it can enter a remediation flow.
Access, limits, and operation pricing are designed to come from versioned commercial authority rather than constants scattered across the interface.
10 · Platform Integrations
Shopify is the deepest commerce integration, while WooCommerce already uses the same PROVEN model for detection and controlled remediation in the certified areas.
One PROVEN model, with platform-specific depth.On Shopify, PROVEN combines catalog intelligence, controlled remediation, bulk workflows, monitoring, rollback, image operations, Agencies, billing, and audit in the same operating model.
Shopify Sidekick can receive a limited read-only catalog-quality view and open the relevant context in PROVEN.
Sidekick does not confirm, publish, or execute remediation.
WooCommerce already uses the PROVEN engine for detection and controlled remediation of product title, description HTML, and image ALT in both operator-managed flows and the separate merchant workspace.
WooCommerce does not yet have full Shopify parity: Merchant bulk, controlled rollback, and image-file optimization are declared separately as bounded rollouts, while Woo billing and webhook/monitoring parity remain outside the current public state.
Why one system
A point-solution stack can detect, edit, monitor, and restore data in different apps. PROVEN keeps the problem, decision, change, verification, and recovery connected.
Point solutions can share the same feature checklist. They do not automatically share operational truth.
Platforms
Capabilities are declared separately by platform. A capability existing on Shopify does not automatically make it available on WooCommerce.
The deepest commerce integration: remediation, controlled bulk, monitoring, rollback, media operations, Agencies, billing, Sidekick, and audit.
Explore Shopify workflowsPROVEN detection plus controlled remediation for product title, description HTML, and media ALT. Merchant bulk for up to 10 items, controlled rollback, and image-file optimization have separate bounded rollouts.
No full-parity promise with Shopify: Woo billing and webhook/monitoring parity are not yet published as available, and image optimization is not yet generally available.Explore WooCommerceExplicit boundaries
Control is valuable only when the boundaries are as clear as the capabilities.
From reference to context
Use Try PROVEN for public signals or review current pricing to estimate the next step.