Guide
Customer Records and Access
Use customer search, imports, purchases, serials, devices, and access actions without conflating them.
Start with the customer context
Customer records are developer-scoped. Search/filter by the supported fields and date range, then review purchases, owned products, serials, activation devices, and verification state. Marketing permission is a separate property, not implied by the record existing.
SoundSync
Customer tools
SoundSync
Actions have different effects
| Action | Meaning |
|---|---|
| Edit customer | Correct supported profile fields in your workspace |
| Resend verification | Send the supported ownership/account verification message |
| CSV import/export | Move permitted developer-scoped records using the supplied format |
| Deactivate a device | Release that activation, not the customer's entire purchase |
| Hide/show portal order | Change supported customer-portal presentation, not necessarily entitlement |
| Remove access | A deliberate access operation on the selected purchase item; not a refund |
| Invoice PDF | View the relevant authorized order invoice |
| Delete customer | A separate sensitive action; review linked records and retention obligations first |
Take care with ownership changes
A serial assigned to another customer cannot be claimed merely by knowing its text. Follow owner proof, verification, and the supported account path. Correcting an email address is not permission to transfer all product ownership.
For refund, dispute, or account-closure requests, follow the policy and support procedure. Never publish raw customer tables, last names, email addresses, serials, or tokens in public screenshots.
Support activity and deliberate grants
Permissioned customer tools also expose activity, plugin-connection events, and internal notes. Supported recovery actions can resend library/activation mail or reset activations. These are not a replacement for customer identity verification.
Manual product grants and suspend/restore/revoke operations require the relevant entitlement permissions and product scope. A grant of access is not authorization to start recurring billing. Keep the action, reason, and customer communication explicit.
Purchase refunds and documents
The Purchases table supports order references, filters, item detail, authorized invoice PDFs, exports, and permissioned refund previews. Refund an eligible full order or whole selected products within the initial 14-day window; do not substitute Remove Access for a payment refund. Review cumulative refunded items, payment state, original tax/fee amounts, and any recipient allocations.
A pending or needs-review refund is not complete. Use its operation reference and the current purchase state for support. Billing and finance summaries can lag the provider event until reconciliation; do not send the same refund again merely because one table has not refreshed.
Customer activation resets, when enabled
Developers can allow customer self-service resets for supported serial and entitlement licenses, with a configured cooldown. Only the signed-in owner of the license can request a reset. The confirmation clears the affected device activations and sessions together while preserving the license and product ownership.
A reset is not a refund, a new serial, or unlimited extra devices. Customers must reload the current state and wait for the next eligible reset when a cooldown applies.
Customer details belong to the relevant store
Authorized developers can correct customer names, email and phone and, for a linked customer account, set a password for their own storefront relationship. These edits do not change the shared SoundSync login, another developer storefront, shared verification, or shared account recovery.
A changed store email or password invalidates earlier sessions and reset links issued for that store credential. The customer signs in using the corrected email in that storefront. Store-only sessions cannot manage global account security or use another store; the shared SoundSync account remains the route for platform-wide settings and integrations.
Email corrections update the store marketing contact, supported pending email work and current store contact references, including support, serial and order contact fields. Later marketing activity and imports retain the corrected store details. Customer edits to the shared SoundSync profile update shared contact records without replacing separate store details. Sent email, issued invoices and payment-provider history remain historical records.
First and last names can be cleared independently. Workspace-wide contact editing requires the existing customers.manage permission and all-products scope. Contact corrections do not transfer purchases, rewrite issued invoices, change refund eligibility or clear marketing restrictions. Last Login records sign-in activity, not a support edit.
Current access and previous records
The customer account separates current licenses and plans from Previous licenses and Previous subscriptions. Ended or inactive records stay available in expandable history; a plan with remaining eligible paid-through access is not hidden merely because cancellation is scheduled.
A signed-in marketplace customer who already owns a product can open their library and downloads from its product page. This is an account-specific lookup, not a public ownership list. License-reset cooldowns show the next eligible date; resetting activations does not create another license.
Purchases and marketing preferences
Customer records and marketing contacts serve different purposes. Purchases and eligible account/serial activity can automatically enroll the associated developer contact; existing unsubscribes, complaints, and suppressions remain protected. Do not infer sending permission from the presence of a customer row.
SoundSync
Marketing information and choices
Help a previous purchaser sign in
If a purchaser has never set a password, direct them to Reset password on your storefront with their purchase email. A blocked-storage message means their browser could not save the session; allowing required site data and retrying is different from changing product ownership. Do not issue another paid order or remove an entitlement to repair sign-in.
SoundSync
Customer sign-in recovery
Account Security
Passwords, browser storage, verification, authenticators, and recovery.
Purchase history also includes access records
The customer tables distinguish paid orders, subscription payments and access-only records. Access included with a subscription or another grant can appear without a new payment. These records have no invoice and do not add sales revenue. A subscription-earned product can display its original funding order and a $0 item amount; other access records use an ACCESS reference. Neither display is a new charge or refund permission.
A manual grant recorded for a customer who already owns the product retains the existing entitlement and serial. Hiding that manual history does not remove the original access. Use the appropriate original license or serial control for an intentional access change; no history action itself refunds money.
Permanent gifts and paid subscription ownership
A timed manual keep-products grant gives the customer permanent ownership of the products included when the developer makes that grant, without a payment. That original product snapshot remains owned after subscription cancellation, expiry or incomplete billing setup. Explicit developer access removal can revoke the grant. New products added later are not retroactively included.
A lifetime manual grant instead provides complimentary ongoing subscription access; it is not the timed-grant ownership model or evidence of a paid invoice. Ordinary access-only grants and unpaid checkout trials also do not create paid ownership.
Paid keep-products invoices establish their own product snapshots. Refunding or reversing a paid purchase affects that purchase, not an independent manual ownership grant. Future paid subscription benefits still require the separate billing setup, preview and customer confirmation; a gift is not permission to charge a card.
Customer identity in redeemed-serial imports
Redeemed-serial imports, through the CSV upload or legacy JSON route, reuse the existing customer identity matched by normalized email without replacing its shared name, verification, account status or marketing preferences. A new identity is created only as part of a successful imported serial row. The serial can retain its developer-specific imported name snapshot; that snapshot is not a shared account-profile edit.
Unknown or unowned products, invalid required input and duplicate serials are skipped. A duplicate race or failed serial insert rolls back any customer created for that row. Earlier successful rows can remain imported if a later row fails; review the result and retry deliberately. A serial import is not a paid checkout, inbox verification, login transfer or permission to bypass an unsubscribe.
Closing one store account is not deleting SoundSync
The developer customer-removal action closes and blocks the customer account at that store and stops supported pending marketing and measurement. Required purchase and financial history remains. Requests for that closed store return CUSTOMER_STORE_CLOSED; the shared SoundSync identity and unrelated stores are not deleted.
Account closure, a refund, unsubscribing and a privacy-erasure request have different effects. For broader privacy requests, contact support@soundsyncsolutions.biz. Existing retention and legal obligations still apply.
Read the sale allocation separately from the final payout
A managed purchase receipt shows the original developer allocation before separately billed account charges, where applicable. Actual processing, marketing or redemption usage, the monthly-minimum adjustment and payout costs can be reconciled elsewhere. That allocation is not the final bank payment.
For external purchases, reseller_estimate.feeBps is 0. recordedAllocation identifies a saved unfunded allocation. A recordedAdjustmentCents value reconciles its original net against the currently resolved sale price, reseller split and recorded collaborator amount; it is not a newly charged fee. Missing prices or split terms stay unavailable rather than becoming a confirmed zero.
SoundSync
Export complete filtered records
Customer, serial and purchase exports
Date meanings, progress and source identities.
SoundSync
Current customer/order/serial export choices
Review the specific product before changing access
Support actions can suspend, restore or revoke an existing customer entitlement for one permitted product. They require entitlement-management permission and the product assignment, with a reason recorded for review. They do not refund the payment, close the customer account or change another store.
Restoring the entitlement does not clear a serial already marked revoked. Review that serial separately rather than telling the customer that every credential is usable again. A disconnected plugin still follows its existing signed authorization until it reconnects or that authorization expires.
SoundSync
Product-specific support actions
Product access API
Request fields, returned access state and restore limitations.
