Skip to content
Vraimony
WooCommerce Plugins — Two tools, one goal

Know if your case is ready.
Then build it to win.

The free scanner tells you what is missing before you submit. The paid builder turns your order into a complete, reviewer-ready case.

WooCommerce 6.0+ HPOS compatible DNR · SNAD · Refund · Friendly Fraud
Proactive model — install once

Every WooCommerce order documented before a dispute happens.

The plugin runs browser-first and WordPress-first: cases, uploads, template routing, and guided fixes happen inside Woo admin before anything reaches the server. Same-server sync only. No third-party AI providers.

🛒
order.created

Hash buyer, items, price, address

📦
order.shipped

Hash tracking, carrier, date

order.delivered

Hash confirmation, carrier scan

dispute_opened

Case assembled instantly

Privacy principle: The plugin only sends hashes to Vraimony — never raw order data, customer names, or PII. All hashing happens in the browser or WordPress layer before transmission.
POST /v1/proactive/record
{ "source": "woocommerce", "event": "order.shipped",
"order_id": "WC-4521", "content_hash": "sha256:3a4b…" }
Free — WordPress.org

Woo Dispute Readiness Scanner

Shows what you have and what is missing — inside the order screen, before you submit anything.

Vraimony Dispute Readiness Scanner
78%
Moderate — 1 critical item missing
DNR (Did Not Receive) · Order #4521
MUST Carrier tracking record
MUST Delivery confirmation
MUST Order confirmation + billing
STRONG Transaction ID on record
Delivery confirmation missing — obtain from carrier before submitting.
  • 📊Dispute type detection — auto-detected from order data
  • 📋Evidence checklist: MUST / STRONG / HELPS, auto-checked against WC data
  • Missing items with plain-English "what to collect next"
  • 📅Case timeline built from order dates — gap warnings included
  • 🏷Readiness badge on orders list — triage at a glance
  • 🔒Zero data leaves your server — all analysis runs in the browser
  • No account, no API key, no subscription

Pending WordPress.org review. Install via Plugins → Add New → search "Vraimony Dispute".

Side by side

Free Scanner vs. Paid Case Builder

FeatureFree Scanner
Dispute type detection
Evidence checklist (MUST/STRONG/HELPS)
Missing items list
Timeline with gap warnings✓ basic
Readiness badge on orders list
Sealed record (ed25519)
Reviewer-facing link (no login)
QR verify code
PDF / JSON export
Redaction-ready outputs
Before/after time metrics
Data leaves your server?Never
Account required?No
PriceFree
How the funnel works

Scanner finds the gap. Builder closes it.

Chargeback arrives

Open the order. The Scanner shows your readiness score, missing evidence, and timeline gaps immediately — no setup.

Collect what is missing

The missing-items list tells you exactly what to gather — tracking screenshot, delivery confirmation, policy record — before submitting.

Build the sealed case

The Case Builder turns your order + collected files into a sealed, structured record. Timeline auto-built. Evidence mapped. Reviewer link generated.

Start now — no account needed

Install the free scanner. See your readiness score in 30 seconds.

Diagnostic integration

Automation now starts from fault detection, not only workflow routing.

Scan first

Run the deterministic scan to identify the dominant fault before drafting replies.

Repair routing

Route the case to the correct repair protocol instead of treating every dispute the same.

Reviewer simulation

Check whether the bundle is likely to survive outside review before sealing or exporting it.

Local-first plugin shell

Four screens. Same-server only. Browser-heavy by default.

Cases

Open a case, track readiness, resume local snapshots.

Upload

Triage, quality gate, bundle verdict, and template routing in the browser.

Templates

Starter vs deep paths from same-server template packs. No third-party routing.

Settings

Only your server, your verify origin, and your fallback policy. No provider marketplace.
Recommended onboarding: Connect your Vraimony server → choose main workflow → open first case → run first browser-first readiness check.