# Revenue-risk sync QA packet: Multi-Store Sync Power

Sample proof-of-process artifact for a Shopify app vendor reliability packet.

## Boundary
This is a first-pass public-signal packet for the app vendor/operator. It does not claim private diagnosis, current production failure, vulnerability discovery, merchant access, or Shopify policy advice.

Do not test the app, stores, APIs, checkout, merchant data, or support systems unless the vendor explicitly authorizes that scope.

## Executive read

- Priority: `hot`.
- Pain score: `100/100` in the local fixture.
- Public bad-review bucket: `20/136` one/two-star reviews in the local fixture.
- Suggested offer: `Revenue-risk sync QA packet`.
- Best next commercial move: offer a fixed-scope public-review + docs/help-center reliability pass, then only expand into authorized repro work if the vendor asks.

## Public pain taxonomy

| Pain | Public signal paraphrase | Vendor handoff |
| --- | --- | --- |
| Data integrity / destructive state risk | A public review claims inventory quantities were set to zero across products and variants. | Create a read-only checklist for destructive actions, bulk updates, rollback surfaces, audit logs, and safe resync paths before touching production data. |
| Inventory and revenue risk | A public review says stock levels changed unpredictably and led to overselling. | Map inventory fields, locations, SKU matching rules, and failure modes that could lead to oversell, undersell, or incorrect stock display. |
| Sync reliability risk | Public listing language centers on real-time sync of inventory, products, and collections. | Review sync cadence, retry behavior, rate-limit handling, idempotency, duplicate prevention, and visibility into failed jobs. |
| Manual recovery burden | A public review ties incorrect stock state to manual recovery work and lost sales. | Identify what a merchant would need to restore manually and what logs/export tools would shorten support resolution time. |
| Sales-impact claim | A public review ties incorrect stock state to manual recovery work and lost sales. | Separate public-review frustration from verified revenue impact; if vendor wants deeper pass, ask for approved examples, timestamps, logs, and support cases. |

## Repro hypotheses, authorization required

- Multi-store source/destination sync with duplicate SKU or duplicate product surfaces.
- Inventory quantity update across variants, locations, and bulk edit/resync flows.
- Failure recovery after rate limits, interrupted sync, stale credentials, or changed product attributes.
- Support-facing evidence trail: logs, export, timestamps, affected products, and rollback route.

These are hypotheses for vendor-approved testing, not actions to run against a live store without permission.

## Docs and support gap pass

- Is there a setup checklist for source/destination stores, locations, SKUs, attributes, and excluded products?
- Is there a safe-mode or dry-run explanation before bulk sync?
- Is duplicate creation prevention explained in merchant language?
- Are rollback, audit logs, failed jobs, and support escalation paths easy to find?
- Are support macros aligned to the review pain language merchants already use?

## 48-hour action plan

1. Confirm whether the vendor wants `public-review-only` or `public reviews + docs/help-center` scope.
2. Pull the app listing, recent public reviews, help docs, pricing/setup pages, and support escalation copy.
3. Build a taxonomy of public pain by failure class and revenue/support risk.
4. Convert the top failure classes into a QA checklist and engineering/support handoff.
5. If the vendor provides authorized test-store access, run only the agreed scenarios and report evidence.

## Buyer reply script

If the vendor asks what is needed:

> I can start with just the app listing, public reviews, and docs/help-center links. That keeps the first pass low-friction and avoids any private access. If you want a deeper repro pass later, you can provide a vendor-approved test store and exact flows to test.

## Deliverable checklist

- Review pain taxonomy.
- Severity / revenue-risk ranking.
- Likely failure classes.
- Vendor-approved repro checklist.
- Docs/help-center/support macro gaps.
- Engineering/support handoff notes.
- Clear limitations and recommended next step.

## Commercial fit

- Public-review-only packet: `USD 149` test price.
- Reviews plus docs/help-center/support gap pass: `USD 299` test price.
- Vendor-approved test-store repro pass: `USD 499` test price if they explicitly authorize scope.