ISVforce Guide

ISVforce Guide: Build and Distribute AppExchange Solutions
Get Ready to Distribute on AppExchange
Use Managed Packages to Develop Your AppExchange Solution
Manage Orgs with Environment Hub
Architectural Considerations for Group and Professional Editions
Security Requirements for AppExchange Partners and Solutions
Pass the AppExchange Security Review
Manage Your AppExchange Listings
AgentExchange Go-To-Market App Guide
Prerequisites and Considerations
Building Blocks of the Go-To-Market App
Go-To-Market App Transaction Lifecycle
Get Started with the AgentExchange Go-To-Market App
Undertand Invoices and Payouts
Understand Licensing in the Go-To-Market App
Your Customers and the Go-To-Market App
Migrate Existing Orders to the Go-To-Market App
Sell on AppExchange with Checkout
Report Orders to Salesforce with the Channel Order App
Provide Free Trials of Your AppExchange Solution
OEM User License Guide
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Building Blocks of the Go-To-Market App

We built the Go-To-Market (GTM) app around five primary objects. Together, they track each milestone within the lifecycle of the transaction. The objects are: products, offers, orders, invoices, and pay out.

Now, we explore each object in-detail. If you want a more detailed view of all objects involved in the GTM app, see the Go-To-Market App Data Model.

GTM App Objects

Object What It Is How It's Used
Products

Represent the thing that you’re selling, which can include licenses, apps, and services.

All offers and orders are built on top of one or more products, which you can create in the Partner Business org (PBO).

Products are associated with a Partner Product Catalog (PPC), which the partner account manager (PAM) creates.

 After you create a product, you can map it to managed package licenses.
Offers

Represent what the customer reviews and accepts in their Salesforce org, including pricing and contract terms.

Each offer is created as a Partner Offer in the GTM app and references one or more products. An offer can be an initial offer or an add-on offer.

 When a customer accepts an offer, Salesforce automatically creates an Order record and handles billing and provisioning on the partner’s behalf.
Orders

Represent the record that Salesforce creates when a customer accepts an offer.

The order mirrors the accepted offer, but is only viewable by the partner. Orders include finer details like finalized purchase amounts, with taxes and calculations applied.

 Includes the finalized purchase details that Salesforce uses to trigger billing and provisioning.
Invoices Represents the invoice that Stripe generates after an offer is accepted and an order is created. The invoice is emailed to the customer and given the pending status. When the customer pays the invoice in Stripe, the status moves to Paid.
Payouts Represent the net revenue that partners receive from settled customer payments.

Stripe consolidates all settled customer payments into a single, daily partner payout, which Stripe deposits into the partner’s bank account.

Every payout shows the related invoices, with Salesforce fees deducted.