Cross-store SKU ID mapping checklist for web shop and CRM
Checklist to keep App Store, Play and web-shop SKU IDs aligned for CRM and support, grounded in StoreKit and Play Billing product concepts.
SKU drift between stores breaks web shop redemption and support macros. Apple StoreKit and Google Play Billing each require their own product identifiers; a web shop adds a third namespace.
Checklist
- Canonical offer key. Human-readable key (for example
pass_s1_premium) owned by economy design. - Three IDs. Map canonical key → App Store product ID → Play product ID → web-shop SKU.
- CRM payload. Email/push deep links carry the canonical key, never a single-store ID alone.
- Support macros. Agents search by canonical key; scripts expand to store IDs.
- Retirement. When an offer ends, mark all three IDs retired on the same date in the sheet.
- No silent reuse. Do not recycle Play product IDs for a different entitlement.
- Reconciliation. Weekly join of store proceeds and web-shop settlements on canonical key.
Limits: Xsolla/Appcharge-specific field names are not read from the primary source here; attach provider docs when wiring a named web shop.
