Complete fictional sample · £250 net audit stage
Migration-readiness audit — Synthetic Store 001.
This page shows the structure and depth of the paid audit. “Synthetic Store 001” is a neutral test identifier created solely for this example; its configuration, order data, findings, and quote are fictional. Nothing here identifies a real business, is a client record, or promises that another store will have the same result.
01 Executive summary
Seven purchase-relevant sources were inventoried. Three depend on legacy Thank you or Order status customizations: a Google Ads conversion tag, a GA4 snippet, and a custom Thank you page block. The configured legacy GA4 snippet and Google & YouTube app both target GA4 and create a duplicate-source risk; whether both sources send a purchase event for the same order remains to be observed under the separate implementation.
Recommended path: retain and verify supported app integrations, retire the legacy Google scripts only after their replacement is observed, replace the unsupported page block, confirm customer-account domain alignment, document the merchant’s stated consent instructions, then record one controlled order under the separately accepted implementation.
Overall riskHigh — two revenue-critical destinations depend on legacy scripts.
Audit outputInventory, decision map, one risk rank per source, test plan, implementation-access list, and fixed quote.
Illustrative fixed quote£1,750 net before audit credit. If this quote is accepted within seven calendar days after it is sent, the £250 net audit fee is credited against the implementation price before VAT.
Illustrative timingThree business days after this written quote and scope are accepted, the required first payment is received, and the operator confirms in writing that all required implementation access and information are complete.
02 Current-source inventory
Every mechanism currently expected to run when an order completes:
| ID | Source | Mechanism | Destination | Owner / source risk |
|---|---|---|---|---|
| SRC-01 | Order status script wrapper | Additional scripts | — | Merchant / High |
| SRC-02 | Google Ads purchase tag | Inside SRC-01 | Google Ads | Marketing team / High |
| SRC-03 | Legacy GA4 purchase snippet | Inside SRC-01 | GA4 | Former developer / High |
| SRC-04 | Google & YouTube app | Supported app | GA4 | Merchant / Medium |
| SRC-05 | Meta app pixel | Supported app | Meta | Paid-media agency / Low |
| SRC-06 | Klaviyo integration | Supported app | Klaviyo | CRM team / Low |
| SRC-07 | Custom Thank you block | Unsupported page script | On-page widget | Merchant / Medium |
“Owner” identifies the party expected to approve the source decision. The source risk shown for every SRC item is separate from the cross-source findings ranked below.
03 Risk classification
| Rank | Finding | Affected | If unmanaged |
|---|---|---|---|
| High | Google Ads conversion depends on a legacy script | SRC-02 | Conversion signal can stop after the page upgrade. |
| High | Two GA4 purchase sources are configured; duplicate receipt is unverified | SRC-03 / 04 | Revenue can be inflated if both send, or fall to zero if the wrong source is retired. |
| Medium | No supported replacement is currently selected for the custom Thank you block | SRC-07 | The widget disappears after the upgrade. |
| Medium | Consent behaviour is undocumented | All tags | Events can fire or remain blocked under the wrong assumption. |
| Low | Customer-account domain alignment is unconfirmed | Destination links | Hardcoded Thank you links or callbacks can fail. |
04 Migration decision map
| ID | Decision | Replacement or action | Planned check |
|---|---|---|---|
| SRC-01 | Retire last | Remove only after every dependency is replaced. | Confirm no unlisted source remains. |
| SRC-02 | Migrate | Use the agreed supported Google integration. | Observe platform diagnostics on the controlled order. |
| SRC-03 | Remove duplicate | Retire after SRC-04 is observed. | One GA4 purchase under the agreed test condition. |
| SRC-04 | Retain | Confirm property link and record merchant consent instructions. | Observe identifier where exposed, value, and currency. |
| SRC-05 | Retain + verify | No planned configuration change. | Observe one purchase event where exposed. |
| SRC-06 | Verify continuity | No planned configuration change. | Observe the placed-order metric and agreed flow. |
| SRC-07 | Replace | Use a compatible app block selected by the merchant. | Render and functional check. |
Irreversibility warning: Shopify page-upgrade rollback is conditional and time-limited, and legacy scripts cannot necessarily be restored. The implementation records current settings and contingency steps but does not promise universal rollback.
05 Controlled test plan
- Use one agreed low-value product, payment method, market, and consent state. This example uses a consent-accepted path.
- Record the Shopify order identifier, timestamp, value, currency, and test conditions.
- Check GA4, Google Ads, Meta, and Klaviyo only through diagnostics each platform exposes.
- Check transaction identifier where exposed, value, currency, and known duplicate sources.
- Record platform delays or missing immediate diagnostics instead of treating them as a pass.
- Refund or cancel the order after the merchant confirms the evidence is sufficient.
One order verifies only the observed configuration at that time. It does not prove every future order, consent state, payment method, checkout path, attribution model, or platform report. This accepted consent-state test does not validate behaviour when consent is withheld; the service follows and records the merchant’s documented instructions rather than supplying a legal consent review.
06 Illustrative implementation quote
Fixed price£1,750 net before audit credit for the written scope shown here; third-party fees excluded.
Audit creditIf this quote is accepted within seven calendar days after it is sent, the £250 net audit fee is credited against the implementation price before VAT. If the credit applies, the implementation balance is £1,500 net. If it does not apply, the fixed price remains £1,750 net. A refunded audit fee cannot also be used as an implementation credit. This illustrative quote remains open for seven calendar days after it is sent.
PaymentIf the £250 net audit credit applies, £900 net is due before work and £600 net at handoff on the £1,500 net balance; if the credit does not apply, £1,050 net is due before work and £700 net at handoff on the £1,750 net price.
TimelineThree business days after this written quote and scope are accepted, the required first payment is received, and the operator confirms in writing that all required implementation access and information are complete.
Additional correction promiseAn additional 14-calendar-day correction promise from written handoff, at no additional service charge, for defects introduced by the implementation; it does not limit applicable statutory or written-scope rights and excludes third-party platform changes, changes by others after handoff, and items expressly documented as excluded, unresolved, or assumed.
Audit access usedRestricted read access to the Shopify upgrade report, implicated post-checkout settings, and listed source configurations; never passwords.
All displayed prices are net prices and exclude statutory VAT where applicable. A business day is Monday through Friday, excluding public holidays at the operator’s service address.
Implementation-access list for this example
- Restricted Shopify collaborator access to the post-checkout, customer-event, app, and test-order records implicated by the accepted scope.
- View or test access only to the named GA4, Google Ads, Meta, and Klaviyo destinations; no unrelated properties or billing access.
- A merchant approver for the documented consent instructions, replacement app block, test product, payment method, and refund or cancellation.
- No passwords, customer export, user administration, or unrestricted account access.
The minimum read access needed to produce the audit is requested after fit and payment. The list above is the separate implementation-access output; implementation access is not required until that quote is accepted.
07 Scope boundary and handoff
Excluded from this illustrative quote:
- Media buying, theme redesign, general CRO, and email-flow strategy.
- Legal review of the merchant’s consent policy or replacement of its consent platform.
- Server-side tracking, historical data repair, unrelated checkout development, and ongoing monitoring.
- Third-party app fees, subscriptions, the test-order cost, and changes introduced by other parties.
The separately scoped handoff would contain:
- Pre-change record and final source → mechanism → destination map.
- Decision log updated with the result of each approved change.
- Observed test evidence, duplicate-source review, open assumptions, and platform limitations.
- Contingency or reversal notes only where the platform permits reversal.
Ready to check a real store? The first message is a free fit check. The paid audit is £250 net for one standard-scope store.