Managing Software Subscriptions in the (Software) Add-Ons Store

Executive Summary & Overview 

The InflatableOffice (IO) Software Add-ons Store allows third-party partners and developers to offer software applications, integrations, and tools directly to InflatableOffice users. This document outlines the guide for partner developer submission and customer onboarding.

1. Add-On Store Architecture & Revenue Model

The store operates on a standardized revenue share and centralized billing architecture to ensure a seamless purchasing experience for subscribers and reliable payouts for developer partners

•  Centralized Billing & Storefront: All paid partner software add-ons go through InflatableOffice billing with a 30% fee, and payouts are distributed at the end of each month.
• Payment Verification: Apps must include a check to verify that the user has actually paid (via the InflatableOffice add-on store) before unlocking functionality. This prevents users from downloading the app directly without going through the payment flow.

Revenue Breakdown

Note: InflatableOffice collects 100% of subscription fees upfront and distributes the 70% developer share at the end of each billing month.

2. Partner Developer Submission Process

Step 1: Submit Application Information (ref. Add-On Creator KB article)

1. Log in to the InflatableOffice portal.
2. Navigate to the Software Add-ons section.
3. Fill out and submit the add-on listing form, including app name, monthly pricing, detailed description, and support contact details.
4. Upload necessary tax and payment documentation (W-9 and ACH Direct Deposit forms) for end-of-month payouts.

Step 2: Configure Subscriber Instructions

Regarding updating the subscription details, the onboarding instructions sent to the customer after subscribing should cover the following guidelines:

• Account Setup Timeline: Let the customer know you are setting up their account, when that will occur, and that they will be connected to InflatableOffice automatically.
• Communication Method: Let them know how you will communicate with them when the account is set up (e.g., sending an email).
• Login & Next Steps: Tell them how to log in, complete any remaining setup, and what next steps to take.
• Support Contact: Provide clear contact information (e.g., support email) so they know how to reach you if they have questions.

Step 3: Purchase & Provisioning Handoff Flow

1. Purchase/Checkout: When a customer wants the add-on, they go to the software add-ons store, select the add-on, and pay through the InflatableOffice checkout system.
2. Money Flow: InflatableOffice collects 100% of the payment upfront and distributes the net developer payout at the end of the month after deducting the 30% store fee.
3. Automated Alert / Notification: The moment the purchase goes through, the system automatically triggers a "New Addon Subscriber" alert notification to the developer with customer details (Company Name, Account Owner Name, Email, Phone Number, etc.).
4. Account Setup: The developer uses the information provided in the alert to set up the customer's account (either manually or automatically through their app backend).
5. Marking as Paid & Authorization: Because the "New Addon Subscriber" trigger only fires after a successful purchase through InflatableOffice checkout, the developer's system flags the customer as paid and authorized, bypassing any separate payment page on their app.
6. Onboarding: The developer's system emails the customer their login details and setup instructions so they can log in and finish configuring their account.

3. End-User / Subscriber Journey

The end-to-end subscriber journey ensures quick provisioning and transparent onboarding steps:

1. Browse & Purchase: User selects the desired software add-on in the IO Marketplace and completes payment.
2. Confirmation: User receives an automated confirmation email with developer instructions outlining next steps.
3. Provisioning: Developer receives subscriber details and provisions the user's account.
4. Onboarding: User receives login credentials from the developer, connects API credentials, and completes onboarding.

4. Operational Boundaries & Support Roles

To ensure operational clarity, responsibilities are clearly divided between InflatableOffice and developer partners.