Reporting sales correctly: order IDs and proof

0:00 Reporting sales correctly

Two creators each sell thirty headsets with their codes. One gets paid in full, on time. The other waits six weeks and loses a third of the payout in a dispute. The difference wasn't sales. It was reporting. In this lecture you'll learn what a good sales report contains, how to collect proof while protecting buyers' privacy, how to handle cancellations, duplicates and ineligible orders, and a sales log with formulas that catches mistakes before you submit.

0:33 Why it matters

Why does it matter? When your earnings depend on reported sales, accuracy is everything. Brands and platforms pay based on data they trust. Accurate, well-evidenced reports get paid faster, build your reputation, and qualify you for better campaigns. Inaccurate reports, even honest mistakes, can delay payment or trigger an investigation. Think of reporting as part of the job, not paperwork after it.

1:00 The expense claim

Here's the analogy. A sales report is like an expense claim at work. Attach the receipt, fill in the date and amount, claim each item once, and don't claim the personal lunch. Finance pays clean claims quickly and questions messy ones. Brands work exactly the same way.

1:20 A good report

So what goes in a good report? Always follow the campaign brief first. In general: the order ID from the brand's system. The date and time of purchase. The code or link used. The order value and currency. The products, if requested. And proof, exactly as specified: a platform-generated confirmation, or a screenshot the buyer chose to share with you, with personal details redacted.

1:48 Protecting buyers

Now privacy. Proof of sale often includes personal data. So only collect what the campaign needs. Ask the buyer's permission before using any screenshot. Redact names, addresses, phone numbers, emails and payment details unless the brief specifically requires them. Store evidence securely, and delete it when it's no longer needed. And never, ever post buyers' order details publicly as proof of how well you're selling.

2:16 When buyers say no

What if a buyer doesn't want to share anything? Respect it, completely. Say thank you, and don't ask again. Many programmes don't need buyer proof at all, because the code on the order record is the evidence, so check the brief before asking anyone for anything. Where proof is required, platform-generated confirmations are best, because they come straight from the system and include nothing extra. And never offer buyers a reward for sending screenshots. That turns a courtesy into an incentive, and it can look like you're manufacturing orders.

2:55 Redaction in practice

Redaction, done properly, takes ten seconds. Open the screenshot in any editor with a blur or box tool. Cover the name, address, phone number, email and payment details. Leave the order number, date, value and products exactly as they are, because those are what the brand verifies. Don't crop so tightly that the platform's layout disappears, and never retype or rearrange anything. Then save it in one restricted folder, named by order ID, and set a reminder to delete the folder when the campaign's dispute period ends.

3:33 Edge cases

The edge cases. Duplicates: check your log before submitting, and never report the same order twice. Cancellations and returns: if you learn an order was cancelled, update or withdraw the report as instructed. Ineligible orders: don't report orders from excluded regions or products. And unclear cases: ask support before submitting, rather than guessing. When in doubt, leave it out and ask.

4:00 Example 1: Usman, Islamabad

First example. Usman, a tech creator in Islamabad, gets DMs from buyers saying they used his code. The campaign needs order IDs. He replies: thank you so much, if you're happy to, could you share the order number and date? Please don't send your address or phone. He logs each one, checks for duplicates, and submits weekly. When one buyer later cancels, he updates his report. His payouts arrive without disputes, and the brand invites him back.

4:33 Example 2 (illustrative): Dubai creator

Second example, a realistic business scenario with illustrative numbers. A Dubai creator reports forty-two orders at the end of a campaign, all on the last day. The brand's checks find six duplicates, four orders from Oman, which wasn't eligible, and three that were cancelled. Thirteen problems out of forty-two makes the brand distrust the whole batch, and it holds the payout while it reviews every order. Illustratively, the payout arrived five weeks late. Next campaign, she logs orders daily and submits weekly with the formulas from the lesson. Zero queries.

5:12 Watch me do it: the self-checking log

Watch me do it. I open my sales log and add the three formulas from the lesson. In the duplicate column: count how many times this order ID appears; if more than once, show DUPLICATE. In a warning column: if I haven't submitted and we're within three days of the deadline, show SUBMIT NOW. In a ready column: if the region is eligible, the product is eligible, the proof is redacted and there's no duplicate, show READY. I paste in this week's orders. One row shows DUPLICATE: a buyer messaged twice. One shows CHECK: it's a bundle, which is excluded. I remove both and submit the rest.

5:59 Timing

A quick word on timing. Submit within the campaign window and any reporting deadline. Don't batch everything to the last day, because that's when mistakes happen and when support is busiest. Keep a running log as sales come in, and submit weekly if the programme allows it. Weekly reporting also shows you early if something's wrong, like a code that stopped working.

6:26 Know the rules on day one

One more point on timing that saves real trouble: read the reporting rules in the brief before the campaign starts, not after. Some programmes want reports within a set number of days of each sale. Some close the reporting window the moment the campaign ends. Some only accept reports through a specific form or dashboard, never by email or DM. Put the deadline and the submission route in your terms sheet on day one, and set calendar reminders. The creators who miss payouts are rarely dishonest. They're usually just late.

7:05 Common mistakes

Common mistakes. Submitting estimates as confirmed sales. Reporting orders you think came from you, without evidence. Editing screenshots beyond redacting personal data, even just to tidy them. That's altering evidence. Collecting more personal data than needed. Missing deadlines. And forgetting to withdraw cancelled orders, which makes every other report you submit look less trustworthy.

7:28 Measure it

How do you measure your reporting? Track your acceptance rate: accepted orders divided by submitted orders. Aim for close to all of them. Track days from submission to payout. Track the number of queries per campaign. And track how many orders you withdrew yourself because you spotted a problem first. That last number is a good sign. It means your process is catching mistakes before the brand does.

7:58 Recap + try this now

Recap. Follow the brief. Include order ID, date, code or link, value and consented, redacted proof. Log sales as they happen, check for duplicates, update for cancellations, and never report ineligible orders or edited evidence. Protect buyer privacy: collect the minimum and delete it when you're done. Try this now: build the sales log from the lesson with the three formulas, and paste in your current campaign's orders. Next, avoiding fraud and self-dealing.