Install once. Start from any Woo order, route the dispute path, and package evidence before friction grows.

Use the production wedge if your goal is Woo dispute readiness inside WP Admin.

This package is the sharper entry point: Case Inbox, Suggested Now trigger memory, Upload, Templates, Settings, local-first upload triage, local Woo timeline, checklist-fit scoring, bundle verdict, and same-server-only handoff into the deeper Vraimony workspace.

Listing kit ready for WordPress.org or direct distribution.

Use the ready-made icon, banner, six screenshots, listing readme, and publishing checklist to publish or hand off the plugin cleanly.

Install once. Reach the first useful result fast.

The plugin should feel like a paid workflow, not a template gallery.

The best template experience inside Woo Admin is job-first: start from the order or the uploads, let the plugin recommend the family, then open the smallest path that moves the case forward.

Pick the plan that matches how often the plugin will be used.

The plugin-first path now stays clearer commercially too: use One Case for one live order, Plugin Pro Monthly when the operator repeats the same workflow every week, and Plugin Pro Annual when order-aware case work becomes part of the normal Woo operation.

Four things that matter operationally.

• 🗂️
  Cases + Suggested NowSee the orders that likely deserve action now, dismiss noisy ones locally, and restore them later without losing the signal.
• 📤
  Order-aware upload bootstrapStart uploads from real Woo order context, not from a blank screen.
• 🧭
  Family templatesChargeback, delivery, refund, and payment-review paths each carry a clearer starter/deep checklist.
• 🔒
  Same-server only handoffKeep the heavy review path on your own server only when the local bundle is worth escalating.

What the customer sees in their order confirmation email.

Keep this as the secondary trust layer. The production wedge starts in WP Admin; the verify / receipt path remains useful when you want a lighter proof surface beyond the dispute workspace.

Chargeback received. Delivery disputed. Invoice rejected. Package the evidence automatically.

The plugin now starts from order context, keeps a small local Woo timeline inside the upload workspace, scores checklist fit as uploads arrive, suggests the sharpest dispute path before you even upload evidence, and loads a family-specific checklist automatically.

• 🔔
  Chargeback trigger — woocommerce_order_status_changed When order status changes to "Refund requested" or a chargeback note is added — auto-prompt appears in WooCommerce admin: "Package your evidence now → $19.99". Pre-fills order ID, transaction date, and item details.
• 📦
  Delivery dispute trigger — woocommerce_order_note_added When a customer dispute note is added to the order — the plugin generates a pre-structured delivery evidence prompt. Pulls shipping carrier, tracking number, and delivery timestamp automatically from order meta.
• 🧾
  Invoice rejection trigger — order status: on-hold / failed payment When payment is refused or invoice contested — prompt generates a review-ready pack with the original invoice, scope documentation from order notes, and delivery proof. One link for the buyer, bank, or platform reviewer. No email chain.

Two shortcodes. Drop into any page, post, or WooCommerce template.

Every order gets a Vraimony sidebar panel.

The Receipt ID (UUID) connects the WooCommerce order to the sealed Vraimony record. The Private Appendix stays in WooCommerce order meta — it is never sent to Verify or any external service.

Every order gets a score. Protected. Weak. Missing key proof.

The plugin analyses each WooCommerce order and assigns a readiness level — so you know before a dispute arrives, not after. No setup required. The score updates automatically as order events come in.

Works with any standard WordPress setup.

Requires: WordPress 6.0+, PHP 7.4+. WooCommerce required for order meta box and email footprint. Shortcodes work without WooCommerce.

Only the hash reaches Vraimony. Never the order data.

The plugin computes the order evidence snapshot locally inside WordPress. Only a SHA-256 hash of that snapshot is sent to Vraimony servers for sealing — not raw order data, not customer names, not addresses, not payment details. This is the same client-first architecture used across all Vraimony surfaces.

Use the plugin as a browser-heavy workspace before you ask the server to do more.

The new shell keeps cases, uploads, template routing, and local cache in the browser first. It only talks to your own Vraimony server when you choose to load template packs or hand off deeper work. No third-party providers. No remote runtime.