Orders and Delivery

Payment confirmation precedes access changes

The checkout/provider flow confirms payment; the customer returning to a success page is not enough on its own. Orders and items preserve transaction context, while entitlements determine access.

A mixed cart can contain products with different ownership and fulfillment scope. An approved external order must not silently turn unrelated reseller products into SoundSync product lines.

Files have a preparation lifecycle

Upload jobs must finish verification and attachment before the intended product file is deliverable. A developer preview download and a customer-authorized download are different permissions. Signed links are private and temporary; do not embed them in public documentation.

Refunds target the affected purchase

An access change must follow the actual refunded/revoked item and policy. It should not remove unrelated purchases, and a raw refund amount without line identity can require manual review. Delivery troubleshooting starts with product/file state and customer entitlement, not merely the browser's download button.

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.