PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
Fancy Clone - Development Company

Fancy Clone Development Company: How to Choose One

Ask each provider to show you a finished shop. On a curated marketplace the question to put to each of them is narrower and more revealing: can you compose the front page in front of me, right now, without a developer? On this page's proposed model, everything else - what you can sell, what a seller will pay for, whether the shop has a point of view - is designed to follow from that one answer.

No named client yet - disclosedFull source - proposed scopeReference deployments modelled - labelled
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
131Tables in the supplied specification
4Operator-set rails - specified
9Order statuses - specified
3Android builds - specified
01 / Compare

Agency vs Freelancer vs Omnistu

Three routes to a curated marketplace, and the trade-off each one asks you to accept. The agency and freelancer columns are the questions to put to whoever quotes you; the Omnistu column is the proposed scope as recorded in the supplied specification.

What you care aboutCustom agency - what to verifyFreelance team - what to verifyOmnistu - proposed scope
Time to a working platformAsk when merchandising lands in the plan - whether it is part of the base build or an afterthought.Ask for the plan in writing and check whether estimates are backed by past work of the same kind.Deployment is scoped as a discrete engagement; the editorial work that makes the shop worth visiting runs on your own clock, and we say so before you buy rather than after.
Cost shapeAsk how the budget moves as scope is discovered.Ask what the quote excludes.No total is published. Scope is quoted in writing before anything starts, with add-ons named up front.
Front page controlAsk who can change the homepage on launch day, and on day ninety.Ask whether the front page is hardcoded and what a change costs.Four operator-set rails plus per-product featured control, changeable without a deployment - specified.
Scheduled deals and eventsAsk whether a daily deal is in the base build or arrives when the first campaign deadline does.Ask whether a "deal" is a sale price field or a scheduled mechanism.A daily deal and time-boxed events with per-product discounts, in the proposed base build - specified.
Editorial in the platformAsk whether the blog is a separate CMS on a separate domain.Same question.Blog module and CMS pages on the same site as the products - specified.
Who owns the codeCheck the contract, not the pitch.Check what is documented, not what is said.The proposed handover transfers the complete Laravel 12 source into your repository, with no encrypted files - verify it in the repository before handover completes.
What happens if they leaveAsk what the handover project looks like.Ask who picks the platform up if one person stops answering.The specification records an ordinary stack - Laravel 12, PHP 8.2, MySQL, Redis 7 and Flutter - chosen so the team maintaining it after handover can evaluate all of it.
Domain knowledge includedAsk what the team knows about curated commerce specifically.Same question.The merchandising model is recorded in the schema itself - 131 tables, as specified.
Proof it worksAsk to operate the front page yourself, not to watch it operated.Same question.Ask us to walk through composing the front page in writing - a rail reordered, a product featured, a deal scheduled, an event opened and closed.

Swipe sideways for the full table

The third row is where this page thinks curated-commerce projects go wrong. A homepage that requires a developer to change is a homepage that stops changing, and a shop whose front page stops changing has quietly stopped being curated. That is a design opinion - test it against your own operation.

02 / Due diligence

Questions Worth Asking Any Provider

Ask these of us, and of everyone else you are talking to. Ask them as things for a provider to demonstrate on a working build; for this preview, ask us to walk through each in writing.

01 - Reorder a rail in front of me

Not describe it - do it, from the console, without a developer and without a deployment. If changing the front page is a ticket, ask yourself whether the shop would look the same in six months as it does today - because curation is the thing you were buying.

02 - Feature one specific product

Not a category, one item. Curation happens at item level. If the only lever is a category or a tag, ask which editorial decisions remain yours and which are limited to buckets somebody else defined.

03 - Schedule tomorrow's deal, then check it fires

A daily deal that depends on someone remembering is not a mechanism. Ask what runs it, and whether the scheduler is configured and monitored at deployment rather than assumed.

04 - Open a flash event, then let it end

Scarcity is designed to work only if it genuinely closes. Watch the event actually expire and the prices revert. A discount that has to be removed by hand is a different instrument from one the platform enforces - ask which one you are being shown.

05 - Can you set discounts per product inside an event?

Ask what a flat event discount does to margin on items that would have sold anyway, and whether it moves the ones that needed help. Per-product control inside an event is what the proposed scope on this page records - specified.

06 - Where does the blog live?

Same site, or a separate CMS on a separate domain? Ask what a second stack costs you in deployments, security reviews and search position.

07 - What exactly can I sell to a seller?

Ask for the list: banners, sponsored positions, event participation. If ranking is decided by an algorithm, ask which placements remain under the operator's control and can be offered for sale.

08 - Is any of the source encrypted?

Ask directly, and ask whether there is a licence callback - and what each answer would mean for your ownership and your negotiating position later. On this page's proposed scope the answer is no to both; verify it in the repository before handover completes.

09 - What have you not done yet?

A provider who cannot name a gap either has not looked or will not say - both are a reason to ask more questions. Ours is on this page, in the section below, without being asked - including an absence a provider has no incentive to volunteer.

If a provider can do the first five in a live console, judge the merchandising for yourself. If any of them turns into "we can build that", you may be looking at a general marketplace with a curated-commerce sales pitch attached - ask which one it is.

03 / Process

The Six-Step Development Process

What the proposed engagement covers between signing and taking your first order, and who is responsible for each part. Sequencing and timing are agreed in writing against your scope.

01 - Editorial model discovery

What your front page should say, which rails you actually want and why, how often you intend to run events, whether you plan to sell placement from launch, and whether a recommendation layer or rail analytics needs scoping alongside the base deployment.

02 - Infrastructure and deployment

Provisioning on your provider under your account, the Laravel 12 application deployed, MySQL and Redis running, and the queue worker and scheduler configured and verified - on this product the scheduler runs your daily deal and closes your events, so it is proposed as checked rather than assumed.

03 - Catalog structure and a real first front page

Your category tree, brand directory and attribute library set up, then the rails configured and a first front page composed with real products in it. The intent is that you look at a shop early in the engagement, not at a wireframe of one.

04 - Branding, blog and CMS

App name, logo, splash screen and colour theme applied to the three Android builds and both web surfaces recorded in the proposed scope, transactional email templates branded, custom domain configured, and the Blog module and CMS pages set up with your structure.

05 - Money, placement and permissions

Gateway credentials installed and tested, commission bands set, banner and sponsored-position slots defined with their prices, the event participation fee agreed, plan tiers mapped to rail eligibility, and staff accounts created with per-module permissions.

06 - Walkthrough, handover and support

We set a rail, feature a product, schedule tomorrow's deal and open and close a flash event - traced with you in writing, rather than described. Then the repository transfers, and support terms are agreed in writing as part of your scoped quote.

Deployment is our side of the work. Recruiting sellers worth curating and writing the editorial that makes the shop worth visiting run on their own clocks - on this model they are the business, and we will say so before you buy rather than after.

04 / Warning signs

Red Flags Worth Walking Away From

Six answers that should make you ask harder questions, whoever you are talking to - including us.

"Our algorithm decides what shows"

Then ask which placements remain under the operator's control and can be offered for sale. On a curated marketplace the front page is the product and the position is the inventory - ask who holds both.

"We can change the homepage for you"

Meaning it is a ticket. Ask what happens to a front page that needs a developer to change, and whether a shop whose front page stops changing is still curated.

"Add a sale price and remove it after"

That is not a flash event. Scarcity is designed to work only if it genuinely ends, on a schedule the platform enforces - ask what happens to a discount that has to be removed by hand.

"Put the blog on a separate site"

Ask what the editorial earns on a second stack: the sale, the search position, or neither - and what a second deployment and a second security review cost you.

"Some files are encrypted for licensing"

Ask what you actually own in that arrangement, and ask early - before the answer shapes your negotiating position.

"Everything is ready, nothing is missing"

No platform is finished. A provider who will not name a single gap is either not looking or not telling - both are a reason to ask more questions.

The last one is the reason the section below exists on our own page - and why its first item is an absence this page states rather than hides.

05 / Domain

What a Curated Marketplace Has to Get Right

Five things that are invisible in a demo screenshot and worth verifying before production. Ask any provider you are considering to show you all five with data in them - and ask us to walk through each in writing.

A front page you compose

Featured, most-demanded, best-selling and best-rated rails set by you, plus per-product featured control, all changeable from the console without a deployment - specified. On a shop built around being shown something rather than searching, this is not the homepage - it is the shop.

Scarcity the platform enforces

One daily deal and time-boxed flash events with per-product discounts, scheduled rather than remembered, starting and ending on their own - specified. The hypothesis on this page: curated commerce runs on scarcity and timing more than on price.

Editorial that ships with the commerce

A Blog module and CMS pages inside the platform - specified - so the story around a product is published on the same site as the product itself.

Position as sellable inventory

Paid banners, sponsored positions on browse pages and a participation fee for joining an event - specified. You can only sell position you control, which is the commercial consequence of curating rather than ranking.

Ordinary marketplace plumbing underneath

Seller KYC and approval, moderation with bulk actions, commission at four levels, a basket across sellers, nine order statuses with per-line delivery state, a returns pipeline and four reconciled wallets - specified. Curation is a layer on solid commerce, not a substitute for it.

06 / Platform trust

What We Have Not Done Yet

Stated plainly, because you will find it out anyway and it is better you hear it from us first.

No named client on this platform

No client testimonial is established by this page. Ask for relevant, authorized evidence and a way to verify it. The configurations below are illustrative planning scenarios, not proof of an implemented platform or client engagement.

The reference deployments are modelled

The two deployments described below are illustrative configurations built only from capabilities recorded in the supplied specification. They are not client engagements, they carry no reported revenue or growth figures, and the numbers in them are properties of the platform rather than results a customer reported.

There is no recommendation engine

Not in the proposed base build, and this page states it rather than staying vague. A recommendation engine listed as a headline feature can stay vague about how good it is; the proposed scope here says plainly that there is not one. For an editorial shop we think that is a position rather than a shortfall - your judgement is what you are selling - but you should decide that for yourself.

Placement is priced, not auctioned

Banners, sponsored positions and event participation fees are recorded as inventory you price and sell directly - specified. An auction where sellers bid against each other for a finite slot is a different mechanism and is scoped separately; whether it would raise what placement earns is a hypothesis to test, not a promise.

Rail analytics is scoped work

The eight standard report types in the supplied specification tell you what sold. Which rail converted, what a featured slot was worth and how an event performed against a baseline is a separate quote. The proposed scope records three Android builds; iOS builds are proposed scoped work, subject to validation in your own testing.

No certification evidence in this preview

This preview supplies no ISO 27001 or SOC 2 evidence; no certification is claimed here. The supplied specification records permissions per module, append-only histories and field-level edit records - the raw material an evidence-gathering programme would need. Certification is a separate programme with its own auditor and its own cost.

Ask any provider for their version of this list. Ours is above - hold us to it.

07 / Modelled

Modelled Reference Deployments

Two illustrative configurations showing how the same platform is set up for two very different commerce markets. Neither is a client engagement. Both are built only from capabilities recorded in the supplied specification.

India: COD-Led Multi-Vendor Marketplace

Illustrative scenario - not a client engagement.

131Tables in the supplied specification
4Wallets reconciled per order - specified
4Operator-set rails - specified

What this scenario assumes: cash closing the order at the door days after it was placed with stock and commission already committed; tax rates differing by category and by region, needing a line on every invoice; buyers shopping in more than one language; and delivery that reaches some areas reliably and others not at all.

What the specification records: cash on delivery with a server-verified code at handover, a cash balance carried per agent and settled to the operator wallet, an operator-set handling fee, zip allowlists deciding where checkout is offered, tax classes bound per zone with per-product rules, and languages configured across web and all three Android apps - all specified.

The figures above are properties of the platform, not results reported by a customer. Named client deployments, when they exist, will be published with their own reported figures.

Thailand: Provincial and Cross-Border Marketplace

Illustrative scenario - not a client engagement.

11Gateways available to switch between - specified
9Order statuses, payment to delivered - specified
3Android builds in the proposed scope

What this scenario assumes: delivery economics differing between a dense capital route and a provincial or island one; buyers who expect to pay on arrival; selling into neighbouring markets that quote in a different currency; and a second market meaning a second deployment to keep in step.

What the specification records: zones with per-category shipping cost overrides, a currency catalog whose default drives checkout display, cash on delivery with per-agent reconciliation, a delivery fleet with pickup and delivery checkpoints, multi-language storefront across every surface, nine order statuses with a full history per order, and one REST API serving the storefront, the seller panel and all three apps - all specified.

The figures above are properties of the platform, not results reported by a customer. Named client deployments, when they exist, will be published with their own reported figures.

We label these as modelled rather than dressing them as case studies because we have not yet deployed this platform for a named client - and a reference deployment presented as client proof is the fastest way to lose the trust this page is trying to earn.

08 / FAQ

Frequently Asked Questions

Have you deployed this platform for a real client?

No client testimonial is established by this page. Ask for relevant, authorized evidence and a way to verify it. The configurations below are illustrative planning scenarios, not proof of an implemented platform or client engagement.

Why would I buy a platform with no client reference?

Our position: something you can verify yourself is worth more than a reference. Put the nine questions above to every provider you are considering - including us - and ask for the complete source before handover completes. Ask us to walk through each answer in writing.

Why is there no recommendation engine?

Our position: on an editorial shop your judgement about what is worth showing is the product, and an algorithm that overrides it works against the proposition. We say so plainly rather than shipping a weak recommender and calling it included. If you want a recommendation layer alongside the curated rails, it is scoped and quoted separately.

Do I own the code, genuinely?

The proposed scope transfers the complete Laravel 12 backend and all three Flutter projects into your repository, unobfuscated, with no encrypted files and no licence callback - as recorded in the supplied specification. Verify it in the repository before handover completes: with no callback mechanism, there is nothing in the proposed scope by which your platform could be disabled remotely.

What if I want placement bidding or rail analytics?

Both are named as scoped work rather than implied, alongside a recommendation layer, and are quoted separately - commercial terms agreed in writing as part of your scoped quote. Rail analytics is the one this page raises first: knowing what a featured slot was actually worth turns the price of placement from a number you guessed into one you can defend to a seller.

Can our own developers maintain this after handover?

That is the intent behind the stack choices recorded in the specification: Laravel 12 on PHP 8.2, MySQL, Redis 7 and Flutter - deliberately ordinary choices, so the team maintaining it after handover can evaluate all of it. The backend is organised into nWidart modules so AI, Blog and Tax are separable, migrations are reversible, and the hot paths carry composite indexes - all as recorded in the supplied specification.

09 / Next step

Ask Us the Hard Questions First

Bring the nine questions above. Ask us to walk through each in writing, and judge the answers for yourself. Email is fine - no calls required, no phone numbers collected.

Explore

Explore the Fancy Clone

Overview

The product page.

Features

Every feature, by role.

Development Cost

How pricing is scoped.

Business Model

How it earns.

You are here: Development Company - how to choose who builds it.

Disclosure

A Partner Who Tells You What Has Not Happened Yet

No named client on this platform, two modelled reference deployments labelled as modelled, and no recommendation engine in the proposed base build - stated on this page rather than omitted from it.

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Fancy. "Fancy Clone" is used descriptively - it is how the software industry refers to building a platform with functionality similar to Fancy, and how clients search for it. Fancy and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.