Title: Checkout Watch: Lost Sales Monitor for WooCommerce
Author: David Mansaray
Published: <strong>2026년 6월 19일</strong>
Last modified: 2026년 6월 21일

---

플러그인 검색

![](https://ps.w.org/checkout-watch/assets/banner-772x250.png?rev=3582161)

![](https://ps.w.org/checkout-watch/assets/icon-256x256.png?rev=3582354)

# Checkout Watch: Lost Sales Monitor for WooCommerce

 작성자: [David Mansaray](https://profiles.wordpress.org/davidmansaray/)

[다운로드](https://downloads.wordpress.org/plugin/checkout-watch.0.2.0.zip)

 * [세부사항](https://ko.wordpress.org/plugins/checkout-watch/#description)
 * [평가](https://ko.wordpress.org/plugins/checkout-watch/#reviews)
 *  [설치](https://ko.wordpress.org/plugins/checkout-watch/#installation)
 * [개발](https://ko.wordpress.org/plugins/checkout-watch/#developers)

 [지원](https://wordpress.org/support/plugin/checkout-watch/)

## 설명

Your WooCommerce checkout can look fine until an update, plugin conflict, payment
setting, shipping rule, or checkout change quietly blocks buyers.

[Checkout Watch](https://checkoutwatch.co/?utm_source=wporg&utm_medium=plugin&utm_campaign=intro)
helps store owners and agencies spot checkout warning signs before customers report
them. Start with a free local checkout health scan in wp-admin, then connect and
configure Checkout Watch when you want scheduled external checks, failure evidence,
and alerts between manual reviews.

The free plugin works without a Checkout Watch account. It stores the latest scan
result in WordPress and gives you a practical checkout-health baseline before or
after WooCommerce, plugin, theme, checkout, payment gateway, shipping, tax, or hosting
changes.

The free local scan can help you:

 * Run a manual local WooCommerce checkout health scan from wp-admin, with no Checkout
   Watch account required.
 * Get a prioritized report with critical issues, warnings, passed checks, recommended
   actions, and coverage gaps.
 * Check cart and checkout page setup, including assigned pages, checkout content,
   and server-side response checks.
 * Identify classic shortcode checkout, block checkout, or missing checkout content.
 * Run a no-order local add-to-cart dry run using an eligible simple in-stock product,
   then restore the previous cart items and coupons.
 * Check enabled WooCommerce payment gateways and payment methods WooCommerce makes
   available for a temporary test cart inside WordPress.
 * Review shipping, tax, WooCommerce fatal-log, WP-Cron, and general failed or past-
   due Action Scheduler warning signs.
 * See recent modification timestamps for active plugin main files, WooCommerce,
   and the current theme directory.
 * See a Checkout Protection Score and Not Protected labels for checks the local
   scanner cannot perform.
 * Use the admin dashboard, detailed report, diagnostics view, and copyable support
   summary.

For stronger protection, connect the store to [Checkout Watch](https://checkoutwatch.co/?utm_source=wporg&utm_medium=plugin&utm_campaign=monitoring)
and configure monitoring in the Checkout Watch app. Connected plans can run scheduled
cart-to-payment checks from outside WordPress, run on-demand checks, send alerts,
keep incident history, and provide checkout health reporting.

Connected plan features can include email alerts, failure screenshots, video replay,
Slack alert channels, longer evidence history, and deeper diagnostics where supported.
See [Checkout Watch pricing](https://checkoutwatch.co/pricing.html?utm_source=wporg&utm_medium=plugin&utm_campaign=pricing)
for plan details.

Connection is optional and is not required for the free local scan. Connection alone
does not start a monitoring schedule or choose alert recipients; finish setup in
Checkout Watch after connecting the store.

The Checkout Protection Score is a weighted summary of local scan findings and monitoring
gaps. It is not proof of checkout uptime, completed orders, payment authorization,
conversion performance, or revenue protection.

The free local scan does not create orders, submit or authorize payments, intentionally
change stock, verify payment webhooks, test checkout from an external browser, capture
screenshots, send alerts, or monitor continuously.

#### External service and data sharing

Checkout Watch offers an optional connection to the Checkout Watch service at [https://checkoutwatch.co](https://checkoutwatch.co/?utm_source=wporg&utm_medium=plugin&utm_campaign=service).
The free local checkout health scan works without this connection.

Running a local scan does not itself send data to Checkout Watch. If the store is
connected, Checkout Watch can later retrieve the filtered latest scan and checkout
test context through authenticated plugin endpoints.

When an administrator starts the optional one-click connection, the browser sends
the store URL, a short-lived request ID, a one-time verification code, and a source
label identifying the WordPress plugin to Checkout Watch. To complete the connection,
Checkout Watch calls the plugin’s verification endpoint. The plugin then returns
the store URL and name, plugin version, a connection access token, and the filtered
latest scan result.

After connection, Checkout Watch can use that access token to request an authenticated
store summary and checkout test context. This can include store URL and name, plugin/
version details, WordPress, WooCommerce, PHP and theme details, cart and checkout
URL information, checkout type, selected product details, store currency, payment
gateway identifiers/display names/availability details/mode labels, and filtered
scan findings, scores, timestamps, and support-summary data.

The plugin does not intentionally include payment gateway credentials or customer
payment details in these responses. Fields whose names indicate credentials, email
addresses, authorization data, card data, or database details are excluded, and 
recognized secret-key, email, and credential patterns in text values are redacted.

When monitoring is configured, Checkout Watch may also store test results and plan-
dependent evidence such as failure screenshots, video replays, incident records,
and reports for the evidence-retention period associated with the selected plan.

Generating a manual connection token does not by itself send store data to Checkout
Watch or complete service setup. Data becomes available after that token is supplied
to and used by the service.

## 설치

 1. Upload the plugin folder to `/wp-content/plugins/checkout-watch`.
 2. Activate Checkout Watch in WordPress.
 3. Open Checkout Watch in wp-admin.
 4. Run the first checkout health scan.

## FAQ

### Does the free plugin require a Checkout Watch account?

No. The local checkout health scan runs inside WordPress and works without a Checkout
Watch account. Connecting to Checkout Watch is optional.

### Will the cart dry run affect orders or stock?

The dry run does not create an order, submit a payment, or intentionally change 
stock. It temporarily replaces the current WooCommerce cart with one eligible product,
calculates totals, and then restores the previous cart items and coupons. Because
the scan uses normal WooCommerce cart logic, installed extensions and custom cart
hooks may also run.

### Does the scan prove real shoppers can complete checkout?

No. The free local scan checks warning signs from inside WordPress. It cannot prove
that an outside browser can complete the checkout path, that a payment can be authorized,
that an order will be created, or that payment webhooks are working.

Connected Checkout Watch monitoring can add scheduled external journey checks and
alerts for the checkout conditions it monitors. It still should not be treated as
a guarantee of checkout uptime, payment authorization, completed orders, conversion
performance, or recovered revenue.

### Does the free plugin continuously monitor my checkout?

No. The free plugin runs a local scan only when an administrator starts it from 
wp-admin. Scheduled checks and alerts are connected Checkout Watch service features.
The store must be connected and monitoring must be configured in Checkout Watch;
connecting alone does not start monitoring.

### What data is shared with Checkout Watch?

Running a local scan does not itself send data to Checkout Watch. Starting the optional
one-click connection sends the store URL, a short-lived request ID, a one-time verification
code, and a source label to Checkout Watch. When the connection is completed, the
plugin returns a connection access token and the filtered latest scan result.

After connection, Checkout Watch can use that token to request the authenticated
store summary and checkout test context described above. The plugin does not intentionally
include payment gateway credentials or customer payment details in this data. Sensitive-
looking fields are excluded, and recognized secret-key, email, and credential patterns
in text values are redacted.

### How does the local scan handle block checkout?

The scanner recognizes the WooCommerce Checkout Block and checks whether the Store
API cart endpoint responds locally. It does not prove that every enabled gateway
supports block checkout or that a shopper can complete the full checkout path. Review
each gateway’s compatibility and test checkout in a browser after WooCommerce, gateway,
theme, or checkout changes.

### What does Not Protected mean?

Not Protected is a coverage label for capabilities the local scanner does not perform.
It does not mean that passed areas are guaranteed or actively protected.

Not Protected can cover areas such as external browser checkout, payment authorization,
payment webhooks, screenshots, alerts, scheduled monitoring, and automatic checks
after updates. Connecting to Checkout Watch and configuring monitoring can close
some of those coverage gaps, depending on the plan and store configuration.

## 후기

이 플러그인에 대한 평가가 없습니다.

## 기여자 & 개발자

“Checkout Watch: Lost Sales Monitor for WooCommerce”(은)는 오픈 소스 소프트웨어입니다.
다음의 사람들이 이 플러그인에 기여하였습니다.

기여자

 *   [ David Mansaray ](https://profiles.wordpress.org/davidmansaray/)

[자국어로 “Checkout Watch: Lost Sales Monitor for WooCommerce”(을)를 번역하세요.](https://translate.wordpress.org/projects/wp-plugins/checkout-watch)

### 개발에 관심이 있으십니까?

[코드 탐색하기](https://plugins.trac.wordpress.org/browser/checkout-watch/)는, [SVN 저장소](https://plugins.svn.wordpress.org/checkout-watch/)
를 확인하시거나, [개발 기록](https://plugins.trac.wordpress.org/log/checkout-watch/)
을 [RSS](https://plugins.trac.wordpress.org/log/checkout-watch/?limit=100&mode=stop_on_copy&format=rss)
로 구독하세요.

## 변경이력

#### 0.2.0

 * Align the WordPress.org package slug and translation domain with `checkout-watch`.
 * Ship the full current local scanner source, including split admin views, diagnostics,
   scan sync, managed test assets, and coupon safety checks.
 * Refresh the WordPress.org listing copy and external service/data sharing disclosure.

#### 0.1.0

 * Initial release with local checkout scanner, admin report, diagnostics, Checkout
   Protection Score, Not Protected labels, and optional Checkout Watch connection
   flow.

## 기초

 *  버전 **0.2.0**
 *  최근 업데이트: **2주 전**
 *  활성화된 설치 **10보다 적음**
 *  워드프레스 버전 ** 6.4 또는 그 이상 **
 *  다음까지 시험됨: **7.0**
 *  PHP 버전 ** 7.4 또는 그 이상 **
 *  언어
 * [English (US)](https://wordpress.org/plugins/checkout-watch/)
 * 태그:
 * [checkout](https://ko.wordpress.org/plugins/tags/checkout/)[ecommerce](https://ko.wordpress.org/plugins/tags/ecommerce/)
   [monitoring](https://ko.wordpress.org/plugins/tags/monitoring/)[payments](https://ko.wordpress.org/plugins/tags/payments/)
   [woocommerce](https://ko.wordpress.org/plugins/tags/woocommerce/)
 *  [고급 보기](https://ko.wordpress.org/plugins/checkout-watch/advanced/)

## 평점

아직 제출된 리뷰가 없습니다.

[Your review](https://wordpress.org/support/plugin/checkout-watch/reviews/#new-post)

[모든  리뷰 보기](https://wordpress.org/support/plugin/checkout-watch/reviews/)

## 기여자

 *   [ David Mansaray ](https://profiles.wordpress.org/davidmansaray/)

## 지원

할 말 있으신가요? 도움이 필요하신가요?

 [지원 포럼 보기](https://wordpress.org/support/plugin/checkout-watch/)