MLM Software Integration

The division of responsibility

An integration works when both systems keep what they are good at, and fails when they overlap. The line we draw is the same on every platform.

Your storefront keeps: the product catalogue, pricing and promotions, the cart and checkout, payment capture for retail orders, tax calculation on the sale, inventory, fulfilment and shipping, order status emails, and the customer-facing brand experience.

The commission engine takes over: distributor identity and enrolment, sponsor and placement trees, order-to-distributor attribution, volume classification (personal, group, leg, retail versus distributor purchase), plan rules and qualification, the commission run, the wallet ledger, payouts, and the compliance controls that depend on knowing whether a buyer is a customer or a participant.

The last item is the one that most often forces the decision. A storefront has no concept of a retail customer versus a distributor buying for personal use, and that distinction is the foundation of the evidence a US direct selling company needs.

Attribution is the part to get right

Everything downstream depends on correctly deciding which distributor an order belongs to. Five signals are supported, in priority order:

1. An authenticated distributor placing their own order.
2. A customer already assigned to a distributor in the back office.
3. A replicated-site link or subdomain, persisted for the session and through checkout.
4. A distributor-specific coupon or referral code entered at checkout.
5. A default house account, if you configure one.

The order in which these resolve is configurable, because the right answer is a commercial one. A company that pays on lifetime customer assignment wants (2) to beat (3); a company that pays on last-touch wants the opposite. Whatever you choose is recorded on the order, so an attribution dispute is answerable.

Refunds, partial refunds and cancellations

The storefront remains the source of truth. When it reports a refund, the linked volume is reversed and the commission consequences unwind through the adjustment mechanism described on the commission software page. Partial refunds reverse proportional volume. Cancellations before fulfilment reverse the volume entirely.

Rate limits and reliability

The API applies per-endpoint rate limits, published in the OpenAPI specification. Webhooks are HMAC-signed and retried with exponential backoff for 24 hours, and every delivery is visible and replayable from the dashboard.

Beyond that, a reconciliation sweep runs every fifteen minutes against each connected storefront and compares order counts and totals for the trailing window. Dropped webhooks happen on every platform; the sweep is what stops a dropped webhook from becoming a commission discrepancy nobody notices until a distributor does.