WooCommerce Administration
v2.20.8 · GPLv2+ · Built for WooCommerce

Precision control
for your WooCommerce store.

Administration controls, order safeguards, webhook infrastructure, operational tooling, and a read-only batch API — designed to keep complex WooCommerce stores predictable.

Explore capabilities ↓ View API ↗
CONTROL LAYER ACTIVE
◈ DEDICATED WEBHOOK QUEUE
Settings / Useral
Order Status Locked Manual changes protected
Webhook Queue Operational Dedicated delivery pipeline
Admin Controls 6 Policies Server-side enforcement
Batch API Read Only Order status lookup
5.8+ WordPress requirement
7.4+ PHP requirement
2.20.8 Stable release
6+ Major control domains
Overview

One control layer.
Multiple operational surfaces.

Useral extends WooCommerce with focused administration controls, order protection, webhook infrastructure and developer-facing operational tools — without interfering with programmatic workflows that need to keep running.

01
⌘

Admin Controls

Control product and order creation screens, attribute management, and other administrative actions with server-side enforcement.

02
◫

Order Management

Protect order status and notes while keeping payment gateways, integrations, APIs and automated workflows operational.

03
↯

Webhook Infrastructure

A dedicated delivery queue with retry, recovery, spacing, coalescing and operational visibility.

04
{ }

Batch API

Read the current status of many orders through a single, authenticated and read-only REST endpoint.

05
₿

Test Gateway

Run realistic checkout flows with configurable successful and failed payment outcomes for end-to-end testing.

06
◌

Operational Safety

Keep manual administration predictable while allowing supported automated processes to continue working normally.

Administration controls

Protect the UI.
Keep the automation.

Useral separates manual administrative restrictions from programmatic WooCommerce workflows. The result is a controlled admin experience without unnecessarily blocking integrations, APIs, scheduled jobs or payment processes.

✓ Create-product and create-order screens can be blocked
✓ Product attribute deletion can be protected
✓ Manual order-status changes can be locked
✓ Manual order-note deletion can be restricted
✓ Payment Type can be surfaced in the order list
✓ Completed status label can be customized
Useral Controls
Settings → Useral
Lock order status Protect manual status changes
Lock order notes Prevent manual note deletion
Lock attribute deletion Protect attributes and terms
Restrict create screens Control new products and orders
Webhook infrastructure

Delivery built as
its own pipeline.

Useral uses a dedicated queue for its webhook delivery workflow, with operational controls for retries, recovery, spacing, coalescing and visibility.

01 / EVENT
WooCommerce Event Order and customer activity enters the delivery workflow.
02 / COALESCE
Request Coalescing Repeated internal save hooks can collapse into one delivery.
03 / QUEUE
Dedicated Queue Delivery is tracked independently with explicit states.
04 / DELIVERY
Retry & Recovery Failed and stuck jobs can be retried and automatically recovered.
Dedicated delivery queue

Own queue storage and scheduling provide an isolated delivery workflow for Useral webhooks.

Retry & recovery

Retry individual failed rows or run all failed deliveries. Jobs stuck in Running can be recovered automatically.

Per-person exclusion

Store managers can exclude customer and order webhooks for specific users. Guest orders remain unaffected.

Delivery spacing

Configure a minimum gap between deliveries for the same order or person without delaying unrelated webhook traffic.

Order re-verification

Recent orders can be re-announced when they remain in selected statuses, with configurable timing and look-back rules.

Queue observability

Pending, Running, Completed, Failed and Blocked states are visible from the Useral webhook queue screen.

Read-only API
GET /wp-json/useral/v1/orders/status-batch

Query order status
at scale.

Fetch the current status of many orders in one authenticated request. The endpoint is intentionally read-only and does not change order state.

✓ Explicit order ID lists
✓ Modified-after filtering
✓ Current-status filtering
✓ Combinable filters
✓ Authenticated read-only access 
$ curl -X GET \
  "/wp-json/useral/v1/orders/status-batch?ids=1024,1025,1026"

// response

{
  "orders": [
    {
      "id": 1024,
      "status": "processing"
    },
    {
      "id": 1025,
      "status": "completed"
    },
    {
      "id": 1026,
      "status": "on-hold"
    }
  ]
}
Testing workflow

A payment gateway
made for testing.

Useral Test Gateway provides a realistic WooCommerce checkout flow for end-to-end scenarios. Choose a successful or failed outcome from an internal test screen without connecting to a real payment processor.

Classic Checkout Block Checkout Success / Failure Configurable Fee User Restrictions
Test Checkout Useral Test Gateway
Product subtotal $120.00
Test gateway fee $2.40
Total $122.40
✓ Successful payment
× Failed payment
Architecture

Clear boundaries.
Predictable behavior.

Useral sits between WooCommerce administration and the operational workflows that need additional control, while preserving supported automated paths.

W
WooCommerce Store foundation
U
Useral Controls Rules & safeguards
↯
Delivery Queue Reliable webhook flow
API
Integrations External workflows
FAQ

Built for real
WooCommerce operations.

Yes. The restrictions are enforced server-side, so direct navigation to the protected admin screens is blocked while the corresponding controls are enabled.
No. The lock targets manual administration paths. Supported programmatic status changes from payment gateways, integrations, REST/API clients and scheduled workflows can continue to operate.
Yes. Useral extends WooCommerce functionality and has no effect when WooCommerce is not installed and active.
The primary settings are available from Settings → Useral in the WordPress administration area.
Yes. The batch endpoint reads order information and returns current statuses. It does not modify order status or other order data.
Yes. A store manager can exclude that user's customer and order webhooks. Orders placed by guests are not affected by this per-user setting.
No. The spacing rule is scoped to the same order or person. Unrelated webhook deliveries are not intentionally delayed by this setting.
The dedicated queue isolates Useral webhook delivery from unrelated background workloads and provides explicit queue states, retries, recovery and operational visibility.
The queue uses WordPress cron scheduling. For stores with low traffic or admin-heavy workloads, a regular system cron invoking WordPress cron can provide more predictable scheduling.
Latest release

Version 2.20.8

Stable tag
Webhook Queue Dedicated queue workflow with operational visibility and recovery capabilities.
Order Controls Stronger administration safeguards for status and order notes.
Payment Type Order-list payment gateway visibility with filtering and sorting.
Batch API Read-only status retrieval for multiple orders in one request.