Launching with Products the Platform Had Never Seen,
Without Delaying Go-Live
An operator preparing for market entry brought a product lineup that went beyond the standard set. ReferOn split the launch into two phases, extended its own system logic, and matched the client’s timeline.
10 days
Base integration, kickoff to live
2 phases
Base products first, new products next
1-2 month
To full product coverage, in step with the brand’s launch
System-wide
Data handling improvements shipped for all future clients
Background
Pre-launch. The affiliate program had to be ready the day the brand went live.
Challenge
Part of the client’s product lineup did not exist in the ReferOn system, or in most affiliate platforms at all.
- Waiting for full product coverage would delay the entire launch
- Forcing the new products into existing categories would corrupt reporting from day one
- The client’s data also surfaced edge cases in case sensitivity and character length that standard integrations never trigger
Why the usual approach fails
The usual vendor answer is a choice: delay the launch until everything fits, or launch with distorted data and clean it up later. Neither is acceptable for a brand entering the market.
Goals
The plan had to protect the launch date and the data at the same time:
- Go live on time with the base products
- Add the remaining products without breaking reporting or reward logic
- Align the platform rollout with the brand’s own product launch schedule
Success criteria
No delay to go-live, clean product-level data across the full lineup, and no re-integration later
Solution
One person on the client’s team had already worked with ReferOn, was happy with how the product looked, and knew how easy it was to set up affiliates. That familiarity made the shortlist short.
Phase one
Fast, standard integration covering the base products
Phase two
the ReferOn team reviewed the platform code and redefined parts of the system logic to support the new product types, launched 1 to 2 months later
Rollout
The rollout was timed to coincide with the client’s own launch schedule, so the two phases matched the brand’s roadmap almost exactly
Along the way, the integration flagged data pickup edge cases around case sensitivity and character length that had not appeared before. ReferOn fixed them at system level, improving data handling for every client that comes after.
Implementation
- Onboarding timeline. 10 days for the base integration, with all integration steps completed smoothly. Full product coverage followed 1 to 2 months later.
- Team involvement. ReferOn integration and platform engineers, working through a full code review and a redefinition of system logic for the new product types.
- Customization. Deep but structural. Instead of one-off patches, the system logic itself was redefined, so the new products behave like native categories rather than exceptions.
Why it worked
The phased rollout matched the brand’s own launch almost one to one, so the client never had to choose between launching on time and launching with clean data.
Results
The brand launched without compromise: no delay, no distorted categories, no re-integration debt. And the edge cases uncovered during this project made the platform more resilient for every operator that onboards after them.
10 days
Base launch
Live in 10 days, on schedule
1–2 months
Full product coverage
Added 1 to 2 months later, in step with the brand’s own launch
Clean
Data quality
Clean product-level reporting across the full lineup, no re-integration
System-wide
Platform impact
Case sensitivity and character length handling improved system-wide
“One of us had used ReferOn before, so we expected the setup to be easy. What we didn’t expect was the team redefining parts of their own system so our products would fit properly.”
– Head of Affiliates
What’s next
With the full lineup live, the operator is scaling partner acquisition and building product-level deal structures on top of the extended category logic.