Shipaton 2025 - Day 22 - Products and Offerings

What I Built Today

Today was about making the subscription catalog rock-solid and consistent across Google Play Console and RevenueCat so the upcoming paywall can “just work.”

✔️ Configured subscription products in Google Play Console for the app’s catalog.
✔️ Created the corresponding products in RevenueCat and assembled them into clear offerings.
✔️ Aligned Google Play product IDs with RevenueCat entries so everything maps 1:1.
✔️ Documented the catalog and offering structure to streamline the paywall integration.
✔️ Kept scope intentionally tight: focus on products + offerings setup across both platforms.

🎯 Result: The product catalog is configured in Play Console and the offerings are set in RevenueCat. Everything is aligned and ready for wiring the paywall and purchase flow next - steady progress toward launch.

Why Products & Offerings Alignment Matters

✅ Removes integration risk. A strict 1:1 mapping between Play product IDs and RevenueCat products prevents mismatches and failed purchases.
✅ Speeds up implementation. Clear, named offerings mean the paywall can target the exact package without guesswork.
✅ Enables clean analytics. A tidy catalog → reliable conversion and cohort tracking later.
✅ Future-proofs experiments. With offerings in place, adding intro deals, price tests, or region-specific packages becomes low-friction.
✅ Simplifies reviews & support. A documented structure is easier to explain in app store review notes and to debug if something goes off-track.

Conclusion

Today’s update locks in a consistent, well-documented subscriptions foundation across Play Console and RevenueCat. With products and offerings aligned, the next step - wiring the paywall UI and purchase flow - will be faster and safer. Another requirement dialed in, another step closer to launch.