Key takeaway
A recipient paying for downloads does not make delivery costless for the seller. Agree on each charge, its billed account and its commercial treatment before promising a large package.
Separate the license price from the delivery bill
A company can accept an attractive data-license price and later discover that repeated downloads, retained copies and archive retrieval were left out of its budget. Begin with the proposed delivery: package version, total size, number of objects, storage period, intended destinations and allowed re-downloads. A price for permission to use records does not explain who funds those operations.
Amazon S3's billing documentation distinguishes storage, requests, retrievals and other charges. Size alone is an incomplete cost description. Record the storage class and time as well as the operation. Retained object versions can also be chargeable. The actual account and destination matter; this article does not supply a current AWS tariff or assume that every transfer incurs the same charge.
Prepare two columns: the account the provider bills and the party that bears the cost under the proposed agreement. They may differ if one party reimburses the other. A reimbursement promise also needs a reporting basis, payment trigger and spending limit; it is not evidence that the reimbursement has arrived.
Read the limits of Requester Pays
For successful requests to an S3 Requester Pays general purpose bucket, AWS documents that the requester pays for the request and downloaded data while the bucket owner pays for storage. Requests must be authenticated. If the requester assumes an IAM role, the role's account is billed. Check the actual account arrangement rather than assuming the person clicking download is necessarily paying.
A separate exception matters for archived objects. When RestoreObject is used with Requester Pays, AWS says the requester pays the request cost but the bucket owner pays retrieval charges. Requester Pays is therefore not a switch that transfers every delivery expense. Its documented billing treatment does not allocate preparation, rights review or support between license parties.
Do not enable a billing option and treat it as permission to disclose. The named recipient, permitted package and evaluation or license use still need their own approval. Conversely, an approved license does not prove that the recipient's downloader supports the intended billing arrangement. Test that operational question within an authorized environment before committing to the delivery method.
Complete a charge allocation before quoting
This hypothetical USD model concerns one license, one named recipient, a 2,000 GB package retained for one month and two complete successful downloads. It assumes one 2,000 GB restore and 50,000 billable requests altogether. All rates below are invented flat planning inputs, not AWS prices. GB is the example's agreed billing unit; no allowance, tier, discount or tax is assumed.
Preparation includes eight export/engineering hours and four review hours, all entered at $100 per hour: $1,200. The conditional license receipt is $5,000, paid in full after the assumed acceptance event. Other external fees are entered as zero, with no upfront seller referral fee to VOID. Financing, tax, additional support and future refreshes are outside this one-delivery comparison. Those exclusions are assumptions to review, not claims that real costs disappear.
| Illustrative charge | Calculation | Entered cost |
|---|---|---|
| Storage for one month | 2,000 GB × $0.02 per GB-month | $40 |
| One archive retrieval | 2,000 GB × $0.01 per GB | $20 |
| Two complete downloads | 4,000 GB × $0.06 per GB | $240 |
| Billable requests | 50 groups of 1,000 × $0.10 | $5 |
| Cloud total | $40 + $20 + $240 + $5 | $305 |
Compare the same package with different payers
If the seller bears all five entered costs, its modeled cash contribution is $5,000 minus $1,200 preparation minus $305 cloud costs: $3,495 before tax and the excluded obligations. If the recipient directly bears the hypothetical $245 of request/download charges, the seller still bears $60 of storage/retrieval plus $1,200 preparation, leaving $3,740. This is a $245 allocation difference, not a change in the dataset's value or an expected earning.
The no-deal case assumes preparation and one month's storage are incurred, but no restore or download occurs. Zero receipts less $1,200 and $40 leaves a $1,240 downside. If a sample, restore or attempted delivery already occurred, add its actual cost instead of reusing this no-deal assumption.
A further complete download would add $120 of transfer cost under these invented rates, before any additional requests or other effects. Decide who can initiate repeated downloads and who can approve spending above the agreed envelope. A cap can create a pause or a new commercial decision; it must not silently turn an incomplete delivery into an accepted one.
| Hypothetical outcome | Seller costs | Cash contribution |
|---|---|---|
| Seller bears all cloud costs; $5,000 received | $1,505 | $3,495 |
| Recipient directly bears $245; $5,000 received | $1,260 | $3,740 |
| No deal; preparation and storage only | $1,240 | −$1,240 |
Give the commercial owner a delivery schedule
The useful schedule names the package, billed accounts, storage duration, permitted destinations, request/transfer assumptions, restore treatment and responsibility for failed or repeated attempts. Include the evidence used for reimbursement, its due date and the person authorized to approve an overrun. Ask the cloud owner to check actual region, service, class, minimum-duration and pricing rules; the illustration cannot substitute for that account-specific estimate.
The seller in the example can offer either reviewed allocation while keeping the recipient and package unchanged. If the recipient asks for another account, destination or package version, return the changed scope to technical, permission and commercial review. Keep a temporary storage estimate from becoming an indefinite hosting promise.
Use the earnings calculator for the entered receipt and total seller costs, and attach the charge schedule to offer comparison. VOID's initial referral helps explore fit and a permissioned named introduction; it does not configure a seller's cloud account or take custody of the records. Introduction, sample delivery and a license remain separate decisions.