# Dropshipping Store Pack Readiness Assessment

Scope: `apps/dropshipping-store-solution-pack/**`, `solution/packs/dropshipping-store.*`, `/solution/dropshipping` landing content, and the module combination of CMS website scope, Store, SCM, and Documents.

Current launch posture: `pilot_ready` with controlled expansion checkpoints.

## Recommendation

The module combination is a strong fit for a **controlled dropshipping operator pilot**. Position this as a scoped launch foundation: one catalog, one supplier flow, and one delivery workflow. It should be an installable operations workspace, not a turnkey promise that suppliers, marketplaces, carriers, payment providers, tax, or consumer-law obligations are solved automatically.

## Why the combination makes sense

1. **CMS + website scope** can anchor public storefront routing, integration endpoints, and website-level configuration.
2. **CMS** can manage landing pages, collection pages, policy content, FAQs, and campaign content with review workflow.
3. **Store** can manage catalog, products, offers, pricing, checkout handoff, and customer order state.
4. **SCM** can manage supplier queues, purchase orders, stock exceptions, shipments, and delivery handoffs.
5. **Documents** can hold supplier agreements, invoices, return evidence, claims, policy snapshots, and audit trail.

## Required scope boundaries

- Start with one supplier catalog and one order-to-delivery workflow.
- Keep connector work sandboxed or human-reviewed until live supplier, carrier, payment, accounting, and marketplace integrations are certified.
- Treat consumer protection, tax, customs, privacy, product-safety, and marketplace-policy requirements as operator responsibilities with human review.
- Avoid claiming guaranteed supplier stock, guaranteed delivery, marketplace approval, payment approval, or automated compliance.

Phase-1 boundary lock
- Install defaults to CMS + Store + SCM + Documents only.
- Optional connectors remain off by default and are only enabled after pilot checkpoint, capability test, and explicit expansion decision.

## Recommended offer

- Landing page: `/solution/dropshipping`
- Parent package: `apps/dropshipping-store-solution-pack`
- Install CTA: `/package/install-and-choose/Global%20Setting/dropshipping-store-solution-pack.json?solution=dropshipping`
- First-run setup: `solution/packs/dropshipping-store.onboarding.json`
- Funnel: `solution/packs/dropshipping-store.funnel.json`

## Completed hardening

1. Production package registry names are now aligned to `CMS`, `Store`, `SCM`, and `Documents`.
2. The operator menu profile is wired through `apps/dropshipping-store-solution-pack/app.json` and post-install application-shell selection.
3. Smoke coverage now includes `/solution/dropshipping` CTA links and local install-and-choose package resolution.
4. Certified sandbox connector packs now cover supplier catalog, carrier tracking, payment status, accounting export, and marketplace channel handoff.

## Phase-2 usability hardening checklist

- [x] Remove non-existent placeholder integration options from install-and-choose metadata.
- [x] Align optional metadata/integration IDs across package manifest, solution meta, and README with real connector packs.
- [x] Keep landing/onboarding language explicit about real, pilot-ready connector paths.

## Phase-3 evidence and supportability gate (before ad traffic)

- Launch stage for ads: `pilot_ready` only.
- First-run boundary remains: CMS + Store + SCM + Documents baseline; connectors only after pilot acceptance.

### Required install and route checks (explicit)

- [ ] `/solution/dropshipping` must render successfully and show the pilot supportability banner.
- [ ] Hero CTA install route resolves with local package metadata:
  - `/package/install-and-choose/Global%20Setting/dropshipping-store-solution-pack.json?solution=dropshipping`
- [ ] Readiness and onboarding artifacts return successfully:
  - `/solution/packs/dropshipping-store-readiness.md`
  - `/solution/packs/dropshipping-store.onboarding.json`
- [ ] Funnel artifact links resolve:
  - `/solution/packs/dropshipping-store.funnel.json`
- [ ] Redirect typo paths continue to route to canonical landing:
  - `/solution/dropshiping`
  - `/solution/droppshiping`
- [ ] Pack install artifact references are present and consistent:
  - `apps/dropshipping-store-solution-pack/manifest.json`
  - `apps/dropshipping-store-solution-pack/meta.json`
  - `apps/dropshipping-store-solution-pack/app.json`

### Manual pilot simulation requirement (pre-ads)

- Before any paid campaigns, run at least one internal manual pilot per pilot-ready solution path:
  - one successful one-catalog, one-supplier operator run,
  - one failed/unsupported route run (carrier/provider/stock exception + routing to review),
  - one connector-gated exception run that confirms expansion remains controlled.
- Validation rule for first-run:
  - no critical blockers in catalog import, PO routing, or shipment/return evidence attachment,
  - no unresolved install/route 4xx/5xx.

### Supportability and escalation contract

- Assumed support scope: same-business-day triage for first-blocker tickets in pilot path.
- First escalation owners:
  - support triage -> launch-ops coordinator -> package/packets owner.
- First escalation criteria:
  - install route cannot resolve to package metadata,
  - required module dependency is missing in catalog-to-delivery setup,
  - shipment/return evidence cannot be attached within pilot continuity target,
  - connectors cannot be safely promoted from pilot to controlled expansion.
- Customer communication rule:
  - use `pilot_ready` and `controlled expansion` language only,
  - avoid GA or broad production claims until explicit rollout review is complete.

## Next implementation gaps

1. Wire live marketplace listings to the parent solution pack and connector packs.
2. Add provider-specific live certification evidence before enabling real supplier, carrier, payment, accounting, or marketplace API calls.
3. Add end-to-end HTTP smoke evidence in an environment with Symfony Runtime, dependencies, and package registry access.