PROVEN public reference

What PROVEN can do now — and where the limits are.

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

Not a collection of tools. One operating model.

Every domain below follows the same principles: explicit authority, observable evidence, verifiable state, and clear boundaries.

01 · Catalog Intelligence

Understand what is wrong before changing the catalog.

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.
AvailablePROVEN

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
Platform-specificShopifyWooCommerce

Evidence-backed findings

A reported problem stays connected to the catalog state that produced it, so the merchant can see what was observed and why it matters.

  • Factual evidence
  • State and severity
  • Product context where available

Not every finding automatically has a remediation available.

Platform-specificShopify

Product-level context

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.

  • Product grouping
  • Semantic targets
  • Shared context for compatible problems

02 · Review & Governance

A finding is evidence, not an automatic change.

Review, exceptions, and stale state remain distinct from remediation and publishing.

Decision stays separate from execution.
AvailableShopify

Review before action

Findings can be evaluated individually or in controlled selections, while the review decision stays separate from any catalog mutation.

  • Individual review
  • Controlled bulk review
  • False-positive and exception states where supported
Platform-specificShopifyWooCommerce

Old state cannot authorize a new change

If the product changed after an action was prepared, supported flows can stop the apply step instead of overwriting newer state.

  • Pre-change revalidation
  • Stale-state protection
  • No blind overwrite

03 · Remediation

Use the right method for the right problem.

Manual, assisted, deterministic, or AI-assisted — different methods with different authority and boundaries.

Rules first. AI where context is genuinely required.
Platform-specificShopifyWooCommerce

Manual, assisted, deterministic and AI — different jobs

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.

  • Manual editing
  • Non-generative assistance
  • Deterministic corrections
  • Optional AI for eligible cases
Platform-specificShopify

Optional AI, separate from publishing

For eligible product-title, SEO-title and SEO-description issues, PROVEN can generate a contextual proposal that remains a draft for review.

  • Bounded eligible fields
  • Editable proposal
  • Explicit approval and publishing

AI is not enabled for every target and does not publish automatically.

04 · Controlled Operations

An API 200 is not enough to declare success.

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.
Platform-specificShopifyWooCommerce

Applying a change does not end at the API 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.

  • Permission and current-state check
  • Target-scoped change
  • Platform read-back
  • Outcome verification
Platform-specificShopify

Controlled bulk remediation for up to 200 findings

The Shopify flow can process one bounded action of up to 200 findings through Prepare → Approve → Publish while preserving per-item outcomes.

  • Separate Prepare step
  • Explicit approval
  • Controlled publish through existing authority
  • Per-item outcomes and recovery

This is the current Shopify flow limit, not an unlimited-bulk promise, and it does not apply to WooCommerce.

Controlled rolloutWooCommerce

Controlled Woo Merchant bulk remediation for up to 10 prepared items

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.

  • Maximum 10 prepared items
  • Strict sequential preview and apply
  • Exact approved preview retained for each change
  • Stale items reported without undoing prior verified writes
  • Applied changes remain in activity history

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.

Controlled rolloutWooCommerce

Controlled rollback for supported Woo Merchant changes

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.

  • Pre-rollback preview
  • Explicit confirmation
  • Drift and supersession protection
  • Post-restore verification
  • Activity history and realtime session refresh

This is controlled rollback for supported PROVEN changes, not universal Undo. Woo billing and webhook/monitoring parity remain outside the current public state.

Controlled rolloutShopify

Product-level apply

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.

  • Identifiable prepared plan
  • Targets kept separately
  • Pre-publish recheck
  • Post-apply reconciliation

The implementation is in controlled rollout; live Shopify certification for the new product-level apply surface is still pending closure.

05 · Monitoring & Recovery

Catalog quality does not end after cleanup.

Monitoring keeps findings aligned with relevant changes, while recovery keeps uncertain states explicit.

The catalog keeps changing. Control should continue too.
Platform-specificShopify

Continuous catalog monitoring

PROVEN can recheck relevant catalog changes, including changes made outside PROVEN, so findings stay aligned with the current state.

  • Targeted rechecks
  • Fresh Shopify read-back
  • Open / resolve / reopen
  • Separate reconciliation path

Monitoring does not automatically start remediation or publish another change.

AvailablePROVEN

Uncertain states are not hidden behind “Error”

Controlled flows can distinguish stale, partial, retryable, unverified, or recovery-required outcomes instead of collapsing every failure into one generic state.

  • Partial outcomes
  • Retryable failures
  • Recovery-required state
  • Convergence after supported operations

06 · Audit & Authority

Know who acted, on which target, and with what outcome.

Audit and authority preserve forward/reverse context, role separation, and the boundaries around sensitive operations.

The reason for a change does not disappear after the change.
Platform-specificShopify

Controlled rollback, not “undo anything”

For supported Shopify mutation families, restore uses factual prior-state evidence and can refuse the operation when drift or a later change makes restoration unsafe.

  • Title and description
  • SEO title and description
  • Media ALT
  • Image source
  • Drift and supersession protection
  • Explicit product-level rollback selection

Product-level rollback for eligible targets is implemented in controlled rollout: it requires preflight and explicit selection and can refuse drift or supersession. Real-store validation is still pending; it is not “undo the whole product”.

AvailablePROVEN

Audit that preserves operational context

PROVEN keeps track of who acted, which target was affected, the outcome, operation correlation, and separate forward/restore events where supported.

  • Actor and authority context
  • Target and outcome
  • Operation correlation
  • Forward change and restore as distinct events
AvailablePROVEN

Authority separated by role and context

Platform administration, merchants, and agencies do not share one global administrator role. Access is evaluated in the context of the store, relationship, and required permission.

  • Platform / merchant / agency separation
  • Store isolation
  • Explicit permissions
  • Revocation and revalidation

07 · Multi-store & Agencies

Operate across clients without merging their authority.

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.
Controlled rolloutShopify

Agency multi-store without merging clients

One agency can administer multiple stores with roles, store scope, controlled assignment, and contextual audit without merging client authority.

  • Agency Admin / Operator / Viewer
  • Store scope
  • Assign / release / reassign
  • Cross-agency isolation

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.

Platform-specificShopify

The agency–store relationship stays visible to the merchant

The merchant can see the active management relationship and support/dispute path without gaining assign, release, or reassign authority from that surface.

  • Active agency name
  • Relationship state
  • Support path
  • No merchant mutation authority

08 · Media Operations

Metadata and the image file are different 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.
Platform-specificShopifyWooCommerce

ALT is a catalog operation, not image compression

PROVEN keeps ALT metadata problems separate from image-file operations so each type of change preserves the correct permission boundary.

  • ALT detection
  • ALT remediation on supported flows
  • No automatic invention of missing facts
Platform-specificShopify

Controlled image-file optimization

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.

  • Original + optimized artifact
  • Replace only when beneficial
  • Live revalidation
  • Verification, backup and controlled rollback
Controlled rolloutWooCommerce

Woo image-file optimization is in controlled rollout

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.

  • Prepare and confirm
  • Publish + read-back verification
  • Recovery state
  • Controlled restore of the original association
  • Progress and savings without manual refresh

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

AI and pricing stay under platform 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.
AvailablePROVEN

AI under control, not in control

Providers, models, budgets, and cancellation are managed separately from merchant permissions, while model output passes independent validation before it can enter a remediation flow.

  • Provider/model control
  • Bounded input context
  • Budget admission
  • Cancellation
  • Independent validation
AvailablePROVEN

Versioned pricing and entitlements

Access, limits, and operation pricing are designed to come from versioned commercial authority rather than constants scattered across the interface.

  • Versioned Pricing Catalog
  • Dynamic entitlements
  • Fix Credits
  • Reservation and accounting for supported operations

10 · Platform Integrations

PROVEN is the product. Platforms are 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.
Platform-specificShopify

Shopify is the deepest commerce integration

On Shopify, PROVEN combines catalog intelligence, controlled remediation, bulk workflows, monitoring, rollback, image operations, Agencies, billing, and audit in the same operating model.

  • Embedded commerce app
  • Current-user authority
  • Monitoring
  • Rollback
  • Agencies
  • Facturare
Platform-specificShopify

Sidekick for review and handoff, not catalog changes

Shopify Sidekick can receive a limited read-only catalog-quality view and open the relevant context in PROVEN.

  • Read-only review
  • Product/finding context
  • Handoff into PROVEN

Sidekick does not confirm, publish, or execute remediation.

Platform-specificWooCommerce

WooCommerce: detection + controlled operator and merchant 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.

  • Preview before change
  • Explicit confirmation
  • Current-state protection
  • Read-back verification
  • Post-change rescan
  • Read-only activity history for applied changes

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

The same feature checklist does not mean the same operational authority.

A point-solution stack can detect, edit, monitor, and restore data in different apps. PROVEN keeps the problem, decision, change, verification, and recovery connected.

Fragmented stack
  • Audit app
  • AI writer
  • Bulk editor
  • Image optimizer
  • Monitoring app
  • Backup / rollback app
  • Spreadsheet / manual QA
PROVEN
  1. 01Finding
  2. 02Decision
  3. 03Remediation
  4. 04Mutation
  5. 05Verification
  6. 06Monitoring
  7. 07Recovery

Point solutions can share the same feature checklist. They do not automatically share operational truth.

Platforms

The same PROVEN model, a different integration.

Capabilities are declared separately by platform. A capability existing on Shopify does not automatically make it available on WooCommerce.

Deep integration

Shopify

The deepest commerce integration: remediation, controlled bulk, monitoring, rollback, media operations, Agencies, billing, Sidekick, and audit.

Explore Shopify workflows
Active integration

WooCommerce

PROVEN 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 WooCommerce

Explicit boundaries

PROVEN also says what it does not do.

Control is valuable only when the boundaries are as clear as the capabilities.

  • It does not invent missing catalog facts.
  • It does not turn ambiguity into an automatic correction.
  • It does not publish an AI proposal merely because it was generated.
  • It does not call a change verified merely because the endpoint returned success.
  • It does not fabricate a global health score or improvement percentage without factual authority.
  • It does not claim support for ecommerce platforms that are not integrated.

From reference to context

See what PROVEN finds in a real catalog.

Use Try PROVEN for public signals or review current pricing to estimate the next step.