Daily visibility
Provisional usage estimates show how the organization is trending before the month closes.
Pricing that follows real use
Pay-as-you-go ecommerce with a clear published-store minimum.
Merchant Meadows measures the resources each store consumes, reconciles them to AWS costs, and applies a published pricing policy instead of taking a percentage of sales.
For: Low-volume, seasonal, and growing sellers who want usage-linked software costs
Physical goodsGuest checkoutCustom domainsNo Meadow revenue share
The case for a lighter store
Flat plans make quiet stores subsidize busy assumptions.
Your organization pays the higher of its allocated infrastructure cost plus progressive service markup or its combined published-store floors. We reconcile measured requests, compute, storage, email and background work to AWS billing exports. The floor is a minimum, not an extra charge on top.
Reconciled totals
The usage ledger supplies tenant weights; AWS billing exports remain the authoritative monthly cloud total.
Published progressive markup
Markup is 100% on the first $25 of allocated cost, 50% on the next $75, 30% on the next $400 and 25% above $500. Each rate applies only within its bracket.
The pricing policy
See how the numbers add up.
Allocated infrastructure cost includes store usage and organization-owned dedicated resources. We apply each markup only to the portion of that cost in its bracket. Your service subtotal is the higher of that cost plus the progressive markup or your combined store floors. The floor is not an extra fee added on top.
| Portion of allocated cost | Markup |
|---|---|
| First $25 | 100% |
| Next $75 ($25–$100) | 50% |
| Next $400 ($100–$500) | 30% |
| Above $500 | 25% |
Each rate applies only to its portion of cost. Crossing a bracket does not change the rate on earlier portions.
Illustrative months
Each example shows one store and its published days. Actual usage varies; these are illustrations, not bill forecasts.
A quiet published store
- Allocated infrastructure cost
- $1.00
- Progressive markup
- $1.00
- Published-store floor
- $5.00
- Platform subtotal
- $5.00
$1 of allocated cost plus $1 of markup is below the $5 full-month floor.
Published for half a 30-day month
- Allocated infrastructure cost
- $1.00
- Progressive markup
- $1.00
- Published-store floor
- $2.50
- Platform subtotal
- $2.50
The floor is $5 × 15 ÷ 30 = $2.50, which is higher than $2 of cost plus markup.
$50 of allocated infrastructure
- Allocated infrastructure cost
- $50.00
- Progressive markup
- $37.50
- Published-store floor
- $5.00
- Platform subtotal
- $87.50
Markup is $25 on the first $25, then $12.50 on the next $25. The $5 floor adds nothing.
$1,000 of allocated infrastructure
- Allocated infrastructure cost
- $1,000.00
- Progressive markup
- $307.50
- Published-store floor
- $5.00
- Platform subtotal
- $1,307.50
Markup is $25 + $37.50 + $120 + $125 across the four brackets, totaling $307.50.
Daily estimates are provisional. Monthly reconciliation, rounding and any later adjustments determine the invoice.
A workable path
From decision to first order.
- 01
Measure
Compact metering records attribute supported shared-service consumption to each store.
- 02
Reconcile
Monthly AWS charges are classified and allocated without exceeding attributable service costs.
- 03
Close and collect
Invoices become eligible to close on the seventh UTC day after month-end, once reconciliation and billing checks pass. Later adjustments carry forward, and Stripe Billing handles collection.
A strong fit for
Know before you build.
- Stores with uneven traffic
- Small catalogs and modest order volume
- Organizations operating several focused stores
- Sellers who value auditable pricing mechanics
Plain answers
Answers before you start.
Is my bill exactly equal to my AWS usage?
No. We add progressive service markup to allocated infrastructure cost, then compare that amount with your combined prorated published-store floors. You pay the higher service subtotal, plus applicable tax and explicit adjustments. Third-party fees are separate.
When is the monthly invoice final?
Monthly closing starts on the seventh UTC day after month-end. Incomplete cost evidence, unresolved reconciliation or billing issues can delay finalization; daily values remain provisional. Later AWS changes appear as explicit adjustments on a following invoice.
Does sales revenue affect the bill?
Merchant Meadows does not use a percentage of sales. Usage can rise with more traffic and orders because the store performs more work, but order value itself is not the pricing base.
Are estimates guaranteed?
Daily values are provisional. AWS can refresh billing exports, so the closed monthly invoice and any later documented adjustment are authoritative.
Launch status
Make a clear, welcoming place for your products.
Public signup and merchant sign-in are not open yet. Explore the platform while we prepare merchant access.
Launch status