An order before the cutoff may have a different payment time

Recover the wording for this order

Open the dated order confirmation and any retained version of the product, shipping or checkout statement shown at purchase. Copy the cutoff, the event it names, the time zone and any stated working-day, stock or payment condition. Keep each condition tied to the source that actually contained it. An internal packing rule is evidence of an operating practice; it does not by itself establish what was disclosed to the buyer.

If the public page has since changed, retain both versions separately. Do not use the newer wording as proof of the earlier promise. If the original cannot be recovered, say which version is missing. Conflicting checkout and policy statements should stay visible in the comparison, rather than choosing whichever one excuses the disputed dispatch.

Name each timestamp before comparing it

Record order creation, the relevant payment event and the time the store recorded that event. Preserve the original timestamp and zone alongside any normalized value. A provider event time and a later store notification time can describe different events; do not silently substitute one for the other. If the promise says payment confirmed but does not explain which confirmation, identify the available records and leave that ambiguity explicit.

WooCommerce’s current order-status documentation distinguishes Draft, Pending payment, On hold, Processing and Completed. Processing records payment received and fulfillment still due; On hold can involve outstanding payment confirmation. Completed is a store fulfillment state. Those labels do not collapse order creation, payment and carrier possession into one time. Read the dated notes and matched payment record rather than inferring an earlier event from the order’s current status.

For the current documented Checkout block behavior, a fresh draft is created at Place Order and an eligible earlier pending or failed order may be reused. Consequently, a creation timestamp needs its order history and checkout context before it is treated as this buyer’s decisive action. That documented behavior is not a claim about every older WooCommerce version or a customized checkout.

Make the comparison without rewriting the condition

If the retained promise expressly makes dispatch depend on payment confirmation before the cutoff, compare the documented confirmation event with that cutoff as well as any other stated conditions. An earlier order timestamp alone does not establish that all of those conditions were met. If the wording instead names order placement and states no such payment condition, a later payment time does not supply the missing wording.

Where the text is ambiguous, record the two event times and the precise phrase that prevents a clear conclusion. This is enough to identify a disclosure problem without claiming a legal resolution of the complaint. Fixing the wording for future orders is separate work and should preserve the evidence for the existing order.

Next compare the shipment commitment with the actual handoff evidence. Under the FTC rule’s definition, shipment is placing merchandise with the carrier. Label creation shows a preparation event; a store mark of Completed is a store record. Identify a carrier acceptance event or other evidence that actually establishes possession. If only a later carrier event is available, do not invent an earlier handoff time to close the timeline.

Give support a conclusion the records can carry

The internal conclusion should identify the published condition, the matching event and whether carrier handoff is evidenced within the stated shipment commitment. If one element is missing, name it. A cutoff dispute is not resolved by saying payment was late unless the records also establish that the promise used that payment condition.

Where the FTC shipment rule applies and the applicable shipment time cannot be met, the seller must follow the specified delay-consent or cancellation and prompt-refund handling. A routine status update does not replace that process. Preserve the actual buyer notice and any answer, and assign the fulfillment or support owner responsible for the next action. This comparison does not decide the rule’s applicability or stronger local rights.

If the checkout wording and operational timestamps conflict, bring that specific discrepancy to a Prism checkout-review consultation. Describe the installed checkout and the public promise without sending customer records. Scope, responsibilities, fees and terms must be agreed before work; an inquiry does not authorize a checkout change or promise resolution of the buyer’s claim.

Cutoff event comparison

Use one real order. Keep the original event timestamps and zones, then compare them on the same time basis. A supported conclusion needs both the wording applicable to this order and evidence of the event it names. Record unknown where either is missing.

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.

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.