Avoylo

Avoylo Billing & Payment Policy

Version: 0.1 Last Updated: September 28, 2026 Effective Date: [TBD BEFORE PUBLICATION]

This Billing & Payment Policy defines how Avoylo calculates Seller charges, records billing events, creates billing statements, accepts Seller payments, handles shipping pass-through costs, and corrects billing or payment errors.

This Policy applies to the initial Avoylo pilot pricing model unless Avoylo publishes a later pricing version or a more specific written agreement applies.

This Policy should be read together with the Avoylo Operations Policy, Seller Services Policy, Host Services Policy, Claims & Incident Policy, Shipping & Carrier Policy, and applicable Terms of Service.

Where a narrower service-specific pricing rule or written agreement expressly conflicts with this Policy, the narrower rule controls for that specific service or transaction.

1. Core Billing Principles

Avoylo billing follows these principles:

  1. The server is authoritative. A browser, client application, Seller-entered number, or payment-provider screen does not determine the amount owed.
  2. Operational events create charges. Charges arise only from defined authoritative events and accepted pricing rules.
  3. Historical charges are auditable. Avoylo does not silently rewrite completed financial history.
  4. A charge is billed once. The same underlying financial event must not appear in more than one payable statement unless a separately identified correction is required.
  5. Retries do not create extra charges. Repeated scans, uploads, requests, retries, or lost client responses do not create duplicate financial events.
  6. Payment-provider status is verified server-side. A payment is not marked paid from a browser callback alone.
  7. Shipping pass-through costs remain separate from Avoylo service revenue.
  8. Current pilot storage compensation belongs 100% to the Host. Avoylo takes no storage allocation under the current pilot pricing policy.

2. Billing Currency

Unless Avoylo expressly states otherwise for a particular market or agreement, Seller billing under the initial pilot is denominated in United States dollars (USD).

A statement must identify its currency.

Avoylo must not silently combine financial entries denominated in different currencies into one payable amount.

If additional currencies are supported later, each currency must have separately defined billing and reconciliation rules.

3. Authoritative Financial Records

Avoylo's authoritative financial source is its server-side immutable or append-only financial record system.

Provider transaction history, browser state, invoices displayed in the interface, and payment-provider receipts are supporting evidence but do not replace Avoylo's internal financial journal.

Where an operational or financial event must be corrected, Avoylo records an auditable correction, credit, reversal, compensating entry, or other linked financial event rather than silently overwriting completed history.

4. Pilot Seller Service Charges

The initial pilot Seller service charges are:

ChargeSeller charge
Inbound handling$0.40 per Parcel
Outbound handling$1.70 per Parcel
StorageAccepted Seller storage bid × authoritative Parcel volume × authoritative storage time
Carrier postagePass-through actual provider cost
Paid carrier pickup or similar carrier feePass-through actual provider cost

These rates apply only to the applicable pilot pricing version.

A later pricing version may change prospective rates but must not silently rewrite historical Accepted Terms or already completed financial events.

5. No Mandatory Seller Subscription in the Pilot

The initial pilot does not require a recurring Seller subscription merely to use the basic storage and handling model.

The initial pilot also does not impose a general monthly minimum spend unless Avoylo separately discloses and the Seller accepts a later pricing rule.

Seller charges are usage-based under the applicable Accepted Terms and service rules.

6. Storage Price Source

For each Placement, the applicable storage rate is the Seller's valid storage offer that was frozen when the Host successfully accepted the Placement.

The historical accepted rate remains linked to that Placement.

A later change to Avoylo's recommended rate, Avoylo's minimum rate, the Seller's offer for future inventory, or a later pricing-policy version does not retroactively change the accepted rate for an existing Placement unless a lawful, expressly authorized correction applies.

7. Storage Calculation

Storage is calculated using the authoritative Parcel volume, the accepted storage rate, and the Parcel's authoritative time in Host storage.

The economic formula is:

Parcel volume in cubic feet × accepted USD per cubic foot per day × elapsed storage seconds ÷ 86,400

Avoylo maintains high-precision source accounting.

Intermediate storage calculations must not be prematurely rounded in a way that materially changes the amount owed.

Display formatting or payment-provider minor-unit conversion occurs only at the appropriate statement or settlement layer.

8. Storage Start Event

Storage accrual begins at the Parcel's authoritative STORED timestamp.

The following do not start storage billing by themselves:

A carrier showing an inbound shipment as delivered does not start Host storage billing until Avoylo records the required Host receipt and authoritative STORED event.

9. Weekly Storage Segments

Under the pilot policy, open Host storage is divided into deterministic UTC billing segments.

The weekly boundary is:

Monday 00:00:00 UTC

Rules:

A scheduler is an execution mechanism only. It does not define the economic period.

10. Normal Outbound Storage Exit

For ordinary customer fulfillment, Host storage ends at the authoritative CARRIER_ACCEPTED provider occurrence timestamp.

Storage does not end at:

If the carrier acceptance event reaches Avoylo later than the actual carrier scan, the trustworthy provider occurrence time controls rather than Avoylo's later ingestion time.

This prevents webhook or provider-delivery delay from increasing the Seller's storage charge.

11. Missed Pickup and Storage

If a Parcel reaches HANDOFF_READY but the carrier does not authoritatively accept it, storage continues.

The Parcel may be moved back into protected Host holding or re-staged through the authorized workflow.

A missed pickup, missing carrier scan, or ambiguous handoff does not create an invented storage-exit time.

Where carrier acceptance remains ambiguous, Avoylo uses the applicable incident and reconciliation process.

12. Host-to-Host Transfer Storage

For an authorized Host-to-Host transfer:

A transfer request, transfer label, staging event, or planned destination does not end source Host storage.

13. Seller Removal or Return-to-Seller Storage

For an authorized removal or return of inventory from a Host to the Seller or another approved recipient:

Where exit evidence is missing or ambiguous, Avoylo does not invent an earlier exit time.

14. Customer Return Entering Avoylo

A customer return does not create Host storage merely because a return label exists or a customer has shipped the package.

A new Host storage lifecycle begins only after the return is authorized for an Avoylo-managed destination, arrives, completes the required receiving workflow, and becomes authoritatively STORED.

If the returned Parcel is blocked, quarantined, damaged, or awaiting review, billing follows the applicable return and storage rules for that state.

15. Inbound Handling Charge

The pilot Seller inbound handling charge is:

$0.40 per Parcel

The charge is created once when the commercially accepted Parcel completes the required Host receipt workflow and reaches its first authoritative STORED event for that inbound Placement.

Repeated scans, storage-confirmation retries, page refreshes, duplicate client requests, or ambiguous client responses must not create a second inbound handling charge for the same inbound event.

16. Inbound Handling and Failed Receipt

No normal inbound handling charge is created merely because the Seller dispatches the Parcel, the carrier is in transit, the carrier reports delivery, the Host starts RECEIVING, or an unknown or unauthorized Parcel appears.

A Parcel blocked before authoritative STORED remains subject to the applicable discrepancy, return, removal, shipping, or other policy.

Extra costs caused by an unauthorized or misdeclared shipment are separate from the normal $0.40 inbound handling charge and may be billed only where another applicable policy or agreement authorizes them.

17. Outbound Handling Charge

The pilot Seller outbound handling charge is:

$1.70 per Parcel

The normal outbound charge is created once when the assigned Parcel successfully completes Avoylo's required Host-side outbound work and reaches authoritative HANDOFF_READY.

The relevant outbound work ordinarily includes retrieving the exact assigned Parcel, QR or identity verification, applying the authorized shipping label, staging the Parcel, and providing required staging evidence.

This is one handling event.

18. No Duplicate Outbound Handling Fee for Retries

Avoylo does not create a second normal outbound handling charge merely because the Host rescans the same correct Parcel, retries a failed request, reprints the same still-valid label, replaces a required staging photograph, refreshes the task, loses a client response, or repeats an idempotent action needed to complete the same outbound event.

The same completed outbound task must not generate duplicate handling revenue.

19. Failed Pickup Does Not Create a Second Normal Outbound Charge

If a properly staged Parcel reaches HANDOFF_READY and the carrier misses pickup, the normal $1.70 outbound handling charge is not charged again merely because the Host re-secures or re-stages the same Parcel for the same fulfillment task.

A second outbound handling charge requires a genuinely new billable fulfillment event under a separately authorized rule, not a retry of the same task.

20. Cancellation and Handling Charges

Cancellation does not automatically erase a handling charge already earned by a completed authoritative operational event.

Any credit or correction follows the applicable correction rules in this Policy and other governing terms.

21. Carrier Postage Is a Pass-Through Cost

Carrier postage is separate from Avoylo's inbound, outbound, and storage service charges.

Under the initial pilot:

Avoylo does not add a shipping markup to ordinary carrier postage.

The Seller is charged the applicable carrier/provider cost actually incurred or authoritatively adjusted for the Seller's shipment.

The pass-through amount may include, where actually imposed by the provider:

A pass-through cost remains separate from Avoylo service revenue in the financial records.

22. No Hidden Shipping Margin in the Pilot

Avoylo does not silently convert provider postage into a higher undisclosed shipping price during the pilot.

If Avoylo later introduces shipping markup, negotiated-rate sharing, a shipping platform fee, insurance fee, protection fee, or another shipping-related Avoylo charge, that charge must be separately disclosed in a later pricing version or applicable agreement before it applies prospectively.

23. Carrier Adjustments

A carrier may adjust a shipping charge after label creation or shipment because of measured weight, dimensional weight, address correction, service change, package characteristics, pickup fee, return, surcharge, or another provider adjustment.

A later authoritative provider adjustment may create an auditable Seller debit or credit.

Avoylo must not silently edit an already completed historical postage record.

24. Aggregated Billing Statements

Avoylo does not ordinarily initiate a separate Seller payment for every small operational event.

Individual financial events are recorded first.

Eligible charges are then aggregated into a Seller billing statement.

A statement may include storage segments, inbound handling, outbound handling, carrier postage, carrier pickup, carrier adjustments, returns, transfers, removal costs, authorized corrections, credits, and applicable taxes where required.

25. Weekly Statement Cycle

The pilot Seller billing cycle is weekly.

The standard billing-period boundary is:

Monday 00:00:00 UTC

Avoylo may generate the statement shortly after the boundary once eligible financial events have been reconciled.

A statement covers eligible unbilled entries through its cutoff.

If there are no billable entries, Avoylo is not required to generate a zero-dollar payable statement.

A final or off-cycle statement may be generated for Seller account wind-down, material correction, operational closure, provider reconciliation, or another legitimate billing reason.

26. One Financial Entry, One Payable Statement

An immutable Seller charge entry may be included in at most one active or paid billing statement.

Avoylo must prevent the same underlying charge from being collected through multiple statements.

If a statement is replaced before payment, the replacement process must preserve audit history and must not cause both the old and new statement to remain independently payable for the same entries.

27. Statement Locking

Before Seller payment begins, Avoylo locks the applicable billing statement.

A locked statement fixes the included financial entries, currency, exact total, relevant corrections then included, and the statement's payment identity.

The browser cannot change the statement amount after lock.

A payment-provider order must be created from the locked server-side amount.

28. No Silent Mutation During Payment

Once a billing statement is LOCKED or PAYMENT_PENDING, Avoylo must not silently change its included entries or total while the payment is in progress.

A financial correction affecting a locked or payment-pending statement must use an authorized safe path, such as voiding/replacing the unpaid statement where safe, waiting for the payment state to resolve, or posting a separate compensating credit/debit after settlement.

29. Statement Status

Avoylo may expose statement states such as:

DRAFT

The statement is not yet fixed for payment.

LOCKED

The included entries and total are fixed for the current payment attempt.

PAYMENT_PENDING

A provider payment attempt exists or payment outcome is not yet safely final.

PAID

Avoylo has authoritative server-side evidence of successful settlement and has recorded the payment settlement.

A browser displaying success does not itself create PAID.

30. Payment Due Date

Under the initial pilot, a Seller billing statement is due within 7 calendar days after issuance, unless a different due date is expressly shown on the statement or agreed in writing.

Avoylo may send reminders before or after the due date.

A payment is not considered completed merely because the Seller initiated checkout.

The statement is satisfied only after authoritative settlement confirmation.

31. Past-Due Accounts

If a statement becomes past due, Avoylo may restrict new paid activity under the applicable agreements.

Restrictions may include new inbound Placements, new replenishment, new optional services, or other prospective activity.

Past-due status does not eliminate Avoylo's or the Host's existing custody and safety obligations for inventory already in the network.

Any stronger suspension, inventory hold, removal, or account-termination right must follow the applicable Seller agreement and law.

32. PayPal as Initial Seller Payment Provider

The initial Seller payment provider is PayPal Business.

The pilot uses statement-based, one-time checkout rather than a mandatory recurring subscription.

Avoylo may later add or replace payment providers, but changing the payment rail does not replace Avoylo's authoritative billing records.

Seller payment remains tied to the applicable Avoylo billing statement.

33. PayPal Checkout Experience

For eligible Sellers, Avoylo may render PayPal-provided checkout controls inside the Avoylo Billing interface.

The Avoylo server creates the payable PayPal order from the locked billing statement.

The Seller must not type or alter the authoritative amount payable to Avoylo.

PayPal may determine which eligible payment methods it presents based on the Seller's region, device, account, browser, and provider rules.

Avoylo does not guarantee that every PayPal-supported payment method will appear to every Seller.

34. No Separate PayPal Processing Surcharge in the Pilot

Under the initial pilot, Avoylo does not add a separate Seller-facing surcharge solely because the Seller pays the Avoylo statement through PayPal.

Avoylo's own payment-processing cost is not added as a separate PayPal fee line under this version.

A later pricing version may change this prospectively only if clearly disclosed before the applicable transaction.

35. No Browser-Controlled Payment Amount

The Seller's browser never determines the amount Avoylo asks PayPal to collect.

The server derives the Seller, billing statement, currency, and amount from Avoylo's authoritative records.

A manipulated browser request attempting to substitute another amount, another Seller's statement, or another currency is invalid.

36. Payment Approval Is Not Yet Settlement

PayPal approval and Avoylo settlement are distinct steps.

A Seller approving a PayPal order does not alone mean the billing statement is PAID.

Avoylo marks the statement paid only after the server verifies the expected provider order, Seller ownership and statement identity, expected currency, expected amount, authorized capture result, and one immutable Avoylo settlement.

37. One Settlement Per Statement

A billing statement may have only one authoritative successful Avoylo settlement.

Retries must reuse or recover the existing provider attempt where possible.

A retry must not create another payable economic obligation for the same statement.

Avoylo uses idempotency, durable payment-attempt records, provider readback, or equivalent controls to prevent duplicate settlement.

38. Ambiguous or Lost Payment Response

If the Seller approves payment but the browser closes, the network disconnects, the Seller refreshes, Avoylo loses the client response, the provider response is delayed, or the outcome is otherwise uncertain, the Seller should not immediately pay the same statement again.

Avoylo keeps the statement in an appropriate pending state and reconciles the stored/provider status.

The Billing interface should provide a status-check or recovery path where supported.

39. Browser Cancellation

Closing or cancelling the PayPal checkout interface does not automatically mean the provider order never existed, capture definitely failed, the statement should be unlocked immediately, or the Seller should create a second payment.

Avoylo determines the authoritative provider/payment state before allowing another attempt that could create duplicate settlement risk.

40. Duplicate Clicks and Retries

Repeated Pay button clicks, network retries, browser reloads, or repeated create/capture requests must not create multiple Avoylo settlements for one statement.

Where the provider returns the same successful payment on replay, Avoylo returns or reconciles the original paid result.

Where a changed request attempts to reuse an idempotency identity with inconsistent details, Avoylo may reject the request.

41. Verified Duplicate Provider Payment

If Avoylo verifies that the Seller was actually charged more than once for the same billing statement, the excess payment is treated as a duplicate payment.

A verified duplicate payment:

If direct provider refund is unavailable, Avoylo may use another lawful refund path or, with the Seller's agreement, an account credit.

42. Duplicate Payment Investigation

Before issuing a duplicate-payment remedy, Avoylo may verify provider order IDs, capture IDs, amount, currency, statement identity, provider status, settlement record, and timing.

A duplicate browser message is not proof of duplicate settlement.

43. Billing Corrections Before Payment

If Avoylo identifies an error while a statement is still safely editable and no conflicting payment is pending, Avoylo may correct the draft statement before payment.

The correction must remain traceable to the underlying financial entries.

Avoylo must not silently change an amount after the Seller has begun approving a locked payment.

44. Billing Corrections After Lock but Before Settlement

If a correction is required after statement lock:

45. Billing Corrections After Payment

A PAID statement is never silently rewritten to change what the Seller originally paid.

A verified post-payment correction is recorded separately as an auditable credit, debit, compensating entry, refund, supplemental charge, or other supported adjustment.

The original statement and original settlement remain historically intact.

46. Overcharge Corrections

If Avoylo verifies that a Seller was overcharged:

By default, an ordinary non-duplicate billing correction may be credited against the Seller's next billing statement.

If the Seller is closing the account, has no reasonably expected future bill, or Avoylo determines direct refund is more appropriate, Avoylo may refund the applicable amount through the original payment provider where technically available.

47. Undercharge Corrections

If Avoylo verifies that a Seller was undercharged because of an auditable billing error or later authoritative provider adjustment, Avoylo may create a supplemental charge.

A supplemental charge must identify the underlying event, preserve the original record, explain or categorize the correction, use the applicable historical pricing or provider cost, and appear in a later statement or other expressly authorized billing process.

Avoylo must not retroactively change a historical rate merely to create a higher undercharge.

48. Compensation and Corrections During Payment

A financial correction affecting entries already contained in a LOCKED or PAYMENT_PENDING statement must not race with payment settlement.

Avoylo may temporarily reject or defer the correction until the statement's payment state is safely resolved.

49. Statement Reconciliation

Avoylo may run reconciliation checks comparing immutable Seller charge entries, statement line items, statement total, provider order, provider capture, payment settlement, credits, corrections, and provider webhook evidence.

A paid statement with missing or contradictory payment evidence may be flagged for investigation rather than treated as automatically normal.

Reconciliation itself must not silently alter immutable history.

50. Provider Webhooks Are Evidence, Not Sole Authority

Verified PayPal webhook events may be used as payment evidence and reconciliation input.

A webhook event alone does not automatically rewrite a Seller statement to PAID where Avoylo's approved capture/settlement path requires additional confirmation.

Out-of-order or delayed provider events must be reconciled by provider occurrence/status semantics rather than blindly applying arrival order.

51. Refund to Original Payment Method

Where Avoylo issues a PayPal refund and the provider supports the refund, Avoylo will ordinarily send the refund through the original provider transaction.

Provider processing time is outside Avoylo's direct control.

A refund initiated by Avoylo is not represented as completed until Avoylo has sufficient provider evidence of the refund state.

52. Seller Billing Disputes

A Seller that believes a statement contains an error should use Avoylo's billing-support or dispute process and identify the affected charge.

Avoylo may confirm the charge, correct the charge, issue a credit, issue a refund, create a supplemental adjustment, or keep the charge unchanged based on the authoritative record.

Submitting a dispute does not automatically invalidate unrelated undisputed charges.

53. PayPal Disputes and Chargebacks

A PayPal dispute, chargeback, or payment-provider reversal does not automatically erase the underlying Avoylo service charge.

Avoylo may provide provider-requested evidence concerning billing statements, accepted pricing, storage periods, handling events, shipping, payment authorization, and other relevant transaction evidence.

If the provider reverses a payment, Avoylo may restore the underlying unpaid balance where permitted by the applicable agreements and law.

54. Claims Are Separate From Billing

An operational Incident or Claim does not automatically cancel a Seller charge.

Billing corrections occur only where an applicable rule, verified billing error, approved remedy, provider adjustment, or authorized decision requires a financial correction.

Claims, loss, damage, and protection matters are governed primarily by the Claims & Incident Policy and any applicable protection, carrier, or insurance terms.

55. No Automatic Offset Against Host Earnings

Seller billing and Host earnings are separate accounting perspectives linked to the same underlying events where applicable.

A Seller dispute does not automatically erase an already recorded Host earning.

A Host payout adjustment requires the applicable Host Earnings & Payout Terms and an auditable financial correction.

56. Storage Accounting Split

Under the current pilot pricing policy:

Seller storage charge = Host storage earning

and:

Avoylo storage allocation = $0

Avoylo must not create a hidden Avoylo storage margin by posting an undisclosed storage allocation.

A later pricing policy may change the economics prospectively, but historical Accepted Terms remain preserved.

57. Inbound and Outbound Internal Allocation

For the current pilot:

Inbound

Seller charge: $0.40 per Parcel Current Host earning: $0.25 per Parcel Current Avoylo allocation: $0.15 per Parcel

Outbound

Seller charge: $1.70 per Parcel Current Host earning: $1.00 per Parcel Current Avoylo allocation: $0.70 per Parcel

These internal allocations correspond to the current pilot pricing version and are preserved in immutable accounting.

A retry of the same event does not create another allocation.

58. Payment Processing Fees

Under the current pilot, Avoylo's ordinary PayPal processing cost is not separately passed through as a Seller payment-processing surcharge.

This does not prevent Avoylo from changing future pricing prospectively through a later disclosed policy version.

Carrier pass-through costs remain separate from payment-processing costs.

59. Taxes

Where applicable law requires Avoylo to collect, remit, or display taxes on Avoylo's own services, Avoylo may add the required tax amount to the statement.

The Seller remains responsible for taxes imposed on the Seller's own retail sales, products, business, imports, or other obligations unless applicable law expressly places the responsibility on Avoylo.

60. Account Closure and Final Billing

Seller account closure does not erase accrued charges.

Before operational closure, Avoylo may generate a final statement containing eligible unbilled amounts such as storage through authoritative exit, completed inbound handling, completed outbound handling, postage, carrier adjustments, transfers, removal, returns, and authorized corrections.

Any Seller credit remaining after final reconciliation is handled under the applicable refund or account-closure process.

61. Long-Term Inventory and Billing

Inventory remaining in storage continues to accrue storage charges according to the applicable Accepted Terms until an authoritative storage-exit event occurs.

Seller inactivity, account-closure request, nonpayment, or an instruction to remove inventory does not by itself stop storage accrual while physical custody remains with the Host.

62. Payment Does Not Change Physical Custody

Paying a statement does not by itself change Parcel custody, storage state, shipment state, Host assignment, or carrier acceptance.

Likewise, a physical custody event does not by itself prove payment settlement.

Operational and financial state machines remain linked but distinct.

63. No Cash Payment to Host

A Seller must not pay a Host directly for ordinary Avoylo storage or handling in order to bypass Avoylo billing.

Host earnings are recorded and paid through Avoylo's separate Host earnings and payout process.

A Host must not demand direct payment from the Seller for an ordinary Avoylo task.

64. No Off-Platform Fee Avoidance

A Seller or Host must not use nonpublic Avoylo information to move an Avoylo Placement or fulfillment relationship off-platform for the purpose of avoiding applicable Avoylo billing or custody controls.

Any restriction or consequence is governed by the applicable Terms of Service and user agreements.

65. Payment Security

The Seller must never be asked to provide Avoylo with the Seller's PayPal password.

Avoylo keeps payment-provider secrets server-side.

A browser may receive only information intentionally safe for the browser, such as public provider identifiers or short-lived browser-safe configuration required for the enabled checkout flow.

Avoylo must not expose its PayPal Client Secret through browser assets or ordinary API responses.

66. Provider Availability

Avoylo does not control PayPal availability, account eligibility, provider maintenance, or provider-specific payment-method availability.

If PayPal is unavailable, Avoylo may keep a statement unpaid or pending until an approved payment route becomes available.

Avoylo must not mark a statement paid merely because the provider interface failed.

67. No Live Payment Before Activation

Sandbox, development, or test payment activity does not create a real Seller payment obligation.

Avoylo will not treat Sandbox provider transactions as live commercial settlement.

Live payment collection begins only after the applicable live payment environment and Avoylo live-payment controls are intentionally activated.

68. Versioning

Avoylo may update this Policy and its pricing versions prospectively.

Each published version should identify its effective date or last-updated date.

A new pricing version does not silently rewrite historical Accepted Terms, completed operational events, paid statements, or prior provider settlements.

Where legally required or contractually promised, Avoylo will provide appropriate notice before a material change becomes effective.

69. Related Policies and Contact

This Billing & Payment Policy should be read together with:

Billing Support: [TBD] Payment Support: [TBD] Legal Contact: [TBD] Company Legal Name: [TBD] Business Address: [TBD]