The direct-selling producer juggles three lists
Who ordered what this week? What must I prepare? Where to deliver? Direct sales — vegetables, cheese, meat boxes, eggs — rests on those three lists, rebuilt every week across messages, calls and a spreadsheet. The classic end-of-chain error: the basket forgotten at the pickup point, the box promised twice.
Generic e-commerce platforms answer beside the point: anonymous shopping carts, mandatory online payment, a frozen catalogue — when the real trade is regulars, products that change weekly, and payment often settled at handover.
Your baskets, subscribers and pickups — structured
Describe how you work: “I grow vegetables. Clients order weekly from available products; some have a subscription basket. I deliver three pickup points on Fridays. I want the preparation list by product, the list by pickup point and pending payments.”
The generated application structures that mechanism: the week's products, orders attached to clients, pickup points — and the two lists that make Friday work: preparation by product, distribution by point.
- Available products per week
- Clients and basket subscriptions
- Weekly orders with statuses
- Pickup points and rounds
- Dashboard: preparation, distribution, payments
The typical week, without friction
Monday: you update available products. During the week: each order takes seconds to enter. Thursday evening: the preparation list by product comes out by itself — so many radish bunches, so many boxes. Friday: the per-pickup list doubles as the round sheet, and payments are ticked at handover.
The application arrives with realistic demo data (seasonal products, clients, varied orders) to project yourself immediately.
A tool that belongs to the farm
A direct seller's client base is the fruit of years of markets and word of mouth: it must stay at the farm. Code ZIP export, GitHub push, free hosting or the included dedicated URL.
Free Discovery plan for the first application; Pro (€25/month) and Max (€149/month) to iterate, with the cost shown before each generation.
Typical generated entities
- Product
- Client
- Order
- Pickup point
- Subscription
Generated screens
- This week's available products
- This week's orders per client
- Preparation list by product
- Distribution list by pickup point
- Weekly dashboard
Dashboard indicators
- Orders this week
- Volume to prepare per product
- Pending payments
- Revenue per pickup point
Frequently asked questions — direct sales
Can my clients order online themselves?
The generated application is your internal management tool: you enter orders received (phone, messages, market). Since the code is exportable and standard, a client order form can be added by a developer if volume justifies it.
Can we manage subscription formulas (small/large basket, every other week)?
Yes: describe your real formulas and they structure the application — the subscription generates the week's order, which you adjust if needed.
Is shifting product availability handled?
It's the core of the model: products have per-week availability, and preparation lists compute from actual orders.
Can I tick payments at basket handover?
Yes: the payment statuses you describe (due, paid, offered) tick from a phone at the pickup point.
What does it cost for a small farm?
The first application generates for free (Discovery plan). Paid plans (Pro €25/month, Max €149/month) only matter if you iterate more — with the cost shown before each generation.