Oneguard for WooCommerce

FAQ

How does age verification work in WooCommerce?

Select the relevant products and set a minimum age. When an affected order is placed, it stays on hold while the customer follows the guided check on their phone. Oneguard then returns the result and updates the WooCommerce order automatically.

Which products can I restrict?

Age verification can be enabled for individual WooCommerce products. Each product can have its own minimum age, or you can use one global default.

Is this plugin free?

Yes. The WordPress.org launch version includes a free Oneguard plan with no monthly or per-verification fee. The plugin does not collect payment details in WordPress.

Does the plugin require WooCommerce?

Yes. Oneguard for WooCommerce requires WooCommerce for product and order verification.

What does the customer experience look like?

Customers complete the normal checkout first. If the order contains a restricted product, they receive a clear link to the mobile Oneguard flow. The guided steps explain what to do, and the result is sent back to WooCommerce automatically.

What happens while verification is pending?

The affected WooCommerce order stays on hold. Once the required check succeeds, Oneguard updates the order automatically so fulfillment can continue.

Does the plugin support WooCommerce HPOS?

Yes. Oneguard for WooCommerce declares compatibility with WooCommerce High-Performance Order Storage.

Which languages are supported?

The plugin includes German and English messages. Customers in German-speaking billing countries receive German messages; other detected countries receive English.

Does this plugin guarantee legal compliance?

No. Oneguard provides age-verification tools, but requirements vary by product, country, and business. Shop operators remain responsible for deciding which verification and fulfillment measures apply to them.

Does Oneguard use an external service?

Yes. The age check is performed by the hosted Oneguard service after the shop operator activates the free plan. This connection is required for the plugin’s main functionality.

When a shop is connected, the service receives the site and home URL, domain, shop name, admin email, WordPress, WooCommerce, and plugin versions, plus the configured default age and verification expiry.

For an affected order, the service receives the information required to perform and return the age check: order ID, number and date; customer email, phone number, name, billing address and locale; return URL; required age; selected check method; and restricted-product details. Oneguard returns the verification ID, status, verification URL, expiry date, diagnostics, and selected result fields when available.

When the shop operator configures name or address rules, those rule values are stored in the Oneguard middleware. Billing and shipping names and addresses are sent to the middleware when an order is evaluated against active rules. Verification evidence remains on the hosted verification service and is fetched only when an authorized WooCommerce administrator opens the order details in the age-verification overview.

The service is operated by OneGuard GmbH, Welserstraße 3, 87463 Dietmannsried, Germany.

• Service website: https://oneguard.app/
• Terms of service: https://oneguard.app/terms/
• Privacy policy: https://oneguard.app/privacy/

Which verification data remains in WordPress?

WordPress stores the verification ID and status, required age, expiration date, and the necessary order, customer, and restricted-product references. After a successful check, selected result fields such as document number and type, birth date, and calculated age may also be stored when Oneguard returns them.

WordPress does not persist document images, face images, selfie videos, biometric raw data, OCR raw data, or full names and addresses read from the identity document in the plugin database. Authorized WooCommerce administrators can view available evidence on demand; it is transmitted for that request but remains stored by the external verification service.

Records in the plugin’s verification table remain until the plugin is uninstalled. Verification metadata attached to WooCommerce orders follows the shop’s normal WooCommerce retention and deletion process.

How is the connection protected?

Protected requests use a secret assigned to the individual shop. Signed callbacks include a timestamp and one-time value; the plugin rejects stale, duplicate, invalid, or mismatched callbacks.