What counts as a qualified quote: how partner commission is validated
Every partner program has to answer one question before anyone trusts it: what, exactly, earns a reward? For PackOS that answer is a qualified quote — a server-validated event, not a click a browser can fake. Here is precisely what qualifies, what does not, and why drawing the line this way protects the partners doing honest work.
THE SHORT ANSWER
A qualified quote is a real file that clears detection on our servers — validated where a partner's browser cannot tamper with it. Commission attaches to that event, never to a bare click or a junk upload. The program is in early access; this article describes how validation is designed to work, not a live earnings claim.
- Server-side only — the count that pays is computed on PackOS, not reported by the embed
- A real file past detection — it must parse into a spec, not be a blank or corrupt upload
- Counted once — the same file re-submitted does not qualify twice
- Tied to your partner key — traffic is attributed to you, and obvious bot floods are screened out
- Hybrid reward — a bounty on the qualified quote plus rev-share on a resulting order; rates published to partners at signup
What a qualified quote is
A qualified quote is the event PackOS rewards a partner for: a genuine buyer, arriving through your link or your embedded quote widget, uploads a real packaging file that our pipeline successfully reads into a spec. That is the moment intent becomes measurable. It is not a page view, not a click, and not a form someone half filled out — it is a file that our servers detected, deduplicated, and attributed to your partner key.
The distinction matters because packaging is a high-intent referral. A buyer who has a die file or artwork in hand and drops it into a quote tool is not browsing — they are specifying. Rewarding that specific action, rather than the traffic around it, is what keeps the program aligned: partners are paid for sending people who actually want a quote, and PackOS pays for outcomes it can verify.
Why validation happens server-side
Anything a browser reports can be forged. Click counts, "conversions" fired from client-side script, event pixels — all of it can be replayed, inflated, or spoofed by anyone motivated to game a payout. A commission program that trusts the client is a program that eventually pays for traffic that was never real, and honest partners are the ones who quietly lose when that budget drains.
So the number that pays is never the one the embed announces. The PackOS embed is a thin client: it collects the file and a public partner key and hands both off. The upload, the AI detection models, the deduplication, the origin check, and the attribution all run on PackOS infrastructure. The embed cannot mark its own quote as qualified — it can only submit a candidate, which the server then validates or rejects. That separation is the whole trust story, and it is the same boundary that keeps a partner's site from ever touching a buyer's file contents or the models behind them.
What makes a quote qualify
A candidate becomes a qualified quote when it clears every one of these server-side checks. None is optional, and they run in order:
- A real file that passes detection. The upload has to parse into a structured spec — dimensions, structure, substrate. A file our quote pipeline cannot read is not a quote; it is a failed upload, and it does not qualify.
- Counted once per file. Each file is fingerprinted on arrival, so submitting the same artwork ten times still counts once. That closes the most obvious way to manufacture events.
- Attributed to your key. The event carries your partner key and is tied to the surfaces you have registered, so a key pasted onto an unrelated domain does not quietly harvest credit.
- Real traffic, not bots. A scripted flood of uploads is screened out, so qualified events reflect real buyers rather than automation.
Only a candidate that survives all four is recorded as a qualified quote and enters the commission ledger. The reward itself is hybrid: a bounty on the qualified quote, plus rev-share if that quote turns into an order. We do not publish the bounty amount or the rev-share rate here — those are shown to partners at signup so the terms you agree to are the terms you see.
What does not count
It is just as important to be explicit about what earns nothing, because a program that is vague here is a program that invites disputes. The following do not qualify:
- Bare clicks and page views. Sending traffic is the start, not the finish. A visit with no submitted, detectable file is not a qualified quote.
- Junk or unreadable uploads. Blank files, corrupt PDFs, screenshots that carry no structure, or anything detection cannot turn into a spec.
- Duplicate submissions. The same file, re-submitted — whether by the same buyer or across sessions — is collapsed by hash to a single event at most.
- Self-dealing and bot traffic. Uploads you generate yourself to trigger a payout, or automated traffic that trips the bot filter, are rejected.
- Mis-attributed traffic. Events that fail the origin check, or arrive outside the attribution window, do not carry commission.
These are guardrails, not gotchas. Every one of them exists to keep the reward pointed at the thing partners are actually good at: putting a real quote tool in front of real buyers who have a real file to price.
How attribution and payouts work
Qualifying is one gate; getting paid is the next, and the mechanics are deliberately simple:
- 60-day last-touch attribution. A qualified quote is credited to the most recent partner touch within sixty days. If a buyer discovers you today and quotes within that window, the event is yours.
- Earnings settle after a short window. Validated commission becomes withdrawable once a brief settling window passes — the same window in which refunds normally surface, so a refunded order simply reverses its share.
- Cash out in fiat or USDC. When you are ready to withdraw, you link a payout account — a bank via Stripe or a USDC wallet — and your balance pays out there. PackOS never holds your funds as a bank.
You can embed, test, and rack up qualified quotes with nothing set up in advance; a payout account only comes into the picture when you decide to cash out. The partner program overview walks through the whole model end to end, and the exact figures live in the program terms you see at signup.
Why this protects honest partners
A commission pool is finite. Every dollar paid on a faked click, a duplicate upload, or a bot flood is a dollar not paid on a real buyer that a real partner sent. Loose validation does not make a program generous — it makes it a target, and the people who suffer are the ones playing straight.
Validating server-side, deduping by hash, and rewarding only detectable files is what lets PackOS keep the terms stable and pay reliably. It also means a partner never has to compete with someone gaming the system: since the count is computed on infrastructure no partner controls, the leaderboard reflects genuine intent, not who wrote the cleverest script. That is the point of drawing the line at a qualified quote — it makes the program worth being honest in.
It is worth adding what this does not change: the buyer experience. There is no spam and no sales call waiting on the other side of a partner link. A buyer uploads a file, gets a price, and decides — the same clean path whether they arrived through a partner or found PackOS directly. Comparing programs on these mechanics is exactly the exercise in our affiliate programs comparison.
Join the early partner list
The partner program is in early access. You can start by embedding the quote widget or sharing a partner link today; commission attaches to server-validated qualified quotes under the rules above, and the specific bounty and rev-share figures are published to partners at signup. If you want the reward pointed at real intent — and pointed away from the freeloaders — this is how that line is drawn. Join the early partner list and we will onboard you as surfaces open up.
Frequently asked questions
What is a qualified quote?
A qualified quote is a server-validated event: a genuine buyer arrives through your partner link or embed and uploads a real packaging file that PackOS detection reads into a spec. The event is deduplicated by file hash and attributed to your partner key. It is the basis for commission under the partner program, which is currently in early access.
Why is commission validated on the server instead of the browser?
Anything a browser reports — clicks, pixels, client-side conversions — can be forged or replayed. To keep payouts real, PackOS computes the qualifying count on its own infrastructure. The embed only submits a candidate with a public partner key; the server runs detection, deduplication, origin and bot checks, then decides whether it qualifies. The embed cannot mark its own quote as valid.
What kinds of activity do not earn commission?
Bare clicks and page views, junk or unreadable uploads, duplicate submissions of the same file, self-dealing uploads meant to trigger a payout, automated traffic caught by the bot filter, and events that fail the origin check or fall outside the attribution window. Only a detectable file that clears every server-side check is recorded as a qualified quote.
How long do I have to earn credit for a buyer I referred?
Attribution is 60-day last-touch: a qualified quote is credited to the most recent partner touch within sixty days. Validated commission then becomes withdrawable after a short settling window — the same window in which refunds normally surface, so a refunded order simply reverses its share. The exact figures live in the program terms you see at signup.
How and when do partners get paid?
When you are ready to withdraw, you link a payout account — a bank via Stripe or a USDC wallet — and your balance pays out there after a short settling window. You can embed, test, and earn qualified quotes with nothing set up in advance; a payout account only comes into the picture at cash-out. The program is in early access, and the exact figures are published to partners at signup.