Farfetch Clone Development Company: What to Check Before You Hire
Anyone can show you a luxury storefront. The questions worth asking are what happens when one basket spans four boutiques, who can release a payout on their own, and which authentication controls are actually built. This page covers how we work, a deployment we have already delivered, and the gaps we name in writing rather than leave for a security review to find.
Talk to Our Team →See PricingAgency vs Freelancer vs Miracuves
Three routes to the same marketplace, and where each one tends to fail on multi-seller settlement specifically.
| What matters | Freelance team | Miracuves ready-made |
|---|---|---|
| Time to live | Four to twelve months, if the scope holds | Six working days |
| Product model | One product per seller, rebuilt later at cost | Master products with competing seller offers |
| Multi-seller orders | The first thing descoped when the budget tightens | Parent and child orders with independent state machines |
| Payout control | A finance person with database access | Maker-checker release, structurally enforced |
| Catalog QA | Usually a spreadsheet and good intentions | A review queue with authenticity and provenance fields |
| Security posture | Rarely documented at all | Named gaps published before you buy |
| Source code | Yours, quality unknown until handover | Full monorepo, 29 services, auditable for due diligence |
| Price behaviour | Hourly, and it moves | $3,399 fixed, quoted before work starts |
A capable agency will build you a fine marketplace. The comparison above is about time, certainty and what you hold at the end, not about whether good agencies exist.
Questions Worth Asking Any Provider
Ask these of us and of anyone else you are considering. The answers are more revealing than a portfolio.
We answer all nine on a call, including the ones where the answer is no. The Platform Trust section below covers the most important of them in writing.
The Six-Step Development Process
What we do, in the order we do it.
Scope, supply and commission model
We confirm your market, your category mix, where the first boutiques come from, and how commission should differ by category and seller tier. A luxury marketplace with no supply is a catalog of nothing, and we would rather say so before you pay.
Branding across four surfaces
Name, logo, colour scheme and splash on the customer storefront, the seller hub, the admin command centre and the Expo mobile build, with the 58-node taxonomy adjusted to the categories you actually carry.
Deploy the services on your infrastructure
The monorepo and its PostgreSQL database go onto infrastructure you control, with payment, messaging and search providers connected using accounts you hold rather than accounts we own on your behalf.
Commission, regions and settlement roles
Commission rules by category and tier, regional pricing, currency and duty configuration, seller tiers defined, and maker-checker roles assigned so payout preparation and approval sit with different people from the first release.
Operator walkthrough and handover
Staff accounts created with the right roles, then we run a multi-seller order end to end and release a payout through maker-checker so the finance workflow is understood before it matters. The monorepo lands in your repository.
The support window
Sixty days of launch guidance, six months of priority bug fixes and twelve months of updates, weighted deliberately after launch because that is when the first multi-seller returns and disputes arrive.
Authentication hardening and any custom module run alongside this on their own schedule and are quoted before they start.
Red Flags That Mean Walk Away
Five answers that should end the conversation
"We will send you a build, not the source." A marketplace you cannot audit is one you cannot take through technical due diligence, and if you raise money someone will ask to read it.
"Sellers are paid manually at month end." This means there is no settlement ledger. It works for ten boutiques and collapses at fifty, and by then the reconciliation problem is historical as well as current.
"Commission is a global setting." A single flat rate across every category and every seller tier will be renegotiated by your largest boutique within the first quarter.
"We host it and manage the payment account." If the vendor holds the payment relationship your sellers are paid through somebody else's account, and your exit is a migration you have not budgeted for.
An estimate with no named exclusions. Every real platform has limits. A quote that names none has either not been thought through or is relying on you not asking.
None of these are hypothetical. They are the patterns operators describe when they arrive having already paid somebody else.
What a Luxury Multi-Brand Marketplace Has to Get Right
The parts that decide whether boutiques stay and whether the platform can be audited.
Every one of these ships in the base build and is demonstrable in the live demo. Ask us to open any of them with data in it.
Named Gaps, Not Hidden
The documented authentication and file-handling gaps, stated here before purchase rather than discovered during a security review.
No MFA or admin step-up
There is no multi-factor authentication and no step-up challenge before a sensitive admin action. For a platform where an operator can approve payouts, both belong on the pre-launch list, and both are scoped work rather than base features.
No refresh tokens or revocation
There are no refresh tokens, no token revocation and no silent renew. Sessions behave accordingly, and a compromised token cannot be invalidated centrally until this work is done. Documented, not discovered.
No signed URLs or virus scanning
Downloads are not served through signed URLs and uploads are not virus scanned. On a marketplace where boutiques upload KYB documents and product imagery, both are pre-launch items worth budgeting for.
Every provider is your account
Stripe, PayPal or Adyen, SendGrid, Twilio, Firebase, Algolia and OpenRouter all run on credentials you hold. This is deliberate rather than a gap: it means more setup on day three and it means leaving is a decision rather than a migration.
Search ships on full-text
PostgreSQL full-text search is what ships and it works from day one. Algolia is an upgrade path with the sync adapter already written, on your own account, and it becomes worth doing when catalog size and query volume justify it.
What is built is real
JWT authentication at the gateway with rate limiting, role-based access across customer, boutique, seller and operator, fraud scoring before payment authorization, AML and sanctions screening in the seller lifecycle, and maker-checker payout release. Auth0 enterprise SSO with JWKS validation is available on your own tenant.
If any of these is a blocker for your compliance position, say so on the first call. Most are scoped modules with a known shape, and knowing now is better than finding out during a penetration test.
Luxury Multi-Brand Marketplace Deployment
How an operator launched a regional luxury multi-brand marketplace on the Miracuves Farfetch Clone. Client identity withheld under NDA.
Regional Luxury Multi-Brand Marketplace
A regional luxury multi-brand marketplace launched on the Miracuves Farfetch Clone, with boutique onboarding, parent and child orders and maker-checker settlement live from day one.
Challenges: onboarding hundreds of boutiques without a manual KYB backlog; splitting one basket across many sellers without breaking fulfilment; and paying sellers accurately, with maker-checker approval on every release.
Goal: launch a luxury multi-brand marketplace without building settlement from zero, give boutiques a real seller portal instead of a spreadsheet and an inbox, and make commission and retail media revenue available at launch.
Solution by Miracuves: the parent and child order model across multiple sellers; commission, retail media and premium seller tiers; regional pricing, currency and locale controls; wishlists, loyalty tiers, concierge and recommendations; all running on twenty-nine independently deployable Node.js services.
What the operator said
"Settlement governance is what won the boutiques over. They can see exactly what they are owed and when it releases." - HR, Head of Retail, luxury marketplace operator, name withheld under NDA.
This deployment ran seven weeks from brief to go-live because it included configuration and migration beyond the base package. The six-day figure elsewhere on this site refers to the standard white-label deployment of the platform as demonstrated.
Frequently Asked Questions
Have you deployed this platform for a real operator?
Why did that deployment take seven weeks and not six days?
What exactly do I own at the end?
Will you fix the authentication gaps for us?
Who works the catalog QA queue?
Can you migrate our existing boutiques and catalog?
Ask us the hard questions first
Bring the nine questions above. We will answer them, including the ones where the answer is no, before anyone talks about a contract.
Explore the Farfetch Clone
A partner who names the gaps before you buy
Six working days to a branded luxury marketplace on your own infrastructure, with the full monorepo in your repository, a deployment already delivered for a live operator, and every documented gap published rather than discovered.
Talk to Us →