← All posts

An online store for your business: what an e-commerce website needs

Selling online is more than a product page and a cart. Here is what an e-commerce website needs to work day to day: catalogue, checkout, payments, delivery, stock, admin and the content to prepare before the build.

Author
Elie Chaaban
Published
Reading time
8 min
Topics
Websites, E-commerce, Planning

Most people picture an online store as a grid of products and a cart. That is the easy part. What decides whether the store actually works is everything around it: how orders reach the person who packs them, how payment is confirmed, what happens when something is out of stock, and how a customer finds out where their order is.

This post goes through what an e-commerce website needs, from the catalogue to the admin, how to choose between a store platform and a custom build, and what to prepare before you ask a developer to quote. It is written for businesses that already sell, in a shop or over social media and WhatsApp, and want a proper store.

Start from how you sell today

Before features, write down how an order happens now. Who takes it, how the customer pays, who packs it, who delivers it, and how stock gets updated. A store that copies a generic checkout but ignores how your team works ends up running beside the real process instead of replacing it.

Questions that shape the build:

That last one matters more than it looks. If wholesale customers order on account with their own prices, that is closer to a B2B ordering portal than a public store, and it is worth knowing which one you need before anything is designed.

The catalogue

The catalogue is the part customers see most, and the part your team edits most. It needs:

If the store is in Arabic and English, plan it from the start: product names and descriptions in both languages, right-to-left layouts that are designed rather than flipped, and URLs for each language so both can rank. I covered this in building bilingual Arabic and English apps and websites.

Cart and checkout

Checkout is where most stores lose people. The rules are simple and often ignored:

Address entry deserves thought in markets where addresses are informal. In Lebanon, for example, many people describe a location by building, street and a landmark rather than a postcode. An open text address with a few structured fields (area, building, floor) and an optional map pin usually works better than a rigid form copied from a foreign template.

Payments

Start from how your customers already pay, not from what a template offers. Depending on the market, that can be cash on delivery, bank transfer, a wallet or transfer service, card payments online, or a mix. In Lebanon, many customers are used to paying cash on delivery or through Whish and OMT, alongside cards.

Whatever the methods, the store needs a payment status on every order (unpaid, paid, refunded), the method used, and a way for staff to confirm payments that do not arrive automatically. For card payments, use the gateway's hosted page or secure components so card numbers never touch your server. Which gateways your business can use depends on where the company and bank account are registered, so confirm that with the providers early, before the design assumes one. The practical options are in accepting payments in your app or website in Lebanon.

Delivery and fulfilment

Delivery is where a store meets the real world, and it needs more design than people expect:

If you use a delivery company, check whether it offers an integration or whether orders are passed to it manually at first. Starting manually is fine if the order status stays accurate.

Stock

Selling something you do not have is the fastest way to lose a customer's trust. The store needs stock per product and variant, reduced when an order is placed and restored if it is cancelled. Decide what happens at zero: hide the product, show "out of stock", or allow back-orders.

If you also sell in a physical shop, the hard question is where the truth lives. Either the store and the shop share one stock record, or someone reconciles them daily. Running two stock lists that drift apart causes most overselling. When stock is complicated, with several locations or regular counts, it may need its own tool; the moving parts are in an inventory and stock-taking app.

The admin your team will live in

Your team spends its day in the admin, where a store either saves time or creates work. It should cover:

The general principles are in what your app's admin panel actually needs. For a sense of the kind of admin desk I build, the Pro Clean+ case study shows the booking admin behind that app, with sample data.

Platform or custom build?

There are three honest routes, and each fits different stores.

A hosted store platform. Shopify and similar services give you a working store quickly, with hosting, checkout and updates handled for you. They fit a standard retail catalogue well. The limits appear when your payment methods, delivery rules or language needs do not match what the platform and its add-ons support in your market, and when monthly add-on costs pile up.

WordPress with an e-commerce plugin. A good fit when the business also needs a content-heavy website and wants to edit everything in one place. It needs disciplined maintenance: plugin updates tested before they go live, caching, backups and an eye on speed as the catalogue grows. The general trade-off is in WordPress or a custom Next.js site.

A custom build, for example a Next.js storefront on a Postgres database with its own admin. This earns its cost when the selling model is not standard: unusual pricing, a delivery flow tied to your own drivers, integration with an existing system, or a store that has to share data with a mobile app. You own the whole thing and it does exactly what you need, but the first version takes longer and you need someone to maintain it.

A small catalogue with standard delivery rarely needs custom code; a business whose checkout depends on its own rules usually does.

Launch, SEO and after

A store needs the same foundations as any business website, plus a few of its own:

If you are moving from an existing store or website, keep the old product URLs or redirect them, or you lose the search traffic you already have. The method is in redesigning your website without losing your Google rankings.

What to prepare before contacting a developer

You will get a clearer quote and a faster build if you have:

  1. A product list in a spreadsheet: names, variants, prices and stock, in every language the store will use
  2. Product photos, or a plan for taking them
  3. The payment methods you want at launch, and which can wait
  4. Delivery zones, fees and how deliveries happen today
  5. Who on your team will manage orders and products
  6. Any system the store must connect to: accounting, a shop's point of sale, a delivery company
  7. Your domain, and any existing site or store

A short written brief covering these is enough to start; there is a template in how to write an app or website brief.

Building your store

I design and build business websites and web apps, from WordPress sites a team edits themselves to custom Next.js builds with their own admin and API, and I set up the hosting and deployment at launch. More about that work is on the website development page. If you are planning an online store, email me with what you sell and how you deliver today, or ask for a call in that note.

More from the blog

Let's work
together