UPLIFY11 checks

Demonstration report

A Merchant audit that checks the entire store before review

Interface status is a symptom, not a diagnosis. Site, schema, feed, Merchant and checkout are reconciled before blockers, risks and nonissues are named.

Evidence status: Demonstration report
Source: Synthetic, internally consistent data
Period: Synthetic readiness snapshot

The store, products and statuses are synthetic. The report does not promise Google approval.

Control snapshot

1,200 products 990 approved + 210 affected = 1,200
40 manually sampled all main groups
2 confirmed blockers before re-review
not ready verdict not a Google score

The 90 second view

Fix Align shipping cost and return window across site, feed and Merchant.
Verify Review affected items without treating low price as counterfeit proof.
Do not submit Do not request review until blocker closure is verified.

What was checked and where confidence ends

Sources

Home, product, cart, checkout and policies
Merchant information and diagnostics
Feed export and Product schema
Mobile journey without placing an order

Coverage

40 of 1,200 products, all policy routes, checkout to payment and account diagnostics.

Limitations

Supplier authorization for one risk group is unavailable. That is uncertainty, not proof of violation.

Measurement confidence

Readiness not ready

990 approved + 210 affected = 1,200 products. The decision rests on two open verified blockers, not a score.

11 checks

Full audit map

The three decisions above give an executive summary. The complete review register below shows the checks behind those decisions.

This page shows 11 of 11 checks in the demonstration register. A client report also links each check to its source, accountable role, and working artifact.

Check	Priority	Decision	What we established
01 11 steps before re-reviewConfirmed mismatches and acceptance criteria determine readiness, not a decorative score.
MC-01	P0	Align	Put delivery rules in one source table.	For two of four regions, the site, feed, and Merchant show different terms.
MC-02	P0	Align	Confirm the return period and cost.	The policy and Merchant conflict, while the product page does not explain the cost.
MC-03	P1	Verify	Match business name and legal details.	The site and Merchant should show the same data.
MC-04	P1	Verify	Reconcile price and stock for 40 products.	The sample covers all main groups and the mobile journey.
MC-05	P1	Investigate	Verify provenance for eight risk products.	Unusual pricing is a risk signal, not evidence of a violation.
MC-06	P1	Fix	Align GTIN, brand, and condition.	Identifiers are checked against the supplier source.
MC-07	P2	Protect	Do not create a new account or domain.	990 products are approved; the blockers are local and fixable.
MC-08	P2	Verify	Run mobile checkout up to payment.	Price, delivery, and currency must match the feed.
MC-09	P2	Document	Record an accountable role and proof for every fix.	A re-review needs a reproducible artifact rather than a promise.
MC-10	P2	Resubmit	Request review after both blockers close.	Early submission does not remove the rejection cause.
MC-11	P3	Monitor	Reconcile policies and feed data after every change.	Readiness can regress after delivery, price, or catalog updates.

Priority decisions with evidence

Fix before review

Shipping cost differs in three representations

Source: site, feed and Merchant. Period: synthetic snapshot. Status: confirmed consistency defect. Confidence: high. Coverage: four regions.

Observation: Two of four regions show different rules across site, feed and Merchant.
Decision logic: Buyer and Google see conflicting terms. A correct checkout does not remove the public mismatch.
Action and verification: The ecommerce manager, feed specialist and Merchant specialist align one shipping table. Acceptance: 4 / 4 regions match on site, feed, Merchant and mobile checkout.

Fix before review

The return window is inconsistent

Source: policy, product footer and Merchant. Period: snapshot. Status: confirmed content gap. Confidence: high. Coverage: all policy surfaces.

Observation: Policy and Merchant state different windows, while product pages omit return cost.
Decision logic: This is a testable consistency issue, not generic trust advice.
Action and verification: The business manager and legal lead confirm the actual terms. Acceptance: window, method, cost, refund timing and contact match and remain public.

Investigate

The risk group needs proof, not an accusation

Source: diagnostics, sample and manager input. Period: snapshot. Status: risk profile. Confidence: low. Coverage: 8 of 40 products.

Observation: Price and brand claims look unusual, but no direct counterfeit evidence was found.
Decision logic: Low price does not prove violation; a legitimate sale is plausible.
Action and verification: The business manager verifies origin securely. Acceptance: keep or remove decision documented without PII or credentials in the report.

What works and should not change

Preserve checkout and approved items

990 / 1,200 products are approved and checkout reaches payment.

Do not create a new account, feed or domain. Make durable fixes and recheck.

Target state and change rules

Target state

The site, feed, Merchant, and mobile checkout show the same terms, with both blockers closed by evidence.

How we test

Local QA is followed by a 40-product control sample before resubmission.

When we roll back

If the control sample finds another mismatch, resubmission stops and the change returns to the source owner.

The 7, 30 and 90 day plan

7 days

Close shipping and return blockers.
Owner
Ecommerce manager, feed specialist and Merchant specialist

Acceptance criteria
Shipping rules match for 4 / 4 regions across site, feed, Merchant and mobile checkout.
30 days

Recheck affected items and final render.
Owner
Merchant specialist

Acceptance criteria
No verified blockers remain.
90 days

Monitor feed drift and policy changes.
Owner
Merchant specialist

Acceptance criteria
The monthly review leaves no unexplained feed or policy drift, and every change has an owner and timestamp.

What the client receives

Evidence matrix
Site, schema, feed and MC consistency
Blockers, risks and nonissues
Fix register and recheck
Readiness without approval guarantee

Method and appendices

Site ↔ feed ↔ Merchant ↔ checkout matrix
40-product checklist and sampling rules
Blocker, risk, and non-issue register
Resubmission and monitoring log

Need to prepare a store for Merchant review?

We separate verified blockers from risks and verify fixes before the human decision.

Discuss an audit for your business