Fix the checkout or rebuild the store?

A checkout page can change without a new catalog

WooCommerce stores started after version 8.3 use the Cart and Checkout blocks by default. The cart and checkout documentation shows how to transform those blocks to the classic shortcode, and it says to change both pages together. That is a change to the cart and checkout pages. It is not a new product catalog and it is not a new legal entity.

The system status report lists the checkout page separately from the theme, the plugins, and the product post count. Use that separation. If the only documented failure is on the checkout page, say so. If you have not checked the other pages, say that the rest of the store is untested rather than calling the project a rebuild.

An incompatible extension is a checkout fact

If the only enabled payment gateways are incompatible with the Checkout block, WooCommerce says no payment method is available and a warning is shown. Compatibility for an extension on WooCommerce.com is marked on its product page. Extensions that add checkout fields with the older hooks usually need integration work before they work with the blocks.

That fact can justify a narrow change: use a compatible extension, or revert cart and checkout to the classic shortcode the documentation describes. It does not justify assuming the catalog, policies, or hosting are the cause. It also does not say which option a provider will accept. Compatibility and account eligibility are different questions.

Template overrides and failures outside checkout widen the scope

The system status report lists files that override WooCommerce templates, including a checkout template when one is overridden, and it says there is no standard for what a theme may do. It also says that if a problem disappears while the Storefront theme is temporarily active, the active theme is involved. That is a diagnostic WooCommerce documents. It is not an instruction to adopt Storefront, and it is not a decision to rebuild.

A failure that also appears on the catalog, the account page, or content pages is not confined to the payment extension. Product data can be exported and imported as CSV, which is a catalog task, not a checkout-page task. Once the theme or the catalog is in scope, ask the implementer to price that larger list. Do not keep the smaller label if the list has grown.

What makes each job bigger or smaller

A quote is comparable only when it says what it assumes. The questions below apply to any proposer, including Prism. They are not a list of what every job includes, and none of them produces a price or a duration on its own.

For a checkout job, the size follows the components involved. Ask which gateway and extensions must support the checkout type you keep, whether custom checkout fields were added with the older hooks WooCommerce says usually need integration work for the blocks, whether the theme overrides checkout templates, and whether the cart has to change with the checkout, since WooCommerce documents the two as a pair.

For a rebuild, the size follows what has to be produced and handed over. Ask who supplies a finished logo and product images and what happens if they are missing, whether the layout is a standard design or bespoke work, which store features are included, such as order emails, abandoned-cart recovery, customer records, shipping tools, or affiliate tools, whether the checkout will be hosted or embedded, how many revision rounds are included, and what the handover covers.

Two questions apply to both: what timing the quote assumes and what a changed deadline would affect, and what the written payment schedule covers. If products, customers, or orders must move to another site, the job includes a migration, and each of those records needs its own line in the scope.

Cost, timing, and eligibility stay blank until the right party answers

You can decide whether the evidence you have is limited to the checkout page and the payment extension. The implementer decides the work it will quote. The provider decides whether a gateway or account change is eligible. Nobody on this page can turn a symptom into a price, a duration, or an approval.

Before quoting a fix, Prism inspects the integration. It does not require a rebuild or a change of processor by default, and it does not promise that a smaller job will resolve the problem before the evidence shows it. When the evidence points at the wider store, the build, completion, or move is scoped as its own job. Supported platforms and payment arrangements are confirmed in the consultation, and Prism confirms scope, responsibilities, fees, and terms before work begins.

In the consultation request, include the platform, the failing behavior, whether other pages show the same failure, any theme or template overrides you know of, and a short summary of any quote you already have. Leave out logins, API keys, and customer data.

Checkout or wider-store matrix

In the last column, note the evidence you have and any quote you have actually received. Leave the quote blank until someone who would do the work provides it.

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.