All rolesReference
Frequently asked questions
Quick answers to common questions from visitors, merchants, and partners across signup, storefronts, store context, payouts, contracts, and public profiles.
Last reviewed: Apr 17, 2026UI path: Documentation home → Introduction → Frequently asked questions
Summary
Quick answers to common questions from visitors, merchants, and partners across signup, storefronts, store context, payouts, contracts, and public profiles.
When to use this page
- You need a quick answer before opening a full task page.
- You want one reference page that covers the most common platform questions across all audiences.
Before you start
- Know which role or experience you are asking about.
Top tasks
Visitor guideOpen public storefront, application, and post-purchase guidance.Merchant first-time setupStart merchant onboarding and initial configuration.Standard Affiliate guideOpen links, payouts, contracts, and store-context guidance.VIP Partner guideOpen storefront, analytics, and VIP-only workflow guidance.
Success looks like
- You can find a direct answer without guessing which guide family owns the topic.
- You can identify whether the next step belongs in visitor, merchant, or partner documentation.
Where to find it
Documentation home → Introduction → Frequently asked questions
General FAQs
1. What is Affilyn?
Affilyn is a Shopify-based partner program platform that helps merchants recruit partners, manage applications, run storefronts, track performance, review payouts, and handle partner agreements.
2. Who is this documentation written for?
It is written for four audiences: visitors using public storefronts, merchants managing the program, Standard Affiliates using partner tools, and VIP Partners managing storefronts and advanced features.
3. Do I need technical knowledge to use the product?
No. The current help center is positioned as non-technical product guidance, so most pages focus on dashboard actions, storefront behavior, and workflow decisions instead of code or API details.
4. What is the difference between a visitor, a merchant, a Standard Affiliate, and a VIP Partner?
A visitor uses public pages only. A merchant runs the program. A Standard Affiliate works with links, payouts, and contracts. A VIP Partner gets the standard partner tools plus storefront and advanced merchandising features.
5. Why do some files in the Affilyn say creator while the docs say partner?
The Affilyn still uses creator in many internal routes, models, and implementation plans. The public documentation uses partner as the clearer user-facing term.
6. How does sign-in work?
Partner access uses magic links sent by email. You enter your email address, open the one-time sign-in link, and enter the dashboard without a password.
7. Do users create passwords?
No password-based flow is documented for partner users. The implemented partner auth flow is based on email magic links.
8. Where should I start if I am new?
Visitors should start in the Visitor Guide. Merchants should start with Merchant First-Time Setup. Partners should start with Partner Signup and Login, then move into the standard or VIP guide that matches their access.
9. Can the same person work with more than one store?
Yes. The platform supports multi-store affiliations, and the active store context changes the data and tools shown in the partner dashboard.
10. Why do dashboard tools change after switching stores?
Because access is store-scoped. A partner can have different affiliations, statuses, and tier access in different stores, so the active store determines what the dashboard shows.
11. What is the default store?
The default store is the store that opens first when a partner enters the dashboard without another store context already selected. It acts as the fallback context when the previous store is unavailable.
12. Can the same partner be Standard in one store and VIP in another?
Yes. Tier and feature access are store-aware, so a partner can have different access levels across different merchant relationships.
13. Are all features available to every shop and every user?
No. Some features depend on role, tier, store affiliation, shop configuration, feature flags, or whether the merchant has published the required storefront or checkout components.
14. What is public versus private in Affilyn?
Public pages include storefronts, public partner profiles, and some application entry points. Private areas include the merchant dashboard, partner dashboard, payout tools, contract signing workspace, and builder pages.
15. How do payouts work at a high level?
Partners configure a payout method, meet the effective threshold, and submit a payout request. Merchants then review that request in the admin payout queue before any automated or manual payout is completed.
16. Does Affilyn hold payout funds itself?
No. The app coordinates payout state and records, but the actual payout funds come from merchant-controlled payout accounts such as Stripe, PayPal, or off-platform manual transfers.
17. How do contracts work at a high level?
Merchants upload an active DOCX template, generate a contract draft for a partner, send it for signature, and the partner signs it in-app. The workflow stores the generated DOCX and the signed PDF summary as separate artifacts.
18. Can a signed contract be edited?
No. Signed contracts are treated as immutable. If something changes, the merchant must issue a new version instead of editing the signed one.
19. Why does the setup wizard still mention a subscription plan step?
Because the wizard still includes a subscription placeholder step. Live setup decisions currently happen in the actual settings and payout pages rather than through that placeholder screen.
20. Is there a public developer API or technical reference in this help center?
Not as a public documentation track. The current help center is oriented around product workflows, so users should expect dashboard and storefront guidance rather than full developer-facing API documentation.
Visitors FAQs
1. Do I need an account to browse a storefront?
No. Public storefronts are designed to be browsed without logging in.
2. What can I do as a visitor?
You can browse public storefront content, view products, see public partner profile information when shared, apply to a merchant program if the storefront supports it, and complete a purchase like any other shopper.
3. Why does the storefront sometimes greet me differently on a later visit?
Some storefronts support returning-visitor personalization. That means the welcome message can change when the system recognizes a repeat visit.
4. Why can a storefront look different during a campaign or holiday?
Because storefronts can use seasonal themes or campaign styling. The public view may change without changing the underlying products or partner identity.
5. Will every storefront show a visible discount?
No. Discount presentation is controlled by the merchant and storefront configuration. Some storefronts show discounts openly, while others reveal them more quietly or later in the journey.
6. Why do I see a different price presentation on different storefronts?
Because discount visibility, storefront settings, and campaign rules can vary by merchant and storefront. Public pricing presentation is not required to look the same everywhere.
7. What is the difference between a regular product offer and a bundle offer?
A storefront can highlight individual product pricing and separate bundle deals. Bundle-style offers are presented as their own storefront experience rather than simply duplicating the normal product card state.
8. How do I apply as a partner from a storefront?
Use the published Apply as a Partner button when it is visible on the storefront. That opens the application flow tied to that merchant’s program.
9. Why don’t I see an Apply as a Partner button?
The merchant may not have enabled applications, may not have published the theme block, or may not use public applications for that storefront at all.
10. Why is the button still visible if applications seem closed?
Because the merchant can turn off submissions in admin without removing the storefront block. In that case the public button may still appear even though the backend is no longer accepting applications.
11. Does submitting an application approve me immediately?
No. Storefront applications go into the merchant’s review flow. Approval still depends on merchant review and program rules.
12. Does submitting an application automatically create dashboard access?
Not by itself. Approval, invitation, or later login activation still needs to happen before you gain the correct partner dashboard access.
13. Should I use the same email across signup, application, and login?
Yes. Using one consistent email is the safest way to keep your future partner access tied to a single identity instead of creating fragmented records.
14. What is a public partner profile?
It is a shareable, read-only partner page that can display a partner’s name, bio, website, social handles, country, affiliations, and summarized attributed-order stats.
15. Why does a public partner profile sometimes return not found?
Public profiles only resolve for eligible partner records. In practice that means the partner must still be active and verified enough for the public endpoint to return data.
16. What kind of information can a public partner profile show?
It can show profile basics, active or historical affiliations, and a summarized attributed-order view. It does not expose private dashboard controls, payout details, or merchant-only data.
17. Can I buy from a storefront without joining the partner program?
Yes. Shopping and partner application are separate actions. A visitor can complete a storefront purchase without applying to become a partner.
18. Will I always see a creator thank-you message after checkout?
No. The thank-you experience depends on attribution and storefront configuration. Some attributed orders can show a partner-branded message, while others will not.
19. Why do I not see the post-purchase partner message even though I bought through a storefront?
The order may not have been attributed to the storefront in the expected way, or that store may not have the thank-you experience enabled for the current journey.
20. Who should I contact if a public storefront or profile looks wrong?
Start with the merchant or brand that shared the storefront, because storefront publishing and public application behavior are controlled on their side. If they direct you to support, use the support contact listed by the product or merchant.
Merchants FAQs
1. How do I start merchant setup?
Install the app in Shopify, open Affilyn from the Shopify app list, and complete the merchant setup wizard or continue setup from the dashboard if you skipped it earlier.
2. Can I skip the setup wizard and come back later?
Yes. The setup flow is soft-gated, and merchants can return through the Continue Setup entry point instead of finishing everything in one session.
3. Does the subscription step in setup control my live billing?
No. The current setup wizard still contains a subscription placeholder. Use the live settings and payout pages for the real operational setup that affects your store.
4. How do I enable public partner applications?
There are two parts: enable applications in Partner Program settings, then publish the Partner Apply Button and Partner Application Modal in Shopify Theme Editor.
5. Why are applications still not working after I turned them on in settings?
Because the public storefront CTA also has to be placed and published in Theme Editor. Admin settings alone do not create a visible storefront apply flow.
6. Why can the application button still appear even after I close applications?
Because turning off applications in admin does not automatically remove the theme block. You still need to hide or remove the storefront button if you want it gone from the public view.
7. Where do I review incoming partner applications?
Use the merchant applications workflow and review queue. That is where pending submissions can be inspected, approved, rejected, or handled in bulk.
8. Can I approve or reject multiple applications at once?
Yes. The admin applications area includes bulk approval and bulk rejection actions for review workflows.
9. How do partner tiers work from the merchant side?
Merchants control or review partner tiers, and the product uses plain-language labels so Standard Affiliate and VIP access are easier to understand. Tier decisions affect which partner tools and storefront capabilities a partner sees.
10. Can one partner be linked to more than one store?
Yes. The tracked architecture and documentation support multi-store affiliations, which let the same partner work with multiple merchant stores under store-specific context and access rules.
11. What does the partner’s default store control?
It controls the store that opens first for the partner when there is no other explicit store context. It is the fallback store for login and store-context recovery.
12. How do I make automated payouts ready?
Enable the payout methods you want, connect the matching merchant-owned gateways, and review the readiness state in Payout Settings. Enabled methods alone are not enough.
13. Can I run a manual-only payout setup?
Yes. A manual-only shop does not need Stripe or PayPal connected. Automated readiness becomes important only when automated payout methods are enabled.
14. Why does the product say automated payouts are not ready?
Usually because Stripe or PayPal was enabled without the matching gateway actually being connected for the current shop, or because partners are still assigned to methods that are unavailable right now.
15. Can I still process payout requests if one gateway is missing?
Yes, but only for requests whose payout method is still available. Payout availability is method-aware, so a missing Stripe setup should not block a PayPal-capable row automatically.
16. What happens when I decline a payout request?
The request is declined, but the commissions remain available for a future request instead of being consumed by the decline action.
17. Can I record manual payouts?
Yes. The admin payouts area keeps manual payout support alongside queue-based payout approvals and payout history.
18. How do contract templates work?
Upload a supported DOCX template, activate the correct version, then generate and send drafts from the partner workflow. The active template controls what new contract drafts use.
19. What happens after a partner signs a contract?
The system stores the generated DOCX and then produces a signed PDF summary after signature completion. The signed version becomes the immutable record for that contract version.
20. Can I change a signed contract after the fact?
No. If the agreement changes, issue a new version instead of trying to edit the signed one.
Partners FAQs
1. How do I sign in as a partner?
Open the partner login page, enter your email address, and use the magic link sent to your inbox to enter the dashboard.
2. Do I need a merchant invitation before I can create a profile?
No. The Affilyn supports self-registration for a general partner profile, and merchants can later invite or link that profile to a store.
3. What happens if I sign up with an email that already exists?
The self-registration flow does not expose a duplicate-account error in the normal way. If the email already belongs to a partner record, the system sends a magic link instead of forcing a new duplicate profile.
4. Why do I see a profile-only state after signing up?
Because self-registration can create a partner profile without any active store affiliation yet. Until a merchant links or approves you into a store, you do not get the full store-specific dashboard experience.
5. Why do I not see any store-specific tools yet?
Because links, payouts, storefront access, and contracts depend on having an active store affiliation. A standalone profile does not automatically include those store-scoped tools.
6. Why does my dashboard change when I switch stores?
Because the active store context determines what data, metrics, links, payouts, and features are loaded for your current merchant relationship.
7. Why can I see the store selector even if I only work with one store?
Because the product treats store context as important even in single-store use. The switcher can remain visible so you can still confirm which store is active.
8. Can I be a Standard Affiliate in one store and a VIP Partner in another?
Yes. Tier access is store-specific, so the same person can have different access in different merchant relationships.
9. Where do I find my affiliate links?
Use the Affiliate Links page in the partner dashboard. That page is designed for product browsing, copying tracked links, exporting link data, and refreshing the catalog when needed.
10. Why does the product list on the Affiliate Links page look incomplete?
Try syncing products first. A stale or incomplete product sync is a common reason a product is missing from the affiliate-links catalog.
11. Do affiliate links depend on the current store?
Yes. Link generation and product browsing are tied to the active store context, so always confirm the correct store before you copy or share a tracked link.
12. How do I request a payout?
Open Payout Settings for the current store, link the required payout account, choose the active method, meet the effective threshold, and submit the payout request when the button becomes available.
13. Can I request payout with Manual / Other or None selected?
No. Those states intentionally disable automated payout request submission.
14. Why is the payout request button unavailable?
The most common reasons are an unlinked or unverified payout account, the wrong active method, not meeting the threshold, or already having a pending payout request.
15. Can I request only part of my available balance?
The implemented payout-request flow is queue-based and is designed around the eligible available balance at request time, not a free-form custom payout amount workflow.
16. What happens after I submit a payout request?
Your request enters the merchant review queue with a pending status. After that, the merchant can approve, decline, or the request can fail during later execution if the method is not runnable.
17. Can I submit more than one payout request at the same time?
No. The current rules prevent a second automated payout request while an earlier one is still pending review.
18. How do contracts work for partners?
Use the Contracts page to review contract versions, open a contract detail, download the generated DOCX, and complete signing when the contract is in a signable state.
19. What do I need to sign a contract?
You need the correct contract version, an eligible contract status, your legal full name, and the required consent checkbox. The contract must not already be expired, voided, or superseded.
20. Can I sign contracts if I do not have an active store affiliation?
No. The creator contract routes explicitly block contract access when there is no active store affiliation for the current partner account.
Limitations
- This FAQ page focuses on product behavior that is visible in the current codebase and public help center. It does not replace full setup, troubleshooting, or internal operations pages.
- The current help center is product-focused, so technical integration or public API reference details are limited.