Not an affiliate plugin — a super-app that turns every agent into a mini-marketer: AI content, one-tap WhatsApp selling, self-serve ads, and milestones to climb.
GoAffPro is a passive affiliate tool — a link, a code, a commission table. It doesn't touch WhatsApp social commerce, it can't generate content, agents can't run ads from it, and there's nothing to climb. Your ask is a different product class: an agent super-app where selling, content, ads, and status all live in one cockpit.
Agent link + coupon, a commission dashboard, payout. That's the floor — good enough for Week 1, but it stops exactly where your growth ambition starts.
Manage orders + payout + AI content generation + one-tap WhatsApp selling + self-serve ads + a milestone ladder — a system that makes agents sell more, not just track what they sold.
Shopify stays the commerce engine (catalog, checkout, inventory, orders). WhatsApp is the social-commerce channel (share, sell, reorder). You build the Agent Growth OS on top — a thin, headless app that reads/writes Shopify, drives WhatsApp, mints ads, generates content, and runs the commission + milestone engines. You don't rebuild commerce; you build the agent's cockpit and its growth loops.
One-tap share of a deal card to their group/status; orders attributed by code + link.
Generate on-brand posts, images & captions for the live drop in seconds.
Boost a post into a Meta ad with co-op or own budget — attributed to them.
Sales unlock higher commission, more ad budget, and status — a reason to keep going.
People use surfaces; surfaces call the Agent Growth OS; the OS orchestrates the platform services (Shopify, WhatsApp, Meta, payments, the Zennith creative engine); everything writes one attribution-complete data layer.
An agent-driven sale and an ad-driven sale hit the same ledger: agent_id and ad_id are both stamped on the order. When an agent boosts a post, the ad's ad_id is minted under their agent_id — so their ad-driven sales attribute to them and feed the existing ad_id → order → CAPI → ROAS chain. One dashboard, one truth, agents are just another attribution source.
Low-fidelity wireframes of the agent cockpit. Everything an agent needs to sell, create, boost, get paid, and climb — in one PWA they open like WhatsApp.
Per-agent + per-product commission · drop config (zones/MOQ/cut-off) · content templates + brand-lock (agents generate only on-brand assets, auto-audited by god-mode ≥9.5) · ad co-op budget + locked audiences (agents can't mis-target or break claims) · milestone/tier rules · payout approval. Agents get freedom inside rails you set once.
Each agent becomes a mini-marketer. The four growth features aren't separate tabs — they're a loop that compounds: create → share → boost → sell → climb → create again, with each turn cheaper and bigger.
Tap "Generate" → the Zennith engine makes an on-brand deal card / reel / recipe + caption for the live drop. God-audited, brand-locked.
One tap posts it to their group + status (and IG/FB). Carries their link + code, so every resulting order is theirs.
Optional: turn the post into a Meta ad with co-op + own budget. An ad_id is minted under their agent_id.
Customers order via code/link → attributed → commission accrues (held to delivery). Real-time MOQ bar drives urgency.
Sales raise the milestone bar → higher commission + more co-op ad budget + status perks → motivates the next Create.
An affiliate plugin gives an agent a link and hopes they post. This gives them the content to post, the channel to post it, the ad budget to amplify it, and a status ladder that rewards doing it again — with every action attributed and fed back into commission + ROAS. The incumbent WhatsApp-chat operators can't see any of it; you compound on all of it.
Core objects in orange. agent_id and ad_id both hang off order — that's the attribution join that unifies agent commission with the ROAS chain.
The sell → attribute → accrue → fulfil → settle sequence, and where each integration fires.
Next.js (React) PWA — installable, push-capable, WhatsApp-share-native. Admin = same app, role-gated. Reuse the Zennith dashboard component library.
A thin API (FastAPI/Node) over Postgres holding agent/drop/order/commission/milestone; the Drop, Commission, Milestone, Content & Ad engines; webhook workers. Sits beside the Zennith sidecar.
Source of truth for catalog, checkout, inventory, orders, payments. Storefront + Admin API + order webhooks. Draft Orders API for host order-on-behalf.
Your existing Chatwoot + WABA. Cloud API for broadcast, deal cards, CTWA, order-confirm, reorder. Dual-pixel CAPI as already wired.
gpt-image-2 (fal) for visuals + the copywriter for captions, gated by god-mode-audit ≥9.5 and brand-lock — the exact stack that generated the brand key-visuals.
Meta Marketing API for agent boosts (ad_id minted per agent). Stripe Connect for commission split + payouts; HitPay/PayNow for SG collection, DuitNow for MY.
Reuse (already yours): Shopify, WhatsApp/Chatwoot/WABA, the ad_id→order→ROAS attribution chain, the gpt-image-2 + copy + god-audit creative engine, DO Spaces. Build-new (the actual project): the agent PWA + admin, the Drop/Commission/Milestone engines, the agent↔ad_id attribution join, and the content/ads self-serve wrappers. It's a focused build on a stack you already run — not a greenfield platform.
Each milestone ships something an agent can use — no big-bang. (Per your call, agent onboarding is deferred; this is the platform build order.)
M1 makes money flow correctly (the hard, boring, must-be-right part). M2 gives agents something to post. M3 lets them amplify. M4 makes them come back. You could ship M1 as GoAffPro-assisted to buy 3 weeks, but since the end-state needs the native ledger + WhatsApp + ads + gamification anyway, building M1 native avoids a throwaway migration.