Launch Affiliate in 15 minutes

#Prepare three things first

Affiliate does not begin with sending messages at scale. It begins with reliable product facts, an executable Campaign goal, and clear human-review boundaries. Before the first launch, confirm that:

1. the target Shop is Authorized and Affiliate is enabled from its Overview;
2. the current Desktop is signed in, will remain online, and has a usable model and Affiliate run profile;
3. the team has named the people responsible for reviewing important Agent proposals and sample applications.

If those foundations are not ready, start with Shop Management and Models, devices, and run profiles.

By the end of this guide, you will have one minimum viable loop: Product Knowledge supplies facts → a Campaign defines the goal → the Agent prepares and advances work → people review important actions → outcomes stay in the Creator relationship history.

#1. Enable Affiliate and confirm how it runs

Open Shops, select the target Shop, enable Affiliate from Overview, then open the Affiliate tab. For a first setup:

• keep the built-in Affiliate run profile;
• use the Global default model until the Shop needs a deliberate override;
• bind business handling to a Desktop that will remain online;
• begin with conservative policies that hold important work for human review, then expand automation after the loop is proven.

The Shop Overview is only for authorization and service switches. Team settings, approval policies, Business instructions, and other operating controls belong in the Affiliate tab.

#2. Build Product Knowledge first

Open Affiliate → Product Knowledge and create or choose a knowledge set for the product you plan to promote. At minimum, record:

• positioning, core benefits, and intended audience;
• verifiable specifications, pricing, fulfillment, and sample rules;
• common Creator questions with approved answers;
• useful creative directions and claims that must not be used.

One knowledge set can link the same product across Shops through Seller SKU. Campaigns and the Agent then work from one maintained source of facts.

APP CAPTUREThe English light-theme Creative Cases view in Product Knowledge. Cases organize creative direction, performance, and assets for reuse in Creator outreach and guidance.

Product Knowledge should contain facts the team can verify and rules the Agent can execute. Do not turn an unconfirmed result, inventory level, or platform outcome into a promise.

#3. Create the first Campaign

Open Affiliate → Campaigns, create a Campaign, and define:

1. Product and offer: choose a product with complete Product Knowledge, then enter commission, sample, or other collaboration terms;
2. Target Creators: set market, category, audience size, content performance, and other qualification criteria;
3. Daily target: begin with a small number so the team can inspect match quality and message tone;
4. First message: explain why this Creator is relevant, how the product fits their content, and the next step;
5. Delivery and review: keep important outbound actions under human review for the first run.

APP CAPTUREThe English light-theme Campaign page, showing active Campaigns, daily targets, funnel progress, and replies.

Before launch, check that the target is not too broad, daily volume does not exceed the team’s review capacity, and the message makes no unsupported promise.

#4. Complete Agent handoffs in the Affiliate Workbench

Open Affiliate → Workbench. Pending review contains Agent operations held by policy; Pending contains work outside the Agent’s capability, tools, or authority that a person must take over. The final three tabs centralize all Agent work, Sample Applications, and Creator messages across Shops.

APP CAPTUREThe English light-theme Affiliate workbench with three proposals waiting for review, including their type, related Creator, and creation time.

Keep “proposal” separate from “executed action.” A proposal is a prepared action that remains on hold until it is approved. During review:

• verify that the recommended action matches the evidence;
• confirm the product, Creator, and Campaign context;
• approve work that is ready to execute;
• rewrite, reject, or request a revision when it is not.

#5. Test human control with a sample review

Open a sample application and compare the Agent recommendation with Creator performance, relationship history, and risk evidence before making the decision.

APP CAPTUREThe English light-theme sample review. The AI recommendation and evidence are shown alongside controls for a person to approve, reject, or add conditions.

Samples, added benefits, and out-of-policy promises create real cost. Keep human approval in place until the team’s decision standard is stable. The result remains in the same Creator relationship and work history, so later conversations can continue with that context.

#6. Close the loop every day

A practical daily rhythm is:

1. review Campaign funnel and execution progress;
2. clear high-priority reviews and human-takeover cases in the Affiliate Workbench;
3. check Creator replies, Samples, and exceptional escalations;
4. add recurring questions to Product Knowledge or Business instructions;
5. increase daily targets or widen auto-execution only after review outcomes are consistently sound.

#Go-live checklist

• The Shop is Authorized and Affiliate is enabled.
• The handling device, run profile, and model are available.
• Product Knowledge contains facts, Q&A, creative directions, and prohibited claims.
• The first Campaign’s target, daily volume, and opening message have been reviewed.
• The team knows where to handle held proposals and sample applications.
• At least one “Agent proposal → human review → recorded outcome” test is complete.