Trace the missing total back to the assigned Checkout block

Establish which saved page supplies checkout

A page called Checkout in the editor is not sufficient evidence that the store uses it. WooCommerce requires the checkout page to be assigned under Advanced settings. Record that assignment and the public route before comparing the edit. If the page that was edited is different, you have an assignment discrepancy to resolve before attributing the buyer's missing summary to those edits.

On the assigned page, record the saved Checkout block and its totals inner blocks, including their order and the presence of Coupon Form. Keep the earlier saved structure or change record if it exists. An editor screenshot taken before saving establishes what someone was editing, not necessarily the content now supplying the live page. If the earlier structure is unavailable, state that limit rather than reconstructing an imagined before-state.

Apply the documented editing boundary

WooCommerce's Checkout block guide allows the totals inner blocks to be reordered. Within that set, Coupon Form is the only block documented as removable. A changed sequence can explain why a buyer looks in the old location and no longer finds a component there. Compare the full summary before classifying a line as absent.

Removing Coupon Form concerns the place where a buyer enters a coupon. It does not establish that other totals components were intentionally removed or that every displayed discount should vanish. Record coupon-form presence separately from the discount amount observed in the real cart. If the complaint is that an issued coupon is rejected, that is a coupon-rule investigation beyond this layout comparison.

These are the native block controls described by the guide. Do not interpret a missing line in a customized store as proof that WooCommerce exposes a normal remove control for that line. Also do not assume that a customized editor or extension follows the same controls. Record the installed WooCommerce version and the theme or extension involved so the maintainer can reconcile the actual installation with the documented behavior.

Compare the structure with the rendered summary

Use an actual reported cart state or a current observation on the store, without submitting a payment. Record the route, time, viewport and the exact label or amount that is missing or displaced. Retain only non-sensitive details. Comparing different cart states or different screen widths can obscure which change you are investigating; keep those conditions alongside both observations.

If a component appears in the saved structure but not where expected in the rendered summary, ask the maintainer to inspect the corresponding rendered element and relevant styling or template customizations. The useful distinction is whether the element is present but visually hidden, appears elsewhere, or was not rendered at all. These are investigation branches, not a diagnosis of the current store.

Link any confirmed customization to its actual rule, template or extension and its owner. A custom CSS rule or template override should be recorded only when found. If none has been identified, the cause remains open. Do not disable unrelated extensions or alter calculation settings solely because the problem followed an editor session. The timing identifies the change to examine; it does not prove its mechanism.

Accept the visible result only for the state checked

Resolve an assignment mistake at the assignment or editing surface, a documented reordering at the saved block structure, and confirmed custom hiding with the owner of that customization. After an authorized correction, compare the affected summary again under the recorded conditions. Confirm that the intended lines and total can be read before the payment action. Saving the editor alone does not establish that result.

A visible amount and a correct calculation are different findings. This check establishes where the summary appears and whether it is missing; it does not establish tax liability or prove shipping and discount rules. If the visible numbers themselves disagree with the genuine cart or order records, preserve that discrepancy for a calculation review.

For a Prism checkout-review consultation, describe the assigned route, the missing line and whether the saved block contains it. Confirm the scope of investigation or implementation, responsibilities, fees and terms before work. A working summary does not establish payment-provider eligibility for the research-only business.

Order-summary change record

Complete this for one reported summary change. Compare the saved structure and rendered page under recorded conditions. Use unknown where no earlier version or customization evidence exists. A row marked visible confirms display in that observation, not correct tax or payment calculation.

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.