The customer places an order
Associate the order with the correct member or referral using the agreed identifier.
If you already sell through an online store, the important connection is between paid orders and your compensation rules. An ecommerce integration can map products, customers and order events to the correct member and volume records.
Examples to discuss: WooCommerce, Shopify, Magento / Adobe Commerce or a custom store.
These are project options to assess, rather than a list of included connectors. We confirm the external API, account access, costs and development requirements in your scope.
Associate the order with the correct member or referral using the agreed identifier.
Credit eligible volume once, using the external order ID to prevent duplicate processing.
Reverse the relevant volume and commission entries according to the refund policy.
Send the provider name, a sample record and the event that should trigger an update. Access to a test account helps us check the workflow without touching live records.
A connection needs more than a successful first transfer. We agree how to detect a missed update, avoid processing the same event twice and reconcile the records after an outage. Your team should know who can retry a failed event and which system to check.
During acceptance, test an ordinary record, a duplicate, a correction and a provider failure. Confirm the result in both systems before going live.
See how custom development is scoped ↗Choosing your platform is a big decision. We’re here to make it easier.
Ask us anythingNo. Product-level volume or exclusions can be scoped. Provide the catalogue and the rules for bundles, discounts and promotional items.
Yes, an integration can connect them. We agree which system owns products, stock, orders and member accounts to avoid conflicting updates.
Bring your compensation plan and your questions. We’ll show you how the software could fit.