PlanewardPlaneward Docs
PlanewardPlaneward Docs
Welcome
Community overviewMember access journeySales journeyMoney journeyApps in your communityCommunity notifications

Developers

REST APIAuthenticationWebhooksMCPEmbedded projectsTask description contentDeveloper hub

API

Community

Sales journey

How a visitor gets from an affiliate's link or one of your redirects to your Site sales page, through checkout, and how the sale credits the right affiliate before revenue share splits it.

Your sales page is a Site, for example contentcreatorlab.cc, and checkout runs on your community address, for example app.contentcreatorlab.cc, or on your own checkout domain. Selling doesn't need a community: Commerce runs checkout on its own. Affiliates share your Site with their code on the end, like contentcreatorlab.cc/jane. The Site shows your home page, remembers Jane for 30 days, and quietly changes every product button so checkout knows Jane sent the buyer. Redirects are separate. They're short paths like /youtube-bio that send people to a page with your campaign's UTM tags, so Site analytics knows where each visit came from.

Related

GuideUse it for
CommerceSelling without a community, checkout domains, what buyers get
Money journeyHow the payment is split, held, withdrawn, refunded
Member access journeyConfirming the buyer's email, signing in, who gets access
Community overviewHow sales, checkout, access and money fit together
Commerce → AffiliatesAffiliate partners, their codes and percentages, the Program settings
Commerce → Catalog → product → Checkout linksDedicated links with their own commission, optionally for chosen plans
Sites → your site → RedirectsShort paths that redirect, with optional campaign tags
Sites → your site → AnalyticsCampaigns, channel and campaign reports

Rule of thumb: Point your Site's product buttons at the community, for example https://app.contentcreatorlab.cc/products/<slug>?plan=<plan id>. Planeward changes them for each referred visitor. You never edit buttons per affiliate.


Journey

The split, holds, withdrawals, refunds and chargebacks are covered in Money journey.


Links you can share

LinkLooks likeMade inWhat it doesLasts
Affiliate linkcontentcreatorlab.cc/janeCommerce → Affiliates (copy link)Shows your home page and adds a=jane to the buttons of products Jane promotes30 days, last click wins
Checkout linkcontentcreatorlab.cc/jane-vipCommerce → Catalog → product → Checkout linksShows your home page and sends that product's buttons to /checkout/jane-vip30 days, last click wins
Redirectcontentcreatorlab.cc/youtube-bioSites → your site → RedirectsRedirects to a page or URL, adding the chosen campaign's UTM tagsEach visit
Promo code…?promo=LAUNCH on a product buttonCommerce → Promo codesThe discount at checkout30 days, last click wins

Codes are 1 to 40 characters: lowercase letters, numbers, - and _. Jane and jane are the same code.

An affiliate code only rewrites buttons for products that person is an affiliate for. Buttons for other products stay as they are.

You can hide the promo code field on checkout in Commerce → Promo codes → Checkout field, for every product or one product at a time. ?promo= links still apply their discount when the field is hidden.

Max redemptions is checked when checkout starts and again when the payment is recorded. If several buyers check out at once with a code's last use, each buyer who pays still gets the discounted price they were shown. Uses past the limit aren't counted against the code, and the payment gets a note that the promo was over its redemption limit and the discount was honoured.

Extend codes add time to recurring plans only. On a lifetime (one-time) plan, checkout refuses an Extend code with a message, and you can't create an Extend code for a lifetime plan. An Extend code for the whole product still works on that product's recurring plans. Lifetime access always stays lifetime.

Promo codes on Stripe

When a buyer pays by Stripe, Planeward sends the promo to Stripe as a single-use coupon, so Stripe charges exactly what checkout shows. You'll see these coupons, named after the code, in your Stripe dashboard.

  • Subscriptions take the promo on the first payment only. Checkout says "· first payment only", and renewals charge the full plan price.
  • Extend promos don't work on Stripe subscriptions, and no processor takes them on a lifetime plan.
  • 100%-off promos can't be paid through Stripe: "This promo makes the payment free, which Stripe cannot process. Choose another payment method."
  • A promo counts as redeemed only when Stripe applied it. If Stripe charged full price, the payment is recorded without the promo: no redemption and no extra time.
  • A Stripe payment page stays open for one hour. Its coupon stops working a few minutes after that, and is deleted when your webhook receives checkout.session.expired.
  • A code's redemption limit counts paid checkouts. Buyers who open payment pages at the same time can each finish within that hour and keep their discount, but only uses within the limit count against the code (see Max redemptions above).

Before every Stripe checkout, Planeward checks the plan's Stripe price: same currency as the workspace, same amount as the plan, and (for subscriptions) the same billing interval. If not, checkout stops with "This plan's Stripe price doesn't match its price in Planeward." Fix the price ID on the plan's Advanced tab, or the price in Stripe. An archived price shows "This plan's Stripe price is archived in Stripe."

A restricted Stripe key (rk_…) needs Coupons write and Prices read permission. See Payment processors.

Who pays

Checkout buys for the signed-in email's own customer. When that email is only another contact of a customer (not its own email or primary contact), its purchases go on a new customer for that person, with that email as the primary contact. The company's customer is never billed or given access by another contact's checkout, including free plans. The company keeps the contact, and the person keeps any access they had through it. Once their own purchase gives access, they sign in as their own customer, with their own Billing and Balance (see Member access journey).

Promo previews and checkout starts are rate limited per buyer and per IP: 30 promo checks a minute, and 10 checkouts every 10 minutes per buyer (30 per IP). Over the limit, the buyer sees "Too many promo code checks. Wait a minute and try again." or "Too many checkout attempts. Wait a few minutes and try again."

One code, one person

A code belongs to one person across your whole workspace, so contentcreatorlab.cc/jane always means the same Jane.

SituationAllowed
Jane uses jane on Course A and on Course BYes. One link covers every product she promotes
Jane's checkout link on Course A uses janeYes. It's still Jane
Sam tries to use jane, as an affiliate code or a checkout linkNo. Planeward shows "“jane” is already used by Jane"

When Planeward makes a code for a new affiliate, it reuses the code that person already has. Otherwise it picks one nobody else in the workspace uses.

Older codes: workspaces set up before this rule may already have the same code on two people. While both exist, /<code> doesn't add that code to product buttons, so neither person is credited by mistake. Checkout links with that code keep working. To fix it, Remove one of them on Commerce → Affiliates and add them again with a new code. Their past payments and earned balance are kept.


Unlisted plans

Each plan has a Checkout access setting:

Checkout accessWho can buy it
PublicAnyone. Listed on the product page
Unlisted — waitlistOnly buyers whose email was accepted on the product's waitlist. They see it on the product page
Unlisted — checkout linkUnlisted, not private: anyone with a checkout link that targets the plan can buy it. Use a random link code, never an affiliate's referral code
Unlisted — waitlist or linkBuyers accepted on the waitlist, or anyone with a checkout link that targets the plan. Unlisted, not private: use a random link code, never an affiliate's referral code

An Unlisted — waitlist plan needs the product's waitlist on, and you can't turn the waitlist off while such a plan exists.

When a product's waitlist is on, every plan on it, public or unlisted, needs the buyer's waitlist entry accepted before checkout. That includes free plans.

Checkout links for chosen plans

A checkout link can target specific plans in Commerce → Catalog → product → Checkout links:

  • No target plans: the link sells the product's public plans, as before.
  • Target plans: the link sells only those plans, including Unlisted — checkout link plans.

An Unlisted — waitlist plan can't be a link target. Every link still belongs to an affiliate and pays that affiliate's commission.

Commission label

Each checkout link names its commission in the earner's ledger history. The label is free text, set when you create the link or later with Commission label… in the link's menu:

LabelLedger history shows
AffiliateAffiliate commission
SetterSetter commission
(empty)Commission

New links start as Affiliate. Changing the label names new commissions only; past ones keep their wording. Commissions from an affiliate code (?a=) without a link always show Affiliate commission.

What a plan gives

What buyers get is set on the product, not the plan, on its Access tab (What buyers get). Every plan of the product gives exactly what is listed there, free plans included. Community access is one item on that list, next to courses, event tickets, file downloads and external links. A product may give nothing at all. See Products and what buyers get.

Buyers of any plan of a product that gives community access become members. Products that had a free plan when Commerce arrived were switched to give community access, so nothing changed for them.

Granting access

Staff with permission to manage Commerce can give a customer free, lifetime access to a product: Commerce → Catalog → product → Subscriptions → Grant access. Pick the customer and any of the product's plans, including unlisted ones. Checkout access doesn't apply, no payment is taken, and this grant never renews or expires.

  • The subscription shows as Complimentary in the table. If the product gives community access, the customer becomes a member, and that counts toward your member limit. If it sells event seats, the customer gets the seat too, the same as a free checkout; revoking the grant releases it.
  • Planeward refuses when the product is archived or the customer already has an active subscription to that plan.
  • Revoke access on the row ends a grant right away. It works only on grants. To end a paid subscription, use the row menu (Cancel a member's subscription) or refund the payment.
  • Payments and refunds never touch a grant. If the customer later pays for the same plan (an invoice, a receipt, a manual payment, or a recorded purchase), that payment starts or continues a separate paid subscription, and the grant keeps its lifetime access next to it. Refunding that payment ends the paid subscription only. Stripe and Xendit checkout treat a grant like a lifetime plan the customer owns, and refuse a purchase that would bill them again for access they already have.
  • A grant sends subscription.started with complimentary true (and managedBy MANUAL, paidCycles 0), and revoking sends subscription.canceled, so workflows and webhooks on those events run for grants too. Filter on complimentary to tell a grant from a paid start.
  • A grant counts as a subscription, so its plan and product can't be deleted.

Deleting plans and products

You can delete a plan or a product only while nothing depends on it. Planeward refuses when it has:

  • Customers: any subscription, past or active.
  • Money records: payments, receipts, invoice lines or open checkouts.
  • For a product, also: revenue-share entries or waitlist entries.

The error lists what's blocking. In that case, archive the product instead.

Deleting detaches any forms attached to it and removes promo codes that apply only to the deleted plan. Deleting a product also removes its plans, checkout links, affiliates and promo codes.


Waitlist

A waitlist lets you approve buyers before they can check out. It works on the whole product, so it applies to every plan on it.

Turning it on

  • With a form: attach a form with the Waitlist purpose in Commerce → Catalog → the product → Forms. That turns the waitlist on, and buyers answer your questions when they apply. A Waitlist form is attached to the whole product, so it can't be attached to a single plan, and it can't be a draft.
  • Email only: use the waitlist switch on the product. Buyers confirm their email and press Join the waitlist, with no questions to answer.

If you unlink the Waitlist form, Planeward asks whether to keep the waitlist on (email only) or turn it off. If you unpublish the attached form instead, the waitlist keeps running as email only until you publish it again.

What the buyer sees

  1. The buyer opens the checkout page and confirms their email.
  2. A dialog opens on the checkout page and they apply there: they answer the Waitlist form's questions, or on an email-only waitlist they press Join the waitlist. The Waitlist form keeps its own layout and Custom CSS in your community colours (see How the form looks).
  3. After applying they see a pending message, and checkout stays blocked until you accept them. A product with only free plans accepts applicants automatically.

Accepting and rejecting

You can accept or reject each application in Commerce → Catalog → the product → Waitlist, or build a workflow that does it for you (see Workflows). A rejected applicant stays rejected, and checkout stays blocked, unless you accept them later. Rejecting fires the Community waitlist rejected event.

Accepting someone unlocks the product's waitlist plans for checkout with that email, and emails them a sign-in. It gives no membership and no access to anything else, so they still have to check out. This is true however they're accepted: by you, by a workflow, or automatically on a free-only product. People accepted before this changed keep the community access they already got.

While the waitlist is on, a checkout link doesn't get anyone past it. To open the cart, accept the people you want to let in, or turn the waitlist off.

With a Checkout form

If a product has both a waitlist and a before-payment Checkout form, the buyer is asked the waitlist first. Once they're accepted, the checkout page asks for the Checkout form before payment.

This order applies to products with paid plans. On a product whose plans are all free, joining the waitlist accepts the buyer at once, so a before-payment Checkout form on that product is never asked.


Checkout forms

A checkout form makes the buyer answer a form as part of buying. Attach a published CRM form in Commerce → Catalog → the product → Forms, choose the Checkout purpose, then pick when it's asked:

TimingWhat happens
Before paymentThe buyer answers first. Planeward refuses to start any payment (free, card, Xendit or bank transfer) until they have.
After paymentThe buyer pays first. The form holds back only the page they land on afterwards; access is never taken away.

Before payment

A before-payment form is shown in one of three ways:

  • Dialog when paying: a dialog opens when the buyer presses the pay button.
  • Dialog on page load: a dialog opens as soon as the checkout page loads and can't be closed until the form is sent. It shows the form for the plan selected at that moment (the first plan, or the one in the link). If the buyer switches to a plan with a different unanswered form, that form opens when they press pay instead.
  • Inline above the plans: the form sits below the email and above the plans. The pay button sends it, then starts the payment. On a form with several pages, the pay button stays disabled and reads Answer the form to continue until the buyer reaches the last page.

The buyer has to be signed in first, so every before-payment form starts with the usual email confirmation (or sign-in) step, then the form. Signing out puts the form back in the way.

After payment

An after-payment form is always a dialog that can't be closed. The buyer's landing is held back until they send it: they aren't forwarded to your after-purchase redirect or the community home. Access to the product is never taken away. If they leave before answering, the dialog comes back on the product page or the checkout page the next time they visit. Once they answer it there, they go where a finished checkout sends them: your after-purchase redirect, else the community home (or onboarding). A form owed for a bank transfer that's still waiting for approval just closes, and the buyer stays on the page.

Bank transfers show the form right after the buyer uploads their receipt, before staff approve it. Awaiting post-purchase form (Commerce → Catalog → the product → Forms) lists the buyers who haven't answered yet. It appears once the product has an after-payment form.

How the form looks

Checkout forms, the Waitlist form and the after-payment form on /join keep the form's questions, layout and Custom CSS, in your community theme's colours. The form's Background, Accent and Corner radius don't apply here. The questions sit straight in the checkout or dialog, without a logo, name or description; a dialog shows the name and description in its header. A form with several sections shows one per page, with Back and Next, and in a dialog the submit button sits under the questions. See Form appearance.

Product or plan

Attach a form to the whole product, or to one plan. A plan's form replaces the product's form for the same timing, so a plan can ask a different question or none of the product's. A product or plan has at most one before-payment and one after-payment form, and a form can only be attached in one place.

What counts as answered

  • A buyer answers each form once. Later purchases of the same form don't ask again.
  • Only answers given at checkout count. Sending the same form through its public link, an embed, a site, the API or MCP doesn't count, even for the buyer's own email, so the buyer is still asked at checkout.
  • Only published forms apply. A draft is ignored at checkout, and the forms table marks it Not applied (draft). Swapping to a different form asks the buyer again.
  • Answers arrive as normal submissions, so Form submitted workflows and webhooks run.

Good to know

  • Staff can't submit. Staff viewing a checkout can't buy, so they see checkout forms but can't send them.
  • Spam asks again. Marking a submission as spam, or deleting it, counts as not answered, and the buyer is asked again.
  • Free plans show an after-payment form once, right after access is granted. They don't have a purchase record, so the buyer isn't asked again and isn't listed under Awaiting post-purchase form.
  • Earlier purchases aren't asked. An after-payment form only applies to purchases made after it was attached. Buying again after access lapsed counts as a new purchase; renewals don't. A bank transfer counts from when the receipt was uploaded, not when staff approve it.
  • Closing the tab. A buyer who closes the tab before answering an after-payment form never reaches an off-site success URL. They're caught on their next visit to the product or checkout page, and sent on once they answer.

Icon and gallery

Give a product its own icon and a gallery in Commerce → Catalog → the product → Media. There's no draft or save step: media is public as soon as you add it, and a removed item comes off the product page right away.

Icon

A square image shown beside the product name on the product page and checkout, and next to the product in your catalog. Upload a JPEG, PNG or WebP up to 5 MB and crop it to a square. Without an icon, the product page shows your logo from Branding there.

Gallery

A gallery holds up to 8 items, in any mix:

ItemWhat you can add
ImageJPEG, PNG or WebP up to 5 MB, cropped to 16:9. Keep important content centered; wide screens trim the top and bottom.
VideoMP4 or WebM up to 512 MB, or your plan's file size limit if that's lower. H.264 MP4 is the safest choice; a video your browser can't play is refused.
YouTube linkA link to a YouTube video. Other video sites aren't supported.

Drag the tiles to reorder them; the first one shows first. Once the gallery has 8 items, remove one to add another.

Where buyers see it

  • The gallery runs full width at the top of the product page and of checkout links, above the product details and the checkout. One image shows as a still picture. Two or more items get arrows and dots, and the gallery never moves on its own.
  • Videos show a preview image with a play button and start only when the buyer presses play. Nothing is loaded from YouTube before that.
  • The icon sits beside the product name.
  • Link previews (when someone shares the product page or a checkout link) use the first image in the gallery, else the first video's preview image, else the icon.

An archived product's page isn't public, so its media isn't served either. You can still edit it, and it goes public again when you unarchive the product.


Payment methods and mobile layout

Both settings live on Commerce → Catalog → the product → Settings.

Payment methods

Payment methods chooses which of your payment methods buyers can use for this product: Card (Stripe), Xendit and Bank transfer. All three are on by default, so a product offers every method your workspace has set up.

  • It only narrows. A switch can hide a method you've set up, but it can't add one. A method you haven't set up shows as unavailable; it's set up in Settings → Integrations → Payments, which the page links to when you can manage integrations.
  • Card payments need a Stripe price. Card (Stripe) only works for a plan that has a Stripe price ID. A plan without one can only be paid with Xendit or a bank transfer.
  • Every paid plan keeps a way to pay. You can't save a change that leaves a paid plan with no method that works for it, for example switching off Xendit and Bank transfer while a plan has no Stripe price ID. Planeward names the plans that would be left out. Turning a method on is always allowed.
  • Watch for later changes. Adding a paid plan, giving a free plan a price or removing a payment method from your workspace can still leave a plan with no way to pay. The Payment methods card then shows a warning naming those plans until you turn on a method that works for them.
  • Free plans aren't affected. They don't take a payment, so they check out the same way whatever you switch off.
  • It applies everywhere. A method that's off disappears from the product's checkout, and Planeward refuses it even if someone tries to use it directly. Checkouts a buyer already started and bank transfer receipts already sent still complete after you switch their method off.

Mobile layout

On phones and narrow screens (anything below the desktop layout, such as a tablet held upright), the product page stacks two blocks: the checkout (plans and pay button) and the product description. Mobile layout chooses which comes first:

  • Checkout details first (the default): buyers see the plans and pay button first, with the description below.
  • Description first: buyers read the description first and scroll down to the checkout.

Desktop is unchanged. A product with no description at all, neither the short description nor the About text, always shows checkout first, since there's nothing to put above it. The setting applies to the product page and to checkout links. A product's gallery isn't part of this choice: it's always on top.


How the Site reads a path

A path on your Referral site can be a page, a redirect, or a code. Planeward checks them in this order and uses the first match:

  1. A published page with that slug.
  2. A redirect with that path.
  3. A code: an enabled checkout link, or an affiliate code on a product that isn't archived.
  4. Otherwise, not found.

You can't create a clash. Planeward refuses a page slug or redirect path that matches an existing code, and a code that matches an existing page or redirect. Built-in paths such as products, checkout and login can never be codes.

Codes only work on the Referral site you pick in Commerce → Affiliates → Program. On your other Sites, /jane is just a missing page.


How a sale finds its affiliate

  • Last click wins. If someone opens /jane and later /sam, Sam's code is used from then on.
  • Checkout link beats affiliate code for the checkout link's own product.
  • The Site, the community and a checkout domain each remember the code on their own address. A buyer who switches browser, device or address starts fresh.

What happens on a click


After the payment

The buyer confirmed their email before paying, so they're already signed in: access appears on its own, with no second email. See Member access journey.

Where the buyer lands

After paying, the buyer sees Finishing your order until the payment comes through, then goes by what the product gives:

The product givesThe buyer lands on
Community accessThe community home (or onboarding, the first time)
A courseThat course
A file, a link, an event ticket, or a mix of thoseTheir Purchases page, at the product's card
NothingA confirmation that says You're all set

Buyers always return to the address they started on. To send them somewhere else, such as a thank-you page, an upsell or a course, set a redirect:

  • One product: Commerce → Catalog → the product → Settings → After purchase.
  • Every product: Commerce → Catalog → After purchase. A product's own redirect overrides it.

A redirect is a full address (https://example.com/thanks) or a path on your community site (/courses/intro). The buyer is redirected only once their access to that product is active, so links back into the community work straight away. This also applies to existing members buying another product. Free plans redirect right away. Bank transfers wait for staff approval, so they don't redirect. Leave both fields empty to use the table above.

The payment is recorded on Finance → Payments, and the affiliate's Uses count goes up by one. A bank transfer's payment is dated when the buyer submitted the receipt, not when staff approved it, so it counts in the day and month the buyer paid. If the product shares revenue, what the buyer paid is split between the affiliate, the product's holders and your treasury, using the program's Cost mode and the product's treasury setting. For Stripe and Xendit payments, the processor fee comes off later from the holders and treasury the product picked to cover it, never from the affiliate. Every share stays on hold until the product's cooldown ends and then becomes available to withdraw. See Money journey.


Paid events

Sell seats at an event through a product. Open the event in Events (create or edit), and under Sold by tick one or more products. Changing Sold by needs Manage commerce; without it the picker is hidden. Checkout doesn't change: buyers pay on the product page or a checkout link as usual. Event tickets don't need a community.

What a payment does

When a payment for any plan of a linked product completes, Planeward registers the buyer's contact for the event. The contact is the payment's contact, or else the customer's primary contact. It runs in the background, a few seconds after the payment. These payments count:

  • Card checkout (Stripe) and Xendit.
  • Bank transfer and QR receipts, once staff approve them.
  • Paid invoices whose items include one of the product's plans.
  • Free checkouts and staff grants of a plan, which need no payment. Revoking the grant, or ending the plan, releases the seat.

The registration works like any other:

  • The buyer joins every email audience filtered on that event.
  • event.registered fires. To send a ticket confirmation, build a workflow on event.registered with a send email step.
  • If the event has a pipeline, a deal is opened, or an open one reused.

A buyer who was already registered, for example through the event's form, isn't registered twice. Their registration is tied to the payment instead, so it becomes a paid seat (see Refunds).

Which events and products

  • Only Scheduled and Live events register buyers. Ended and cancelled events don't, so archive the product once the event is over.
  • The product must be in your workspace and not archived to be linked. A product that's already linked stays linked after you archive it, until you remove it.
  • Free plans register the buyer too. A free checkout and a staff grant both give the event seat, and ending the plan or revoking the grant releases it, unless another live product still sells the event.
  • Earlier buyers who paid before you linked the product aren't registered. They're registered on their next payment for that product, or you can add them by hand on the event page.
  • Recurring plans register again on every renewal. If you remove a paying buyer's seat by hand, their next renewal adds it back; unlink the product or end their plan instead.

Refunds

A refund that ends a plan removes the customer's paid seats at Scheduled and Live events that product sells. That's a full or partial refund where staff choose End now, a refund or chargeback from the payment processor, or a purchase reversed through the API or MCP. The buyer leaves the event's audiences and event.registration_cancelled fires.

The seat stays when:

  • Staff refund but keep the plan running.
  • The customer still has active access through another product sold for the same event.
  • The seat was never paid for: seats from the form, the dashboard, the API or a workflow aren't removed by a refund. The exception is someone who signed up for free and later bought a linked product. Their seat became a paid seat, so a refund that ends that plan removes it.
  • The event has already ended.
  • The payment was an invoice. Invoice refunds don't end a plan, so they never remove a seat; remove it by hand on the event page if needed.

Staff setup

  1. Build and publish the sales page on your Site. Link its product buttons to your product page on your checkout address, for example https://app.contentcreatorlab.cc/products/<slug>?plan=<plan id>. That is your community address unless you set a checkout domain.
  2. Pick the Referral site in Commerce → Affiliates → Program. The site must be published. From then on, every Copy link for affiliates and checkout links gives <your site>/<code>.
  3. Add affiliates on Commerce → Affiliates, and optionally checkout links on the product for partners with a different commission or plans only they can sell (Unlisted plans). Send each partner their copied link.
  4. Add redirects on Sites → your site → Redirects: + New redirect, then From (for example youtube-bio), To (a page or a URL) and, optionally, a Campaign whose UTM tags are added. A redirect works as soon as you save it, with no publish needed. The Hits column counts visits.

Removing affiliates and checkout links

RemoveWhereWhat stops workingWhat's kept
An affiliateCommerce → Affiliates → row → RemoveTheir code on that product, and their checkout links on that product. <referral site>/<code> stops working only if they have no other product with that codePast payments, commissions and their balance
A checkout linkCommerce → Catalog → product → Checkout links → Delete/checkout/<code> and <referral site>/<code> right away (unless the code is also their affiliate code)Past payments and commissions

Both can't be undone. If you might want a checkout link back, Disable it instead. Refunds and chargebacks on earlier sales still take the commission back from the right person.

A sale that's already in checkout when you remove the affiliate or delete the link pays no commission.


Troubleshooting

The affiliate wasn't credited

  • The button isn't a link to your community product (/products/<slug> or /products/<slug>/checkout). Buttons inside a Custom HTML block are never changed.
  • The person isn't an affiliate for that product, so its buttons weren't changed.
  • Two people share the code from before the one-code-one-person rule, so /<code> doesn't add it to buttons. Remove one of them on Commerce → Affiliates and add them again with a new code.
  • The buyer opened another affiliate's link afterwards (last click wins), or more than 30 days passed.
  • The buyer checked out in a different browser or device from the one they clicked in.
  • The checkout link was disabled.

/<code> shows "not found"

  • No Referral site is set, or the link is on a different Site.
  • The Referral site isn't published.
  • A page or redirect already uses that path. The page or redirect wins.
  • The code's product is archived, or the checkout link is disabled.

"Already used by" when saving a code

Another person in this workspace already owns that code, on any product or as a checkout link. Pick a different code.

Copy link gives the community URL, not the Site

  • No Referral site is set, or it isn't published.
  • The code matches a page, redirect or built-in path on the Referral site, so the Site can't serve it. Rename the code.

A redirect doesn't work

  • The path has a typo, or a published page uses the same path (the page wins).
  • The site isn't published.

Sales from a redirect don't show as revenue on that campaign

Site analytics credits revenue to the buyer's first touch. Community checkout is always linked, so it carries the Site visit and credits a new buyer to it, including the redirect's campaign. The community remembers the first visit for 30 days, so it still counts when the buyer comes back to a product, checkout or join page without pw_site and pw_vid in the address (a new tab, a bookmark, a cleaned-up link). It's lost only in a different browser or device. A buyer whose first touch was recorded elsewhere keeps that first touch, so the sale stays with that earlier campaign. The visit itself always shows under the campaign.


Open items

  • A visit to /<code> is counted in Site analytics as a visit to /.

Member access journey

How people sign in to your community (email link or code, Google, Discord, passkeys), how Planeward decides whether they're a member, a team member, a past customer or not in yet, and how buyers confirm their email before they pay.

Money journey

How a customer's payment becomes revenue-share credits on your treasury and member accounts, when it can be withdrawn, and how refunds, chargebacks and manual transactions change it.

On this page

JourneyLinks you can sharePromo codes on StripeWho paysOne code, one personUnlisted plansCheckout links for chosen plansCommission labelWhat a plan givesGranting accessDeleting plans and productsWaitlistTurning it onWhat the buyer seesAccepting and rejectingWith a Checkout formCheckout formsBefore paymentAfter paymentHow the form looksProduct or planWhat counts as answeredGood to knowIcon and galleryIconGalleryWhere buyers see itPayment methods and mobile layoutPayment methodsMobile layoutHow the Site reads a pathHow a sale finds its affiliateWhat happens on a clickAfter the paymentWhere the buyer landsPaid eventsWhat a payment doesWhich events and productsRefundsStaff setupRemoving affiliates and checkout linksTroubleshootingThe affiliate wasn't credited/<code> shows "not found""Already used by" when saving a codeCopy link gives the community URL, not the SiteA redirect doesn't workSales from a redirect don't show as revenue on that campaignOpen items