Draft orders do not measure every abandoned checkout
The two counts can represent different moments and different populations. WooCommerce's current documented block-checkout behavior stores early form interaction in the session and creates a fresh draft at Place Order. An eligible pending or failed order may be reused, and inactive drafts are cleaned up. A count of checkout entries therefore need not equal the Draft orders visible later. Establish the installed version, checkout type, event definition and observation window before calling the gap lost database records.
For: A research-only store owner comparing checkout-start counts with the Draft orders currently visible in WooCommerce.
Opening checkout and creating an order are separate events
The WooCommerce documentation checked on September 29, 2026 describes fresh block-checkout interaction as session state until the buyer attempts to place the order. A page load or an ordinary field edit does not itself create a fresh draft under that documented behavior. Someone can reach checkout and leave before the point where a draft is created.
Start with the definition behind your checkout-start report. Establish whether it counts a page visit, a particular form action or a submission, and whether it counts events, sessions or distinct people. Use the configuration or records of the measurement you actually run. The report's label alone does not answer these questions, and this page does not assume a particular analytics tool is installed.
If the counted action happens before Place Order, the absence of a draft can be consistent with the documented creation point. That is a reason to correct the comparison, not evidence that every unrecorded checkout was healthy. Your other observations may still reveal a real obstacle.
Pin the behavior to the version and checkout in use
Record the WooCommerce version and whether the assigned checkout uses blocks, a classic shortcode or another implementation. The current documentation is not a claim that every historical WooCommerce release created drafts at the same point. A guide describing an earlier release cannot settle what your installation does now.
Separate fresh checkout attempts from retries of existing orders. The current documented flow can reuse an eligible pending or failed order already in the session. A new submission is consequently not guaranteed to produce a new distinct draft ID. Use existing order references and dated records to establish whether reuse occurred in the cases you can trace.
When your installed version or customization's creation point is unconfirmed, mark that as an open dependency. Do not change cleanup settings or commission a database repair to satisfy an assumed one-draft-per-visit rule. First obtain the version-specific behavior from the maintainer or documentation for that installation.
A current Draft list is not a historical checkout counter
The Draft view shows orders in that state when you inspect it. WooCommerce documents scheduled daily cleanup of inactive drafts. It also distinguishes Draft from Pending payment, Failed and other order states. A later status-filtered list cannot establish all drafts or submissions that existed earlier.
Record both the period covered by the checkout-start report and the time you read the Draft list. Also preserve the filters used in each. Checking a present-day list against last week's event total mixes a historical count with a surviving-state snapshot unless you have records that bridge the two.
Do not subtract the current Draft count from checkout starts and label the remainder lost orders or abandoned buyers. That subtraction includes differences in creation point, reuse and later record state. Without a compatible definition and historical evidence, its meaning remains unknown.
Choose the next investigation from the evidence you have
If the start event precedes draft creation, retain it as a measure of that earlier action and stop expecting draft equality. If you have genuine place-order evidence, compare the traceable attempts with existing order references, including reused orders and later statuses. If only today's Draft list survives, report that limitation rather than reconstructing vanished history from a guessed count.
A specific submission with an unexplained missing record is a narrower investigation than a mismatch between two totals. Preserve its time, checkout path, installed versions and non-sensitive error wording for the maintainer. A draft or submission count still does not establish whether the payment provider received or completed a payment.
For a Prism checkout-review consultation, summarize the two definitions and the remaining discrepancy. Include the website, research-only products and question, with no customer records, credentials or payment details. Any measurement investigation or implementation requires an agreed scope, responsibilities, fees and terms. Email follow-up to an inquiry is not a booked appointment, service purchase or processing application.
Checkout-count definition map
Complete this from the real installation and reports. Use anonymized observations, not customer sessions or personal data. Compare counts only after the creation point, counting unit and time window are known. An unknown row identifies what must be established before the difference can be interpreted.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Checkout-count definition map. The last column is for temporary notes.
Definition to establish
Evidence to use
Consequence for comparison
Your definition or finding
WooCommerce version and checkout type
Evidence to useInstalled version record and the checkout implementation actually assigned.
Consequence for comparisonApply the documented creation behavior for that installation; do not generalize current block behavior to every release.
Checkout entry event
Evidence to useThe actual event trigger and report definition.
Consequence for comparisonState whether it observes entry, interaction or submission and whether it counts events or distinct sessions.
Place-order attempts
Evidence to useExisting dated submission evidence, with personal data removed from your summary.
Consequence for comparisonDistinguish an attempted submission from simply entering checkout.
Draft creation point
Evidence to useVersion-specific behavior for a fresh checkout.
Consequence for comparisonCurrent documented blocks create a draft at Place Order; earlier interaction alone does not require a draft.
Prior order reuse
Evidence to useExisting pending or failed order references associated with traceable retries.
Consequence for comparisonA reused order prevents a reliable one-new-draft-per-attempt assumption.
Comparison time range
Evidence to useStart, end and timezone of the report, plus the time the Draft view was read.
Consequence for comparisonA historical event count and a present-state list need an explicit bridge.
Status filters and cleanup
Evidence to useThe selected order statuses and available evidence of later state or scheduled cleanup.
Consequence for comparisonAbsence today does not identify whether a draft never existed, changed state or was cleaned up.
Decision from the gap
Evidence to useThe definitions above and any individually traceable submission.
Consequence for comparisonChoose a corrected measurement, an unresolved evidence gap or a specific missing-record investigation.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
Fresh draft creation at Place Order describes the current documented WooCommerce block flow, not every version, classic checkout or customization.
Drafts, analytics events and payment-provider results are separate evidence. Their counts do not establish completed payments or the cause of abandonment.
This worksheet supplies no missing-event estimates or conversion benchmarks. Keep personal data and payment secrets out of it.
Current WooCommerce order-status and draft behavior — checked 2026-09-29. Current documented fresh block checkout keeps early interaction in the session and creates a draft at Place Order, can reuse eligible pending or failed orders, and schedules inactive-draft cleanup. The behavior must be bounded to the applicable version.
Prism solutions — checked 2026-09-21. Published support is storefront review, processing preparation and help with provider website questions. Scope, fees and terms are discussed before work; providers decide eligibility.
Prism contact — checked 2026-09-21. The form asks for the website, products and question without sensitive records. Email follow-up does not book an appointment, purchase a service or submit a processing application.