PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
Engagement scope - proposed scope

Goldbelly Clone Development Company: What to Check Before You Hire

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.

Build scopeConfirm servicesDefine the features and exclusions
Delivery planAgree milestonesNo fixed launch duration implied
Source rightsWritten termsCheck licences and handover
OperationsTest before launchAgree acceptance and support
01 / Scope areas

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.

02 / Typical scoping questions

Typical scoping questions

How does an order reach the buyer?

  • Local delivery, collection, or a parcel carrier. Ask before anything else, because a nationwide gifting proposition on a locally-fulfilled platform is a mismatch that no feature list will fix.

What happens if the payout job is retried?

  • It should settle the same cycle to the same figures. Anything else means a slow run pays your entire roster twice, and vendors never forgive being paid wrong.

Can two vendors be on different terms?

  • Ask them to put one maker on a plan and another on commission. A single global rate means the producer you most want cannot be signed on the terms it takes to get them.

Can a vendor read another vendor's numbers?

  • Ask them to try, from inside a vendor account. On a marketplace of competitors this is not a nicety, and it is the kind of thing nobody checks until somebody notices.

What does a vendor's statement look like?

  • Ask to see it as the maker sees it. If they can check their own numbers, your most common support conversation becomes a page they open; if not, it becomes your inbox.

Where do gift details live?

  • On the order record, or in a notes field. In a note, gifting is a manual process wearing a feature's clothes, and it cannot be scheduled, reported on or refunded consistently.

How is a vendor approved?

  • Ask who approved the last one and when. If the answer is not a query, then your onboarding is a set of emails and your due diligence record does not exist.

What does the vendor panel actually do?

  • Ask to use it as a maker. A small producer who cannot mark a batch sold out without phoning you is a support cost that grows linearly with the roster you are trying to build.

What is on your list of what is missing?

  • All nine get answered on the first call, the uncomfortable ones included. The Platform Trust section below puts the same answers in writing.
03 / A proposed launch process

A proposed launch process, without time promises

Define the first service area

  • Where you operate, what you charge inside it, and any limits such as cash-on-delivery ceilings. The first zone usually becomes the template for the ones that follow.

Apply your branding

  • Name, logo, colour scheme and invoice layout applied across the storefront and apps. Which parts are configuration and which are build work is confirmed in the written scope.

Set the commercial rules

  • Commission or subscription structure, discount responsibilities, delivery pricing per zone, tax rules and payout preferences, recorded in the written scope.

Connect your own accounts

  • Payment gateways, store listings, maps and notification services stay under your own accounts, with access arranged before build work starts.
04 / Red Flags That Mean

Red Flags That Mean Walk Away

Five answers that should end the conversation

  • "Everyone's on the same commission, it's simpler." Simpler for the platform and worse for the business. The maker you most want to sign is exactly the one who will want their own terms.
  • "Vendors get a login to the admin." A cut-down view of your console is not a shop a producer can run. Every thing they cannot do themselves becomes a message to you, forever, growing with the roster.
  • An estimate with no named exclusions. A marketplace has real edges: fulfilment model, perishables, vendor accounting. A number presented without any of them was never costed properly.
05 / What a Multi-Vendor Marketplace

What a Multi-Vendor Marketplace Has to Get Right

The machinery that keeps independent makers on a platform they could leave at any time.

06 / What We Have

What We Have Not Done Yet

Six items, stated before a purchase rather than after one, and the first two may decide whether this is the right platform for you.

What does not arrive is the roster

  • Buyers come for the catalogue, so makers signed and kept is the number that decides the business. A curated list of producers who cannot easily be found elsewhere is worth more than anything in this build, and assembling it is relationship work no software shortens.
  • 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

  • When an acquirer or a partner sends a security questionnaire, we would answer from the documented control map agreed in the scope. Clone names the functional target rather than the provenance of the code: this is an original implementation on Laravel, Flutter and Next.js, with no affiliation to Goldbelly.
07 / A Delivered Engagement

A Delivered Engagement, and What It Was Not

A custom-built delivery platform: three applications, six isolated third-party integrations and three environments, with the source transferred to the client at handover.

08 / Hire on the answers

Hire on the answers, not the deck

Approve a vendor, set their terms, take a gift order against their catalogue, run the payout, then run it again. Half an hour, and you have tested the parts a roster actually leaves over.

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Goldbelly.

10 / Next step

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.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead