Sprusify

Multi-store considerations

Running Sprusify across multiple Shopify stores introduces challenges around global affiliate accounts, attribution, and payouts. This page outlines recommended setups and trade-offs.

Deployment patterns

  • Separate apps per store: each Shopify store installs a separate Sprusify instance; simplest for isolated accounting and store-specific campaigns.
  • Centralized multi-store: a single Sprusify platform manages multiple stores and aggregates affiliate performance; useful when affiliates promote multiple stores.

Key considerations

  • Affiliate identity: use a global affiliate_id so the same affiliate can be recognized across stores in centralized setups.
  • Currency differences: normalize revenue in exports or in reports; decide which store’s currency governs commission calculations.
  • Payout routing: centralize payouts per affiliate or per store - choose based on tax, legal, and operational constraints.

Attribution across stores

  • If an affiliate links to several stores, track clicks and conversions per store and present aggregated views.
  • Use coupon codes or cross-store tracking parameters to help track cross-store conversions where cookies are not shared.

Accounting & compliance

  • Keep store-level exports for tax purposes and a consolidated export for affiliate payments in the platform currency.
  • Consider region-based KYC/Tax rules - central payouts may trigger different obligations.

Developer notes

  • Design your DB schema to include store_id on clicks, conversions, and payouts to allow simple filtering and aggregation.
  • Ensure webhooks are registered per store and that your OAuth flow handles multiple store connections for a single merchant account.

Choosing the right model depends on operational complexity and legal requirements - start with separate per-store instances if unsure.

Setup checklist

  1. Connect each Shopify store separately from Admin > Stores > Connect store.
  2. Choose whether affiliates are global (single affiliate ID across stores) or store-scoped (different affiliate records per store).
  3. Set currency handling: enable automatic currency conversion for reporting or keep per-store currency reporting.

Data and attribution implications

  • Orders are attributed per-store; reporting will aggregate across stores if global affiliates are enabled.
  • Inventory and SKU differences require mapping rules if you use product-level commission overrides.

Testing and verification

  • For each connected store, place a test order to confirm tracking, coupon creation, and webhooks are routed to Sprusify.
  • Verify exports include a store_id column to segregate data by store during reconciliation.

Best practices

  • Prefer global affiliate IDs for ease of reporting unless your business requires different affiliate contracts per store.
  • Keep a canonical product SKU mapping table if you run separate catalogs across regions.