Concept page
Platform Concepts
Understand products, orders, entitlements, serials, devices, files, subscriptions, storefronts, and partner scope.
SoundSync
Objects have different responsibilities
| Concept | Meaning |
|---|---|
| Product | The developer-owned offer and integration configuration |
| Customer | The relevant customer identity/record; not automatically a marketing subscriber |
| Order | A transaction or supported external-order record |
| Order item | The particular product line and its transaction context |
| Entitlement | The customer's right to access a product under its current policy |
| License / serial | Licensing/claim information linked to product access; knowing a serial is not always owner proof |
| Activation / device | Authorized use on a machine under the product device policy |
| Download | An authorized delivery event for an eligible file |
| Subscription | Recurring commercial state that can affect entitlement |
| Storefront | A hosted/embedded customer commerce surface |
| Partner relationship | Approved developer/partner scope and operating model |
| Product credential | Product-scoped API access, not a developer account token |
Follow the right chain
A successful checkout redirect is not final payment proof. A payment event can create order and entitlement records; activation then checks customer/product/device access. A library token authorizes browsing; it is not a developer account credential.
Refunding a purchase, hiding a portal order, deactivating a device, and deleting a contact have different effects. Use the specific operation and policy instead of treating them as interchangeable cleanup.
SoundSync