Skip to main content

How to Apply In-App Purchases & Subscriptions Using the Purchase Tab

Offer one-time purchases and auto-renewing subscriptions directly inside your Buildfire app, with payments synced to Google Play and the Apple App Store.

Amr Alshareef avatar
Written by Amr Alshareef
Updated yesterday

The Purchase Tab lets you create consumables, non-consumables, and subscriptions. This guide shows how to configure, test, and publish your in-app products using the latest guidelines.

Accessing the Purchase Tab

  1. Log in to your Buildfire App Dashboard.

  2. In the left menu, go to Features → Purchase Tab.

    • If it isn’t added yet, open Marketplace, search for “Purchase Tab,” and add it.

  3. Manage products, subscriptions, and pricing from this tab.

Setting Up Products & Subscriptions

  • Consumable Products
    One-time items users can buy repeatedly (tokens, credits, downloads). After use, they’re consumed and can be bought again.

    • ⚠️ Important: Prefix consumable names with c_ in the Control Panel so they’re recognized as consumables and can be repurchased.

    • Note: Consumables do not persist across devices or reinstalls.

  • Non-Consumable Products
    One-time unlocks that remain available after reinstalls or device changes (e.g., Remove Ads, Unlock All Lessons).

  • Subscriptions
    Auto-renewing plans for ongoing access (e.g., monthly membership, premium features).

To add a new item

  1. Click Add Product or Add Subscription.

  2. Enter Name, Description, and Product ID.

  3. Set the Price Tier (must match store listing).

  4. Choose Visibility (all users or specific groups).

  5. Click Save.

    • ⚠️ Important: Product IDs must match exactly with Google Play Console or App Store Connect. Mismatches will fail validation.

Connecting to Google Play and App Store

Google Play

  1. Sign in to Google Play Console.

  2. Go to Monetization Setup → In-App Products.

  3. Add each product/subscription using the same Product IDs as in Buildfire.

  4. Link your Google Merchant Account.

  5. Ensure Google Play Billing Library v6+ is enabled.

Apple App Store

  1. Open App Store Connect.

  2. Go to My Apps → Your App → In-App Purchases.

  3. Add products/subscriptions with the exact same Product IDs.

  4. Configure pricing, availability, and subscription duration.

  5. Confirm your Paid Applications Agreement is active.

Testing In-App Purchases

  • Confirm products/subscriptions appear in the Purchase Tab with matching Product IDs.

  • Verify prices and descriptions.

  • Double-check products are linked to the live app configuration.

  • 🟡 Note: You don’t need developer/test user purchases—our Publishing Team validates setup during app submission.

Publishing Your App with Purchases Enabled

  1. Open the Publish tab in your Buildfire Dashboard.

  2. Our Publishing Team submits your app to Google Play and the App Store.

  3. Make sure store listings include accurate pricing and subscription details.

    • 💡 Tip: Apple and Google review in-app purchases during approval. Avoid test or placeholder prices in live submissions.

Post-Publishing Responsibilities

Once live, you’re responsible for keeping subscriptions and products active and consistent:

  • Keep active subscriptions configured in Buildfire.

  • Maintain matching Product IDs across Buildfire and store listings.

  • Ensure pricing and visibility reflect your current offers.

Failing to maintain these risks removes access for paying customers.

Store Variables

Use variables to display localized prices and offers without manual updates.

Available Variables

  • store_price — shows the product/subscription price in the user’s local currency.

  • initial_price — shows a special introductory or trial price when an offer is active.

How Variables Work

Insert variables as:
​({ store_price | fallback_value })

  • Always include a fallback value so layouts don’t break in the Control Panel.

    • Example: ({ store_price | $8 })

    • Avoid ({ store_price }) alone.

Placeholders and Fallbacks

If a variable returns no value, use a pipe to chain fallbacks:
​({ variable_name | fallback_value })

  • Example: ({ store_price | $8 })

    • In the Control Panel, the fallback shows because store prices aren’t fetched during editing.

Advanced Variable Logic

initial_price appears only while an offer is active. Chain to avoid blanks:
​({ initial_price | store_price | $1 })

  • If a promo is active → initial_price

  • If not → store_price

  • In the Control Panel → $1

🟢 Example copy:
“Subscribe now for ({ initial_price | store_price | $1 }) during your trial, then ({ store_price | $8 }) per month after.”

FAQs & Troubleshooting

Q: I see “Invalid Product ID.” What now?
Check the Product ID in Buildfire exactly matches what’s in Google Play Console and App Store Connect.

Q: How do I offer free trials?
Configure the trial or intro offer in your store listing and surface it using initial_price.

Q: Can I change prices after publishing?
Yes. Update pricing in Play Console or App Store Connect. Users see the change via store_price.

Q: Purchases worked in testing but not after publishing.
Confirm the release build uses the same signing key and is linked to the live store listing.

Q: What happens if I delete a subscription product?
Deleting/unpublishing a product in stores or Buildfire can revoke access for active subscribers. Update with care.

Pro tips

  • Keep product names and descriptions short and clear.

  • Document your Product IDs in a shared sheet to avoid mismatches.

  • After launch, monitor refund/chargeback activity in stores to catch mis-configured items early.

Did this answer your question?