Start with the template overrides recorded in the real WooCommerce system status report, then reconcile each entry with the installed file and customization history. Record its location, the theme or extension whose template it replaces, the version information actually available, the reason for the difference and its maintenance owner. The status report identifies items to investigate at a point in time; it does not explain every modification or establish compatibility with future updates.
For: A research-only merchant receiving a WooCommerce store handoff or changing the team responsible for its theme and extensions.
Tie the template list to the store being handed over
WooCommerce's system status report records site addresses, installed versions, active plugins, the assigned checkout page and template overrides. Preserve a dated copy from the actual installation under discussion. Compare the site address and software versions with the handoff record so that a report from an earlier installation is not used to describe today's store.
Read the template entries separately from the plugin list. An inventory of installed extensions does not explain which template files have been customized. Keep the report as a snapshot: it records what was reported at collection time, not a promise that later changes will leave the list or behavior unchanged.
Reconcile each override with the actual customization
For every reported override, record the file's relative location and have the maintainer identify the default template it replaces. Distinguish the component providing the default from the theme or customization that holds the override. Then compare the actual file with the corresponding default for the installed version to describe the difference. A file path alone establishes a location, not the reason it was changed.
Look for the original change request, version history or contractor notes that explain the intended behavior. Record the affected store surface and the merchant's reason for keeping it. If no reason is documented, label the purpose unconfirmed and inspect the real behavior before deciding the override can be removed. Do not infer that unfamiliar code is unused.
Reconcile in both directions: every reported override needs a register entry, and each template customization named in the handoff needs a located file or an explanation of where it lives. An item absent from the status list is not automatically disproved. Keep it as a discrepancy for the maintainer to resolve rather than presenting the report as a complete inventory of all possible custom code.
Separate recorded versions from compatibility evidence
Record the installed WooCommerce, theme and relevant extension versions alongside any template version information actually present. If a file has no useful version marker, say so and identify the baseline used for comparison. The component's installed version and the customized file's recorded version are different facts; copying one into the other's field would hide uncertainty.
A version marker or absence of a warning does not prove that an override behaves correctly. Keep a dated record of the actual affected surface and what was observed. For checkout-related templates, describe the visible behavior that must survive maintenance, and keep provider payment evidence separate. Do not treat a page rendering successfully as proof that payment processing or every dependent control works.
Before an update, the owner needs the current override, its reason and the relevant upstream difference to decide what work is required. Do not instruct the incoming maintainer to delete the file or copy it forward solely because of its age. Both decisions need the specific difference and the behavior the merchant intends to preserve.
Assign responsibility for the next change
The handoff is usable when the next maintainer can locate the file, understand why it differs and identify who may authorize a change. Record who monitors the owning theme or extension, who reconciles template changes, and who checks the affected behavior afterward. If an outgoing contractor is the only person who knows the purpose, retain that as an open handoff item with a specific question.
Keep unknown purpose, missing files and unassigned maintenance visible when accepting the work. The merchant can distinguish a documented override with an owner from an override that remains an unresolved dependency. This is a narrower decision than declaring the whole theme compatible or the whole project finished.
For a Prism checkout-review consultation, describe the website, research-only products and the template-dependent behavior in question. Ask for the handoff or checkout investigation you need; scope, responsibilities, fees and terms are confirmed before work. Send an ordinary-language summary through the public form, not a full system report containing private site details. Follow-up is by email, and an inquiry does not buy maintenance, book an appointment or submit a processing application.
Template override register
Repeat this sheet for every reported override and each additional template customization named in the handoff. Use relative file locations and non-sensitive summaries. Leave missing evidence explicitly unresolved; a populated register records dependencies but is not a compatibility certificate.
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.
Template override register. The last column is for temporary notes.
Register entry
Evidence to locate
Interpretation for the handoff
Your record and owner
Status snapshot
Evidence to locateReport collection date, actual site address and installed software versions.
Interpretation for the handoffEstablish which installation the list describes and whether later changes need reconciliation.
Template location
Evidence to locateRelative path from the override list, reconciled with the installed file.
Interpretation for the handoffA missing file or unexplained path is an open item; do not substitute a similarly named file.
Owning theme or extension
Evidence to locateComponent supplying the default and the location supplying the override.
Interpretation for the handoffIdentify whose default must be compared and who maintains the replacement.
Recorded version
Evidence to locateAvailable template marker, installed component version and comparison baseline.
Interpretation for the handoffKeep these values separate; missing markers remain unknown rather than copied from the plugin list.
Customization reason
Evidence to locateActual difference, change request or history, and affected store surface.
Interpretation for the handoffState the behavior the merchant needs preserved; an undocumented reason is not permission to delete the override.
Observed behavior
Evidence to locateDated observation of the real affected page or existing operational record.
Interpretation for the handoffBound the observation to what was checked; a rendered page does not establish all checkout or payment behavior.
Maintenance owner
Evidence to locateNamed person responsible for upstream review, reconciliation and the affected behavior check.
Interpretation for the handoffRecord who may authorize the change and which task remains unassigned.
Unresolved handoff discrepancy
Evidence to locateCustomization notes not matched to files, or reported overrides without a documented purpose.
Interpretation for the handoffAssign a concrete follow-up question before marking that dependency understood.
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
WooCommerce's system status report is a snapshot. It does not establish the completeness of all customization records or automatic compatibility with an update.
Do not remove or replace a template solely from this register. The actual file difference, intended behavior and authorized maintenance scope govern that decision.
Technical template review does not establish provider eligibility or legal approval. Keep credentials, private server details, customer records and payment data out of the worksheet and public form.
WooCommerce system status report — checked 2026-09-21. The status report records site addresses, installed versions, active plugins, template overrides and the assigned checkout page. Those reported facts are a snapshot, not evidence of each customization's purpose or future compatibility.
Prism solutions — checked 2026-09-21. Published support includes storefront review, processing preparation and provider website questions. Scope, fees and terms are discussed before work; the provider decides eligibility and account terms.
Prism contact — checked 2026-09-21. The inquiry asks for the website, products and question, excludes payment details, passwords and customer records, and receives email follow-up. It does not book an appointment, purchase a service or submit a processing application.