Goldbelly Clone Features: A Vendor Spine, and Local Fulfilment
This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.
Scope areas for this kind of build
The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.
Feature Set by Role
Five surfaces over one Laravel backend, arranged around the vendor rather than around the restaurant.
The Buyer
- They browse vendors, categories and products with filters and a home feed you curate, open a maker's storefront, build a basket and check out. Thirteen gateways plus wallet credit, cash and offline methods, with split tender reconciled against the order rather than blended into one figure.
The Gift Sender
- Buying for somebody else, with recipient details and the delivery slot carried on the order record itself rather than bolted alongside it in a notes field. That is what makes a gift a first-class order the platform can schedule, track and report on rather than a special case somebody handles manually.
The Vendor Manager
- Applications, document checks, approval and go-live as a recorded workflow with the operator and timestamp attached. Commission set per maker, or a monthly plan instead, so the terms a vendor was signed on are a query rather than an email somebody has to find a year later.
The Merchandiser
- The category structure buyers browse, the home feed, and featured positions sold to vendors competing for attention, scheduled and reported so placement revenue is measurable rather than anecdotal. On a marketplace of makers, what appears first is a commercial decision.
The Finance Desk
- One scheduled disbursement job settling every approved vendor from what was actually charged, with statements, exports and overlap locks. Vendors forgive most things and never forgive being paid wrong, which is why this is the job the whole platform is arranged around.
- Vendors cannot read each other: catalogue, order and payout data resolve against the vendor that owns them, so a maker signed into their own panel sees their own business and nothing else.
How It Works, End to End
Seven stages, running from a maker applying to a maker being paid.
A maker applies and is approved
- Application, document checks, approval and go-live run as a recorded workflow with the operator and timestamp attached, so who approved a vendor and on what terms is a query rather than a memory. It is the first thing an acquirer or a dispute asks about.
Their terms are set individually
- Commission per vendor, or a monthly plan instead of it, rather than one rate across the roster. On a marketplace of independents the ability to sign a sought-after maker on different terms from everybody else is frequently what gets them signed at all.
They build their own storefront
- A surface carrying their own name and catalogue, with sizes, options, extras and allergen notes modelled as variations rather than separate products. You keep visibility over category structure, availability and pricing changes without having to make them.
A buyer browses and orders
- By vendor, category or product, with filters and a home feed you curate, showing only the makers who can actually fulfil to that address. Thirteen gateways plus wallet credit, cash and offline methods, with split tender reconciled against the order.
Gifting and scheduling share one spine
- Ordering for somebody else, choosing a slot for later, or setting a standing weekly order all run on the same order system, with recipient details and the chosen slot carried on the order record rather than as three separate mechanisms nobody can report across.
It is fulfilled locally
- Riders you run, vendors delivering with their own staff, or collection in person. Coverage is drawn as delivery zones with their own charges and rules, and a buyer outside a maker's zone cannot order from them. This is the boundary of the build and it is stated plainly.
Every vendor settles from one run
- A single scheduled disbursement pays every approved maker from what was actually charged, with statements, exports and overlap locks so a retry settles the same cycle to the same figures. Change a vendor's rate next month and their last statement still says what it said.
- Offers, first-order discounts, free delivery thresholds and loyalty points run alongside, with each campaign funded by you or by an individual vendor and the split recorded either way.
Every Feature Earns Its Place
Each row is here because a multi-vendor marketplace stops working without it, not because a competitor lists it.
A built-in till captures counter and phone orders in the same system, so a maker with a physical shop reports through one platform rather than reconciling two.
The Technology Behind the Features
Conventional and easy to hire for, with the vendor and payout spine as the part that was designed rather than assembled.
Boundaries we state in writing for your build
The first two items decide whether this platform is right for you at all, so they are stated before anything else rather than in an appendix.
No cold chain handling
- Proposed go-live checks: test-mode passcodes verifiably off in production, cross-origin rules narrowed to your domains, and transport and frame headers added at the server or middleware layer. Operator two-factor on console sign-in is scoped where your deployment needs it - on a console that can change what a vendor is paid.
Answers from the proposed control map
- What no codebase supplies is the roster. A curated list of makers who cannot easily be signed elsewhere is worth more than any feature here, and assembling it is your work rather than software's.
The roster is the asset. The payout run is the retention.
A curated list of makers who cannot easily be signed elsewhere is worth more than any feature, and a maker paid correctly on schedule does not shop around. Both run on a platform you own outright.
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Goldbelly.
More pages on this build
Overview
The full proposal on one page.
Features
Every proposed capability grouped by who touches it.
You are hereBusiness model
How a platform in this category earns, and which lever to switch on first.
Cost
What actually moves the budget, and how a scope-first written quote is put together.
Company
Agency versus freelancer versus Omnistu, plus the checks to run before hiring anyone.
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Goldbelly.
Discuss your scope by message
Tell us what you want to launch and where. We reply by email with a scoped proposal - no calls required, no phone numbers collected.
