The Platform Is the Visible Decision. Your Product Data Is the Real One
Every e-commerce project begins with a platform argument, and almost none of them begin with the catalogue. That order is backwards. A shop can be built on any of the major platforms and work well; the same shop cannot work at all if the product data is inconsistent, because search, filtering, shopping feeds and paid ads all read the same fields — and all four break together.
No credit card required · 30-minute call · No obligation to sign up
Six things the catalogue decides before the build starts
None of these is a platform feature. All six are properties of your product data, and they behave the same way on Shopify, WooCommerce or anything else.
- Filters can only use fields you haveNo size field, no size filter · ever
- Feeds reject what humans forgiveMissing GTIN, wrong category, item disapproved
- Naming inconsistency splits search“T-Shirt”, “Tshirt”, “Tee” · three products
- Images are a data field tooOne angle, no scale, no alt · on 4,000 lines
- Supplier copy is everybody’s copySame description on forty other shops
- Variants model badly if modelled lateAnd remodelling them is a migration
The first row is the one that ends the argument about platforms. A customer filtering by size, material or fit is filtering on fields that either exist in your catalogue or do not. If they do not, no amount of front-end work creates them, and the choice becomes a build project on the data rather than on the site. This is checkable in an afternoon: export your catalogue, count how many products have every attribute a customer would want to filter by, and the answer usually decides the project plan.
Four systems read the same fields and all four break together
On-site search, faceted filtering, the shopping feed and paid product ads are usually treated as four separate projects owned by different people. They are not separate. All four read the product record, and a catalogue with missing attributes fails in all four places at once — which is why the symptoms show up everywhere and the cause never gets found. Somebody fixes the search tool, somebody else fixes the feed, and the data underneath stays exactly as it was.
The fix is unglamorous and it is the highest-value thing in most e-commerce projects: agree the attribute set before the build, decide what is mandatory, and fill it. Not for every product on day one — that is what stalls these projects — but for the lines that earn, with a rule that nothing new gets added without them. A catalogue that is 40% complete and improving beats one that is 100% planned and never started.
Product copy deserves the same honesty. If your descriptions came from the manufacturer, so did everybody else’s, and every shop selling that item has the identical paragraph. Rewriting nine thousand products is not a real plan and we would not propose it. Rewriting the two hundred that earn most of the revenue is, and it is the version that actually gets done.
Then there is the part nobody enjoys discussing: what happens after the sale. Returns, exchanges, stock accuracy and delivery expectations are usually treated as operations rather than website, and they are the things a customer judges you on. A shop that takes an order it cannot fulfil accurately has a data problem wearing a customer-service costume, and it is worth building for that before adding another payment method.
- ✓Filters need fields — A filter can only use an attribute that exists on the product. Front-end work cannot invent one.
- ✓Four systems, one cause — Search, filters, feeds and ads all read the product record. Bad data breaks them simultaneously.
- ✓Complete the lines that earn — Forty per cent and improving beats a hundred per cent planned and never started.
- ✓Rewrite two hundred, not nine thousand — Supplier copy is duplicate copy. Fix the products that pay for the fixing.
- ✓Returns are a build problem — Stock accuracy and delivery expectations decide the review, not the checkout button.
On-site search, filters, the shopping feed and paid ads look like four projects. They read one product record, and they fail together — which is why the cause never gets found.
What an e-commerce build actually involves
Six things. The first two happen before a platform is chosen, which is the part most projects skip.
The Catalogue Audit
Export what you have and count what is missing, per attribute, across the lines that earn. An afternoon of work that usually rewrites the project plan, and always in a cheaper direction.
Attribute & Variant Modelling
What a product is, what varies, and what customers actually filter by — agreed before anything is built, because remodelling variants after launch is a migration rather than an edit.
Platform Selection, Afterwards
Chosen once the catalogue is understood, because that is what determines whether a platform fits. We have no preferred answer to sell, and the honest one is sometimes the cheaper one.
Checkout and Payment
Fewer steps, fewer surprises, and the delivery cost visible before the final screen. Most of what improves a checkout is removal rather than addition.
Feeds and Integrations
Shopping feeds, stock, fulfilment and returns wired to the same product record the site uses — so one correction fixes every surface instead of one of them.
Performance at Catalogue Scale
Category pages with hundreds of items behave differently from a homepage. Image handling and pagination are where a shop is slow, and where the fix is structural rather than a plugin.
What clients say
Real clients, quoted in their own words — published with their permission.
“We’re very thankful to Ghalib and his team for building a fully-functioning website for our business.”
“It was a pleasure working with Ghalib and his team.”
“Highly professional and dedicated to achieving results.”
More of them, in full, on our reviews page.
— Our Proprietary Methodology —
The Visibility Framework™, applied in E-commerce Development
The method doesn’t change by market. What it’s pointed at does.
Audit & Discovery
What the current site earns, where it leaks, what your competitors do better, and what the new one must achieve. Ends in a written scope and a fixed price — not an estimate that grows.
Structure & Design
Sitemap, wireframes and user journeys agreed before decoration, then a design system applied consistently. You approve the shape before we make it beautiful.
Build & Test
Front end, back end, CMS and integrations, on a staging site you can see from day one. Tested on real devices, real screen readers and real slow connections.
Launch & Improve
Redirects verified, analytics connected, handover recorded — then we look at what real visitors actually do and fix what the design assumed wrongly.
Honest, No-Nonsense Commitment
The price we quote after discovery is the price you pay — if we underestimated the work, that is our problem, not a change request. And on any rebuild, if organic traffic drops because of something we did at migration, we fix it at our cost, however long it takes.
Website Development pricing for E-commerce Development, in USD
Quoted per build, and the honest driver is catalogue size and data condition rather than design. A shop with 200 well-described products is a smaller project than one with 4,000 half-described ones, whatever the two look like from the front. The catalogue audit is quoted separately and is the cheapest useful thing here.
Starter
A focused catalogue, built properly.
- Catalogue audit & attribute model
- Platform selection on evidence
- Checkout and delivery expectations built in
Growth
Larger catalogue with feeds and integrations.
- Everything in Starter, at catalogue scale
- Shopping feeds, stock and fulfilment wired in
- Migration & redirect planning
- Optional: bundle in SEO or Social Media
Enterprise
Multi-market or ERP-integrated retail.
- Dedicated senior developer
- ERP, PIM and multi-currency integration
- Custom reporting and ongoing support
- Optional: combine all 4 services for full-funnel growth
Every plan is scoped around your market — get a free audit and we’ll recommend what fits, priced in USD.
What you’re actually committing to
Most agencies keep this in a contract you only see after the sales call. We would rather you knew now, because it is the question everyone asks second — right after the price.
- A fixed price, agreed before we startQuoted after discovery, not estimated on a call. If the work takes longer than we thought, that is our risk — the price does not move unless you change the scope.
- 50% to begin, 50% at launchNo large upfront payment held for months, and nothing owed until the site is live and you have seen it working.
- You own everythingDomain, hosting, code repository, design files and content — all in your name from day one, and still yours if we never work together again.
- No proprietary lock-inStandard, widely-used technology only. Any competent developer can take the site over, and nothing stops working because you stopped paying us.
- Two rounds of revisions per stageIncluded at wireframe and design stage, where changes are cheap. Beyond that, or after sign-off, changes are quoted before any work starts.
- 30 days of support after launchBugs and small tweaks included as standard. A care plan afterwards is optional, never automatic, and cancellable with 30 days’ notice.
These are the terms as they appear in the agreement itself — nothing here is softened for the website. The full wording lives in our terms and conditions, and you get the agreement to read before anything is signed or invoiced.
E-commerce Development Website Development questions, answered
Related Website Development pages
Same service, different angle — by market, by discipline and by platform.
Ready to start with the catalogue instead of the platform?
Free 30-minute audit · No obligation · Response within 24 hours
Get in touch with Ghalib Ashrafi HQ
Ghalib Ashrafi takes on work for brands in six markets — the UK, USA, UAE, Saudi Arabia, Australia and Pakistan. Every enquiry gets a reply within 24 hours.