> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/affiliate-program/sales.md). # Sales Tracking Sales review keeps your affiliate program honest. Every order an affiliate drives starts as a claim — the gap between claim and payment is your chance to catch cancellations, returns, and fraud before money leaves your account. The **Sales** tab is where that review happens. Every affiliate-driven order is recorded, calculated, and held until you approve it. A sale links an order to the affiliate who drove it and stores the order, customer, total sale amount, commission Bloop calculated, and which campaign rules applied. > **Best practice:** Align your review rhythm with your refund window. Approving sales weekly — after the typical return period — means you rarely pay commission on an order that later comes back. Skim for anything unusual (a sudden spike from one affiliate, oddly large baskets) before bulk-approving the rest, and reject cancelled or returned orders promptly so balances stay accurate. ### Sale statuses | Status | Meaning | | -------- | --------------------------------------------------------------------- | | Pending | Recorded and awaiting your review. Not yet payable. | | Approved | Valid and confirmed. Counts toward the affiliate's payable balance. | | Rejected | Declined (e.g. cancelled order, fraud, returned). No commission owed. | | Paid | Included in a completed payout. | A sale starts as **pending**. Approve it to make the commission payable, or reject it to dismiss it. Once included in a payout, it becomes **paid**. Nothing is payable until you approve it — pending is a holding pen, not an obligation. ### How commission is calculated When an order comes in through an affiliate link, Bloop calculates the commission from the affiliate's campaign: * For a **percentage** campaign, the commission is a percent of the qualifying sale amount. * For **flat per order** (`amount_order`), it is a fixed amount for the whole order. * For **flat per item** (`amount_item`), it is a fixed amount times the qualifying item quantity. The qualifying amount respects the campaign's exclusions — excluded products or collections, discounts, shipping, taxes, and tips are removed from the base as configured. Tiered campaigns pick the rate the order total qualifies for, and product-specific rates override the campaign rate for listed products. See [affiliate campaigns and commissions](/affiliate-program/campaigns.md) for the full rules. If the campaign has a maximum cap, the commission is limited to it. Each sale stores a snapshot of the campaign rule that applied (its name, type, value, and which exclusions were active), so you can always see why the commission came out the way it did — even if you have since changed the campaign. ### When to approve and when to reject | Situation | Decision | Why | | ----------------------------------------------------------------------------------------- | ---------------------- | --------------------------------------------------------------------------------------- | | Order fulfilled, past the return window, nothing odd | Approve | Real revenue; commission is genuinely owed. | | Order cancelled before fulfilment | Reject | No revenue, so no commission. | | Order returned or refunded | Reject | The revenue reversed; don't pay on money you gave back. | | Within the return window, otherwise normal | Wait, then approve | Approve after the window so a late return doesn't leave you paying on a reversed order. | | Suspicious pattern (self-referral, coupon abuse, spike of tiny orders from one affiliate) | Reject and investigate | Protects the program from fraud before money leaves. | | Manual/offline sale you can verify | Approve | Legitimate revenue tracked outside the normal flow. | **Approve what represents revenue you have kept, reject what reversed or never existed, and wait when the outcome is still in doubt.** ### Adding a sale manually If a sale happened outside normal tracking — for example an offline order or a missed attribution — you can record it by hand: 1. In the **Sales** tab, create a new sale. 2. Select the affiliate it belongs to. The affiliate must be **approved**; sales cannot be created for pending or rejected affiliates. 3. Enter the order details, total sale, and commission. Manual sales are flagged so you can tell them apart from automatically tracked ones. Verify the order is real first — a manual sale skips the automatic tracking that would otherwise vouch for it. ### Approving sales Review pending sales and confirm the valid ones: * Approve or reject an individual sale from its record, or * Select multiple sales and **bulk approve** them. Approving a sale updates the affiliate's approved balance and sends them an approval email. Rejecting sends a declined email instead. If you later delete or change a sale, Bloop recalculates the affiliate's approved balance automatically. A practical rhythm: filter to **pending**, scan for anything unusual, handle exceptions individually (reject returns and oddities), then bulk-approve the clean remainder. ### A worked example: a week of sales review *The numbers are illustrative.* 1. **The queue.** It is Monday. Your campaign pays 15% with shipping and tax excluded. Over the past week, Bloop recorded six pending sales across three affiliates. 2. **The clean ones.** Four are normal fulfilled orders past your 14-day return window. A $60 order (product base after exclusions: $60) shows a $9 commission; an $80 order shows $12; and so on. They check out against the rule snapshot, so you bulk-approve all four. 3. **The return.** One $120 order was refunded on Friday. Its $18 commission is not owed, so you **reject** it. The affiliate's approved balance never includes it. 4. **The one to wait on.** One $200 order shipped just two days ago — still inside the return window. You leave it **pending** and let next week's review catch it once the window closes. 5. **The result.** Four sales approved, one rejected, one held. Your approved balances reflect only real, kept revenue. ### Exporting sales Export your sales to CSV from the **Sales** tab. The file includes the order ID, campaign, affiliate name and email, customer, total sale, SKUs, commission, status, created date, and any note — useful for accounting and reconciliation. ### Common mistakes to avoid * **Approving before the return window closes.** Approve a sale, the order comes back, and you have committed commission on reversed revenue. Time your approvals just after your typical return period. * **Bulk-approving without a skim.** Running bulk approval blind waves through returns, cancellations, and fraud. Scan for the odd ones first. * **Ignoring suspicious patterns.** A sudden spike of tiny orders from one affiliate, or self-referral signals, deserve a closer look before approval, not after payout. * **Letting pending sales pile up unreviewed.** A growing pending queue hides both money you owe and problems you have not caught. Review on a steady cadence. * **Recording manual sales without verifying the order.** Manual entry skips automatic tracking, so an unverified manual sale is a commission with nothing vouching for it. ### Related * [Affiliate campaigns and commissions](/affiliate-program/campaigns.md) — the rules that set each commission. * [Affiliate payouts](/affiliate-program/payouts.md) — turn approved sales into payments. * [Managing affiliates](/affiliate-program/affiliates.md) — the affiliates behind each sale. * [Paying affiliates reliably](/best-practices/paying-affiliates.md) — the rhythm that turns approvals into trust. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.bloop.plus/affiliate-program/sales.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.