Onboarding

Overview

Merchant onboarding in Klippradar is a controlled product flow, not a one-off manual setup. It covers:

• invite and claim
• plan selection and pool assignment
• activation readiness gates
• optional or required feed bootstrap
• migration from shared to dedicated capacity

Flow summary

1. An operator creates or updates the merchant in admin.
2. Klippradar assigns shared or dedicated capacity based on plan and state.
3. An owner or admin is invited into the merchant dashboard.
4. If feed bootstrap is required, the first validation run is executed.
5. The merchant only becomes staged when access, pool readiness, and feed readiness are all in place.

Activation requirements

To be considered ready, a merchant must have:

• active owner/admin access
• dashboard enabled
• a ready crawl pool
• a successful feed result if feed is required
• runtime policy enabled

Feed usage

Feeds can be used in two ways:

• optional as a data-quality improvement
• required as part of onboarding for higher data trust

If a feed is required, a failed first run blocks activation until the source is fixed and rerun.

Onboarding outcomes

After onboarding, a merchant may end up in one of these states:

• shared verified capacity
• direct dedicated capacity
• migration requested from shared to dedicated capacity

Support

The most common onboarding blockers are:

• wrong invite email or invite state
• feed bootstrap failures
• dedicated capacity not ready
• migration waiting for source-pool drain

During pilot onboarding we support merchants operationally, but the goal is a repeatable and verifiable product flow rather than ad hoc setup.