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

Etsy Clone - Development Cost

Etsy Clone Development Cost: The Seller Side Is the Expensive Part

Hypothesis to test when collecting quotes: whether a maker-marketplace quote is priced on the storefront. The expensive parts are the ones a buyer never sees: self-service onboarding with KYC, commission that resolves at four levels, subscription plans with listing caps, a moderation queue with bulk actions, and a payout process built for many small withdrawals. The platform is quoted as one figure for the scoped build, agreed in writing before work starts. No figure is published on this page - the number follows your scope.

Per-seller commission - specifiedSeller tooling in the base scopeQuote agreed in writing
131Normalized MySQL tables in the supplied specification
4Levels commission resolves at - specified
6Surfaces on one REST API - specified
9Order statuses, per-line state - specified
01 / Compare

What an Etsy-Style Platform Costs Each Way

Three routes to the same capability, and what to verify on each for a maker marketplace.

What you are buyingBuild from scratch - what to verifyOmnistu clone - proposed scopeAssemble from products - what to verify
CostAsk for the fully loaded programme cost in writing, including employer costs.One quoted figure, agreed in writing before work starts.Ask what three subscriptions cost over three years, with reviews.
Time to first orderAsk where seller tooling lands in the roadmap.Durations agreed in writing against your scope.Ask which gaps appear after the integration work.
Self-service onboardingAsk whether it is designed or deferred.Registration with KYC and documents, then an approval queue - as recorded in the supplied specification.Ask whether an admin form caps your catalog at headcount speed.
Commission at four levelsAsk how hard it is to add later - it is a schema property.Global, category, seller and product, resolved per line and reversed on refund - specified.Ask whether one platform rate plus a spreadsheet for exceptions is the answer.
Plans with listing capsAsk whether the revenue model was thought of early.Subscription tiers with product-count limits and reduced commission - specified.Ask whether the billing product knows about listings.
Who owns the codeYou do - verify the handover terms in writing.Proposed full source handover, as agreed in writing.Ask whether you own anything, or rent all three.
Security reviewOne, on your own schedule.One codebase, one review - as proposed scope.Ask what three vendors, three reviews and three answers cost you.
Where it runsYour infrastructure.Your infrastructure, your branding - proposed.Ask whose infrastructure your business runs on.

Swipe sideways for the full table

Hypothesis to test: a marketplace where an administrator creates each vendor by hand risks capping catalog growth at headcount speed, whatever the marketing budget.

02 / Included

What the Quote Covers

The proposed scope is the whole system, seller tooling included, as recorded in the supplied specification. This preview does not implement or verify any of it.

Seller onboarding pipeline

Self-registration with KYC and document upload, an operator approval queue with those documents attached to the decision, and suspension and reinstatement from the console.

Subscription plans

Tiered packages with product-count limits, reduced commission, featured placement and priority support, billed on a cycle with a trial and a grace period on failure.

Buyer storefront

Category browse and a shop directory, search with filters, product pages with galleries, video and photo reviews, a basket spanning several independent shops, and a persistent wishlist.

Seller panel and app

Shop profile and KYC, product CRUD with variants and stock, AI-assisted copy, buyer chat, the order queue, refund responses, review replies, wallet and withdrawals - from a desk or a phone.

Operator console

The seller approval queue, listing moderation with bulk actions, full editing rights over anything on the platform, commission at four levels, the withdrawal queue, marketing and tax configuration, all behind per-module permissions.

Source code

The complete Laravel 12 backend and all three Flutter projects are recorded in the specification; the proposed handover is full source in your repository, as agreed in writing.

Deployment and handover

Proposed installation on your infrastructure with the queue worker, scheduler and storage running, then an admin walkthrough and the configuration checklist as scoped handover activities.

Support window

Launch guidance, priority bug fixes and updates - the terms agreed in writing with your scope.

The first two cards are the ones worth checking against any competing quote - ask any marketplace-script provider whether those two are included.

03 / Drivers

What Moves the Number

The base scope is agreed in writing. These genuinely sit outside it, and the first is the one every maker marketplace has to decide about.

An options and quote builder

Named as scoped work. The proposed base scope handles custom and made-to-order arrangements through buyer-to-seller chat, Whether that tradeoff suits your catalog is a scoping question. If your model requires buyers to configure a product and see a price without talking to anyone, that is a real piece of engineering and it should be quoted at the start.

iOS builds

Three Android apps are in the proposed scope, recorded in the supplied specification as Android builds. iOS builds - developer account, signing setup, store submission and review cycle - are proposed scoped work, subject to validation in your own testing.

Automated moderation assistance

The queue, the bulk actions and full editing rights are in the proposed scope. Automated pre-screening - image classification, prohibited-item detection, duplicate listing detection - is scoped work, and it is worth costing once your listing volume outgrows the people reading it.

Seller-facing analytics beyond the base

Sales analytics are in the proposed seller panel. Cohort views, funnel reporting or a seller-facing traffic breakdown are additions, and on this model they are also a retention lever, because a maker who can see what is working stays.

Payout automation to a provider

The withdrawal queue with approve, deny and mark-processed is in the proposed scope, running against operator-defined methods and each seller's saved details. Pushing those payouts automatically into a banking or payouts provider is an integration - ask whether it belongs in your first scope at your expected seller count.

Governance beyond the base

Age-gated categories, country-specific catalog rules, per-seller document expiry or a four-eyes approval on payouts are all custom modules. Ask about per-seller document expiry if your seller base is KYC-heavy.

Anything beyond the base is scoped and quoted before work starts. You approve a number before work starts rather than watching one accumulate.

04 / Timeline

The Path to Live

What happens, in the order it happens. Durations are agreed in writing against your scope, and the seller-side configuration is not the last thing in it.

01

Model and scope

How many sellers you expect and how small they are, what your approval bar is, what documents KYC needs to collect, and whether custom or made-to-order work is central enough to need an options builder scoped alongside the base deployment.

02

Infrastructure

Provisioning on your provider, the Laravel 12 application deployed, MySQL and Redis running, the queue worker and scheduler configured, storage wired and the domain pointed.

03

Seller pipeline and plans

The registration flow and KYC document requirements configured, the approval queue set up with the right staff permissions on it, and subscription tiers defined with their listing caps, commission rates and placement benefits.

04

Branding and catalog structure

App name, logo, splash screen and colour theme across the mobile builds and both web surfaces, transactional email templates branded, the custom domain configured, and your category tree and attribute library set up.

05

Money and rules

Gateway credentials installed and tested, commission set at the levels you intend to use, withdrawal methods and thresholds defined for a high-frequency small-value payout queue, loyalty and coupon rules in place, and cash on delivery configured if you use it.

06

Walkthrough and handover

A proposed joint walkthrough of the seller journey - onboarded, approved, put on a plan, given their own commission rate and paid out - as scoped handover activities agreed in writing. Source handover as agreed in writing.

The deployment window is not the go-to-market window. Recruiting makers is the business and it runs on its own clock - plan it as the longest pole.

05 / Context

Regional Development Context

We do not publish a dollar figure for a from-scratch build: a total depends on your team, your region and your scope. Here is what to verify before you commit, region by region.

RegionWhat to verify before you commit
North AmericaGet the blended rate in writing, including employer costs - and ask how it compares across regions.
Western EuropeAsk for the fully loaded figure, including employer costs and notice periods.
Gulf and Middle EastIf this is the market you are selling into, ask how local hiring affects market knowledge and timeline.
Eastern EuropeAsk how the seller-side work is specified - specification quality is the thing to verify.
Latin AmericaAsk about working-hours overlap with your team, and verify marketplace experience rather than rate.
South and Southeast AsiaAsk for seller-side marketplace experience specifically - onboarding, commission resolution, payout queues - and how it is evidenced.

Swipe sideways for the full table

Why we give you the questions instead of the total

A from-scratch total depends on your team, your region, and above all on whether the seller side is scoped honestly at the start. In this category that variable dominates: teams budget for a storefront, build an admin form to create vendors, and then discover late that their catalog grows at the speed of their operations headcount. Publishing one number would mean inventing those assumptions and presenting them as a finding. Build the estimate from your own inputs rather than take ours on trust.

06 / Pricing policy

Why the Quote Is Written, Not "Starting At"

What the written quote covers

The proposed scope is specified in detail before work starts, so the quote covers implementing and configuring that scope for you - rebranding, deployment and handover included - agreed in writing rather than open-ended.

The options builder is named before you buy

It is stated as scoped work on this page, not revealed once you are committed. A floor price works precisely by leaving that kind of gap unmentioned.

Configuration is not a change request

Setting up your KYC requirements, approval queue, subscription tiers, listing caps and commission levels is proposed as deployment work, not billable scope creep.

Commercial terms belong in the quote

We do not publish revenue-share, per-seller or per-order promises on this page. Commercial terms are agreed in writing as part of your scoped quote.

The enterprise route

Custom, compliance-heavy and high-scale work is quoted against the final scope rather than listed here.

07 / Budget honestly

Hidden Costs Most Quotes Leave Out

None of these are ours to charge you for. All of them are real, and on this model the first two dominate everything else.

01 - Recruiting the makers

The onboarding pipeline is in the proposed scope; the people walking through it are not. On a maker marketplace seller acquisition is the business, it is a headcount and marketing line, and it is the longest pole in every launch of this kind.

02 - Working the moderation queue

With many small sellers this is a daily shift rather than an occasional check. The queue, the bulk actions and the permissions are in the proposed scope; the people reading listings are a standing headcount line that most business cases omit entirely.

03 - Seller support

A thousand small sellers generate proportionally more support than fifty large ones, because each is running their shop alone and none has an account manager. Budget for it as a function of seller count, not of revenue.

04 - Payout transaction fees

Many small withdrawals means many transaction fees. A payout structure that works at fifty monthly transfers can quietly cost you a meaningful fraction of commission at a thousand weekly ones - set thresholds deliberately.

05 - KYC document storage and review

Collecting identity documents from a large seller base is a storage cost, a review cost and a data-protection obligation. All three are yours, and the third is the one that surprises people.

06 - Notification volume

Order updates, approval decisions, chat messages and payout confirmations across a large seller base add up to real SMS, email and push volume, priced per message by someone else.

07 - OpenAI token spend

On a maker marketplace the AI copy module does more work than usual, because listing copy quality varies across a large seller base. That makes it valuable and makes it a real line item - the per-call cost log exists so it stays visible.

08 - Media storage

Many sellers uploading galleries, plus photo reviews on top, is a genuinely media-heavy application. Storage and egress scale with seller count rather than with revenue.

We list these because a quote that omits them is not cheaper, it is just less finished. Every one is yours to own regardless of who builds the platform.

08 / Business Model

Where the money comes back from

On a maker marketplace commission alone is fragile. The Business Model page walks through the hypothesis that the subscription is the line that funds the business.

09 / FAQ

Frequently Asked Questions

What does the quoted figure cover?

The quote is prepared against your proposed scope and agreed in writing before work starts: the Laravel 12 source, the buyer storefront, the seller panel, the operator console and the three Android applications, installed on your infrastructure under your branding, as recorded in the supplied specification. An options and quote builder, or any other extension, is named on this page as scoped work before you buy rather than after.

Does the price change with how many sellers I have?

Commercial terms are agreed in writing as part of your scoped quote, and we do not publish per-seller or per-order promises on this page. Whether you onboard fifty makers or five thousand, the seller-side tooling - onboarding, four-level commission, plans with caps, moderation at volume - is in the proposed scope either way.

What does the from-scratch alternative cost?

We do not publish a dollar figure, because a total depends on your team, your region and your scope. The regional context table above lists what to verify. In this category the variable that dominates is whether the seller side - onboarding, four-level commission, plans with caps, moderation at volume - is scoped honestly at the start rather than deferred.

Do you take a commission on my sellers' sales?

Commercial terms are agreed in writing as part of your scoped quote, and we do not publish revenue-share promises on this page. Commission is a lever you set - globally, per category, per seller or per product - as recorded in the supplied specification.

Should I budget for an options builder?

Only if buyers need to configure and price a product themselves. The proposed base scope handles custom requests, sizing questions and made-to-order arrangements through buyer-to-seller chat with attachments, Whether that tradeoff suits your catalog is a scoping question. If a structured configurator is core to your model rather than a nice-to-have, scope it at the start - it is quoted before work begins.

What happens after deployment?

Launch guidance, priority bug fixes and updates - the terms agreed in writing with your scope. The proposed handover is full source in your repository; third-party accounts - hosting, payment, messaging, app stores - stay yours, and each side's responsibilities after handover are agreed in writing.

11 / Explore

Explore the Etsy Clone

You are on Development Cost.

Overview

The product page.

Back to overview

Features

Every feature, by role.

See the full breakdown

Business Model

How the platform earns.

See the model

Development Company

How to choose who builds it.

See what to check

12 / Next step

Get a scoped quote, agreed in writing

Bring your expected seller count and your approval bar. Ask what is configuration, what needs your own account, and what the quote covers, before you commit to anything. Email is fine - 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