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

Fancy Clone - Features

Fancy Clone Features: Designed Around a Front Page You Compose

The design premise: on a curated shop, buyers arrive to be shown something rather than to find something, so what surfaces is specified as an editorial choice the operator makes rather than a ranking an algorithm produces. That single difference shapes the rails, the deals, the CMS and the way placement is sold. Here is what the supplied specification covers, grouped by who touches it; this preview does not implement or verify any of it.

Operator-set rails - specifiedPlacement as sellable inventory - specifiedDesigned for editorial commerce
4Rails, operator-set - specified
131Normalized MySQL tables in the supplied specification
9Order statuses, per-line state - specified
6Surfaces on one REST API - specified
Quick scan

What a Curated Front Page Is Made Of

Six elements, as recorded in the supplied specification.

01 - Featured rail, per-product control ย  02 - Most-demanded and best-selling ย  03 - Best-rated, from real reviews ย  04 - One daily deal, scheduled ย  05 - A time-boxed flash event ย  06 - Paid banners you sold yourself

01 / By role

Feature Set by Role

Six surfaces on one REST API, as recorded in the supplied specification. On a curated shop the operator is a merchandiser rather than an administrator, so that column is the one that describes the actual product.

Buyer

Arrives at a front page composed rather than generated. Featured, most-demanded, best-selling and best-rated rails, one daily deal and time-boxed flash events, editorial posts and CMS pages beside the products, product pages with galleries, video and photo reviews, a wishlist that persists, one basket spanning several sellers with shipping per seller, and coupon, wallet credit and loyalty points applied together.

Seller

Registers with KYC, approved and suspendable by an operator. Product CRUD with variants, stock and multi-image galleries; applies to join a flash event rather than assuming a slot; buys banners and sponsored positions on browse pages; a plan tier that decides which rails they are eligible for; AI-assisted descriptions, SEO titles and image alt text; the order queue, refund responses and review replies; and a wallet with commission visible and a withdrawal request flow.

Delivery Agent

A first-class identity with KYC, approval and zone assignment. An assignment feed with accept and reject, navigation to the seller then the buyer, live location broadcast in transit, status checkpoints from pickup to delivery, a one-time code verified at the door, earnings held separately from cash collected on COD, and a payout request flow from the app.

Merchandiser

Sets every rail by hand, plus per-product featured control. Schedules the daily deal and time-boxed flash events, sets per-product discounts inside an event, publishes blog posts and CMS pages from the same console, sells and places banners and sponsored positions, approves which sellers join an event and charges for it, moderates the catalog with approve, reject and bulk actions, and reads eight report types over any date range, to Excel, CSV or PDF.

The fourth role is listed as merchandiser rather than operator deliberately: on this model the person composing the front page is doing commercial work every day, not configuration once a quarter - that is the design rationale for treating it as its own surface.

02 / Compare

Omnistu Clone vs a Generic Commerce Script

What to verify on each route. On a curated shop the rows that decide it are the merchandising rows, because on this model the front page is the product.

CapabilityOmnistu clone - proposed scopeA generic commerce script - what to verify
What surfaces on the front pageFour rails set by you, plus per-product featured control - an editorial decision rather than an output, as specified.Ask whether you get a newest-first grid, or a plugin's guess.
Scheduled scarcityOne daily deal and time-boxed flash events with per-product discounts, both scheduled from the console - specified.Ask whether scarcity is a sale price field and a reminder.
Editorial contentA Blog module and CMS pages on the same site as the products - specified.Ask whether the blog is a separate site nobody links to.
Placement as a productPaid banners, sponsored positions and an event participation fee - position you control and can therefore sell, as specified.Ask whether there is anything to sell, or the algorithm gives position away.
Who decides rankingYou do. There is no recommendation engine in the proposed base scope, stated plainly.Ask who - or what - actually decides.
Multi-seller catalogSeller KYC and approval, moderation with bulk actions, commission at four levels, payouts on one ledger - specified.Ask whether it is single-seller.
Basket across sellersOne basket spanning several sellers, shipping estimated per seller, a delivery status per line - specified.Ask whether one order means one seller.
Source codeProposed full source handover, as agreed in writing.Ask whether files are encrypted or carry a licence check.

Swipe sideways for the full table

The ranking row is the one people misread. Having no recommendation engine sounds like a gap until you remember what you are buying: on a shop where the front page is the product, an algorithm choosing it is the risk to avoid, not the feature to want.

03 / End to end

How It Works, End to End

A product going from a seller's catalog onto a curated front page and out to a buyer - as recorded in the supplied specification.

01

A seller lists, and waits to be chosen

Registration with KYC and operator approval, then product CRUD with variants, stock and galleries. Listing is where a seller's control ends on this model - what happens next is your decision, and both sides understand that from the outset.

02

Moderation is an editorial filter, not a compliance check

The queue has approve, reject and bulk actions, and the operator keeps full editing rights over any listing - as specified. On a curated shop rejection is designed to be a normal outcome rather than an exception, because the standard is fit with the shop rather than merely being a legitimate product.

03

You compose the front page

Featured, most-demanded, best-selling and best-rated rails, plus per-product featured control. Some of those draw on real signal and some are entirely your choice, and the mix is itself an editorial position. Nothing is specified to appear because a relevance score put it there.

04

Scarcity and timing get scheduled

One daily deal, plus time-boxed flash events carrying per-product discounts. The design rationale: curated commerce runs on scarcity and timing more than on price, and both are scheduled from the console rather than improvised with a sale field.

05

The story ships next to the product

A Blog module and CMS pages are part of the platform, as specified, so the editorial around a drop lives on the same site as the thing it is about. On a shop where buyers arrive to be shown something, the writing is part of the merchandising rather than a marketing afterthought on another domain.

06

Sellers pay for the position you control

Paid banners, sponsored positions on browse pages, and a participation fee for joining an event - as specified. The hypothesis to test: because the front page is finite and curated, position is genuinely scarce, which is why sellers may pay for it in a way they never pay for a search ranking.

07

The order settles like any marketplace order

One basket across several sellers, nine order statuses with a delivery status per line, a returns pipeline with its own status machine, commission taken on completion and reversed on refund, and four wallets each writing an append-only history row inside the same transaction as the balance move - all as recorded in the specification.

Steps three to six are the ones a conventional marketplace does not have. Everything else is the same commerce machinery underneath - deliberate: the curation is designed as a layer on solid plumbing rather than a substitute for it.

04 / Justified

Every Feature Earns Its Place

Each row exists because a specific thing goes wrong on a curated shop without it.

CapabilityWhy it is in the proposed base scope
Rails set by handBecause on a shop where nobody searches, the front page is the shop. A rail generated from a relevance score is a shop assembled by something you cannot question, argue with or sell a position on.
Per-product featured controlBecause curation happens at the item level, not the category level. Without it your editorial choices are limited to whatever buckets someone else defined.
A scheduled daily dealBecause a reason to return today is the retention mechanism an editorial shop is designed around. Scheduled means it happens whether or not anyone remembers to do it.
Time-boxed flash eventsBecause scarcity is designed to work only if it genuinely ends. An event with a start and an end that the platform enforces is a different commercial instrument from a discount someone forgets to remove.
Per-product discounts inside an eventBecause a flat event discount risks giving away margin on the items that would have sold anyway, or failing to move the ones that needed help.
A blog and CMS on the same siteBecause the story is part of what you are selling. Put it on a marketing microsite and it risks earning neither the sale nor the search position, and it stops being merchandising.
Paid banners and sponsored positionsBecause position you control is inventory. Ask which placements remain under the operator's control and can be offered for sale.
An event participation feeBecause being in the drop is proposed to be worth money to a seller. Charging for it is designed to convert your editorial calendar into a revenue line without touching anyone's commission rate.
Plan tiers tied to rail eligibilityBecause on this model a seller's tier is mostly about which rails they can appear in. That makes the upgrade argument concrete rather than a list of dashboard features.
Moderation with bulk actionsBecause rejection is designed to be a normal outcome here rather than an exception, and an editorial filter that can only be applied one row at a time risks becoming a bottleneck on your own standards.

Swipe sideways for the full table

Hypothesis to test against your own shop: these are the ten places where a marketplace built for search-led shopping risks breaking on a shop where nobody searches.

05 / Stack

The Technology Behind the Features

Deliberately ordinary choices, so the team maintaining it after handover can evaluate all of it - as recorded in the supplied specification.

Backend

Laravel 12 on PHP 8.2, organised into nWidart modules - and on this product the Blog module matters, because editorial ships as part of the platform rather than as a bolt-on.

Data

131 normalized MySQL tables with reversible migrations, soft deletes on customer, seller, agent and product rows, composite indexes on the hot paths, and append-only wallet histories - all recorded in the supplied specification.

API

One REST API in versions v1, v2 and v3 serving the storefront, the seller panel, the operator console and all three Flutter clients. Six surfaces, one contract - specified.

Mobile

Three Flutter projects - buyer, seller and delivery agent - are recorded in the supplied specification as Android builds, in the proposed source handover; iOS builds are proposed scoped work, subject to validation in your own testing.

Merchandising

Rails, per-product featured flags, the daily deal, flash events with per-product discounts, banners and sponsored positions - all specified as configuration rather than code, and all changeable without a deployment.

Payments

Eleven gateways recorded in the specification, plus operator-defined offline methods and cash on delivery, with settlement records held per gateway and per currency.

Why there is no recommendation engine, and why that is stated rather than hidden

A recommendation engine listed as a headline feature can stay vague about how good it is. This scope says plainly that there is not one in the proposed base build. For an editorial shop that is a positioning decision rather than a shortfall: the value you are selling is your judgement about what is worth showing, and an algorithm that overrides it works against the proposition. If you later want a recommendation layer, placement bidding or rail analytics, all three are named as scoped work and quoted separately - a more honest arrangement than shipping a weak recommender and calling it included.

The proposed handover is full source in your repository; licence and handover terms are agreed in writing for your scoped project.

06 / Honest readiness

What Is Not Included in the Base Package

Scoped separately, or yours to own. Recorded in the supplied specification; this preview does not implement or verify any of it.

A recommendation layer

There is no recommendation engine in the proposed base scope, stated plainly rather than buried. On an editorial shop that is a deliberate position - your judgement is the product - but if you want algorithmic recommendation alongside the curated rails, it is scoped and quoted separately.

Placement bidding

Banners, sponsored positions and event participation fees are specified as things you price and sell. An auction where sellers bid against each other for a slot is a different mechanism, and it is scoped work.

Rail analytics

Eight standard report types are in the specification. Measuring which rail converted, what a featured slot was worth and how an event performed against a baseline is scoped separately - ask whether it belongs in your first scope, because on this model it can change how you merchandise.

iOS applications

The supplied specification records three Android builds in the proposed scope. iOS builds are proposed scoped work with signing and store submission, subject to validation in your own testing.

Gateway credentials

Eleven gateways are recorded in the specification; each needs your own merchant account and its own approval.

SMS and email provider

Integration-required - your accounts, your sender reputation, your deliverability.

Firebase project

Push notifications across the Android apps run through your own Firebase project. On a shop built around daily deals and drops, push is doing real commercial work.

OpenAI key

The AI module is specified to generate descriptions, SEO copy and alt text against your key, with per-feature token quotas and a per-call cost log. Whether AI-assisted copy improves listing quality and search visibility on your catalog is a hypothesis to test, not a promise.

Catalog data and editorial

Products, imagery, seller recruitment and the writing itself are the business. The Blog module is in the specification; the point of view does not ship.

ISO 27001 and SOC 2

This preview supplies no ISO 27001 or SOC 2 evidence; no certification is claimed here. Certification is a separate programme.

Rail analytics is the one to weigh early: curating without measuring is possible, but knowing what a featured slot is actually worth is what turns placement from a price you guessed into a price you can defend.

07 / Development Company

See how Omnistu compares to agencies and freelancers

The proposed deployment process, modelled reference deployments, and how to test the rails, the daily deal and a flash event before you hire anyone - on the Development Company page.

08 / FAQ

Frequently Asked Questions

Is there a recommendation engine?

No, and we say so plainly rather than implying otherwise. Rails are set by you - featured, most-demanded, best-selling and best-rated, plus per-product featured control - as recorded in the supplied specification. For an editorial shop that is the proposition rather than a gap: what you are selling is your judgement about what is worth showing. A recommendation layer is scoped and quoted separately if you decide you want one alongside the curation.

How much of the front page can I actually control?

All of it, as specified: four rails, each set by you, plus per-product featured control so curation happens at item level rather than being limited to buckets someone else defined. On top of that sit one daily deal and time-boxed flash events with per-product discounts, all scheduled from the console. Nothing is specified to appear because a relevance score put it there.

How do flash events work?

They are time-boxed, with a start and an end the platform is specified to enforce, and they carry per-product discounts rather than one flat rate across the event. Sellers apply to join rather than assuming a slot, and you can charge a participation fee for it. The design rationale: an event that genuinely ends is a different instrument from a discount someone forgets to remove.

Is the blog part of the platform or separate?

Part of it, as recorded in the specification: a Blog module and CMS pages, so the story around a product lives on the same site as the product rather than on a marketing microsite nobody links to. On a shop where buyers arrive to be shown something, the writing is part of the merchandising.

Can I sell placement to sellers?

Yes - paid banners, sponsored positions on browse pages and an event participation fee are all recorded in the specification. The hypothesis to test on your own shop: because the front page is finite and curated by you, position is genuinely scarce, which is why sellers may pay for it here in a way they never pay for a search ranking. Placement bidding, where sellers auction against each other for a slot, is scoped separately.

Is the commerce underneath a full marketplace?

The specification says so: seller KYC and approval, moderation with bulk actions, commission at four levels, a basket spanning several sellers, nine order statuses with a delivery status per line, a returns pipeline with its own status machine, four wallets with append-only histories, a delivery fleet with verified handover, and eight report types over any date range - all recorded in the supplied specification. This preview does not implement or verify any of it.

10 / Explore

Explore the Fancy Clone

You are on Features.

Overview

The product page.

Back to overview

Development Cost

How pricing is scoped.

See the cost shape

Business Model

How the platform is proposed to earn.

See the model

Development Company

How to choose who builds it.

See what to check

11 / Next step

Ask us to compose a front page in writing

Set a rail, feature a product, schedule tomorrow's deal and open a flash event - ask us to walk through each in writing, and judge whether the merchandising model fits your shop. 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