Guide
WooCommerce Partner Fulfillment
Connect an approved reseller store, approve product mappings, and fulfill only the relevant order lines.
Connection and approval are separate
The native integration connects a reseller's WooCommerce store to an approved SoundSync partner relationship. No WordPress plugin is required. The reseller authorizes the store connection; the developer reviews mappings for their own SoundSync products.
WooCommerce grants store-level read/write API access. SoundSync's filtering does not narrow that provider permission. Native webhooks can contain a whole order, including unrelated lines. Review those permissions and privacy obligations before connecting a store.
SoundSync
Approve a store safely
-
Connect the reseller store
An approved partner creates the connection and authorizes WooCommerce access. Keep the callback and webhook credentials private.
-
Sync catalog
Review the minimal catalog data used for candidate matching: IDs, titles, SKUs, types, prices, and product links.
-
Review candidates
Inspect Strong, Possible, Approved, and Dismissed mappings in the relationship Integration view. A suggestion is not automatic fulfillment approval.
-
Approve relevant products
Map only products owned by your developer workspace. Dismiss false matches so unrelated products do not hold relevant orders.
-
Handle variations
Approve specific variations or explicitly approve all current and future variations. Understand the broader scope of the latter choice.
-
Activate and test
Exercise a mapped product, mixed cart, duplicate event, unmapped candidate, and refund with an agreed test order before relying on live fulfillment.
Mixed carts and financial scope
Fulfillment and reporting are limited to approved relevant lines and their actual discount/tax amounts. Unrelated products, shipping, and unrelated coupons must not be converted into SoundSync product revenue. An external WooCommerce sale does not become a SoundSync Merchant of Record sale just because SoundSync issues access.
Refund matching
Refunds match fulfilled order-line IDs. An unrelated line cannot revoke access to the mapped SoundSync product. An amount-only partial refund requires review rather than guessing which entitlement to remove. Serial delivery and serial-free entitlement delivery depend on the approved relationship configuration.
Resync and retained data
A complete catalog sync must succeed across all pages before absent items are archived. Changed names require a new sync; existing approvals and fulfillment history are not discarded simply because a suggestion changes.
The durable webhook inbox stores identifiers, references, and signature hashes rather than retaining an entire raw customer payload. Relevant fulfillment still requires limited customer/order data. Do not describe this as a guarantee that the provider never transmits personal information.
SoundSync