Pricing
One flat price. Every feature. No cut of your sales.
14 days free with no card, so you can run a real drop before you decide anything. The price is on the screen before you ever pay.
What the one price includes
There are no tiers, because a tiered menu is a tax on reading comprehension. Everything the platform does, every shop gets.
- Your shop at yourshop.grazepost.com
- Drops, one-offs and preorders
- Caps that hold under a rush
- Regulars' head start, earned automatically
- Standing orders, filled before the public
- Waitlists when a pool sells out
- Pickup slots and pickup day board
- The pack sheet and printable labels
- Store credit as a ledger
- Customer import from a CSV
- One-click export of everything
- Drop alert texts, on recorded consent
- Light and dark shop themes
- No trackers on your buyers, ever
The economics, plainly
One subscription
GrazePost takes no cut of your sales. A bigger market day costs you nothing more.
Zero waste by design
Caps and preorders mean you bring what is claimed. The pack sheet is a loading list, not a guess.
No apology overhead
The cap is enforced inside the order's own transaction, so overselling is not a risk you manage; it is a thing that cannot happen.
Against the ways makers sell today
Most sellers arrive here from a marketplace app, or from DMs and a spreadsheet. The columns below describe how those models work, not somebody else's fine print; check any app's current pricing yourself, because it is theirs to change.
| GrazePost | Marketplace apps | DMs + spreadsheet | |
|---|---|---|---|
| Where your shop lives | Your own address, with your name in it | Inside their app, under their brand | Your DMs, wherever they scroll to |
| What it costs you | One flat subscription. No cut of sales | Typically per-order fees, or fees your buyers pay at checkout | Free, priced in Saturday chaos |
| When two people want the last jar | The cap decides, inside the transaction | Depends on the app | You decide, and apologise to somebody |
| Your customer list | Yours. Exports in one click, stay or go | Usually lives in their platform | Buried in a message history |
| Loyalty | Regulars earn a head start automatically | Rarely modelled at all | Whoever texts fastest |
Your data
What we do with it, written from the codebase.
A shop holds other people’s names and phone numbers, which makes security a food safety issue with different ingredients.
Every shop is walled off
Every record a shop owns carries that shop's id, and all database access goes through a client scoped to one shop at a time. Hand-written cross-shop queries are banned by an automated test, and every feature is exercised against two shops before it ships.
Passwords we cannot read
Passwords are stored as salted PBKDF2 hashes. We keep the result of the math, never the password, so neither we nor an attacker who read our database could recover one.
Sign-in codes that spend themselves
Texted codes are single use, bound to one shop and one purpose, stored only as keyed hashes, and rate limited per phone and per address. A code minted for signing in cannot be replayed to do anything else.
Sessions that JavaScript cannot touch
Session cookies are httpOnly, secure in production, and same-site. The storefront's own scripts cannot read them, and neither can anyone else's, because buyer-facing pages carry no third-party scripts at all.
Consent as evidence
A marketing text can only go to a phone number with a consent timestamp on record, and the timestamp is stamped by our servers, not typed by anyone. No record, no message.
Encrypted transport, everywhere
Every page is HTTPS, with strict transport security that covers every shop's subdomain, plus nosniff, frame denial, and referrer and permissions policies on every response.
Cards never touch us
When card payments are enabled they are handled by Stripe. Card numbers go to Stripe's servers and never to ours.
Your data leaves when you do
Customers, orders and the credit ledger export as spreadsheets on one click, with every cell defused against formula injection. Deletion requests are honoured.
No security page is a proof, and anyone who tells you otherwise is selling something. If you find a hole, tell us and we will fix it before we explain it. What we store and why lives on the privacy page.
Before you ask
Questions, answered
- Do my customers need an app?
- No. Your shop is a web address. They open it, claim, and pick up at your stall.
- What happens after the trial?
- One flat subscription, and nothing changes about the shop you already built. Cancel any time and your data still exports.
- How do drop alerts work?
- Buyers who opt in get a text the moment ordering opens. No consent on record, no text, and nothing sends outside waking hours.
- I already have a stall. Why preorder?
- Because the market becomes a pickup line instead of a gamble. What you bring is already claimed, and walk-ups still buy whatever you brought extra.
- Who owns my customer list?
- You do. Customers, orders and the credit ledger export to CSV in one click, whether you stay or go.
- What happens when I sell out?
- The cap holds and the board says so. Buyers can join the waitlist, first come, and you pack exactly what the pack sheet says.
Run a real drop before you pay anything.
14 days free. No card to start. Leave with your list.