WebEngine

0%
Web Development

Building an Online Store: Platforms, Payments and Delivery

Choosing a platform, wiring payments and shipping, product pages, cart and checkout — and which of those moves store conversion the most.

Pavlo8 min read

A catalogue with a Buy button is not a store. A store begins where the order reaches the warehouse, the payment reconciles with the bank, and the product page stops showing "in stock" for something that sold yesterday. Below is every moving part in order: platform choice, payments and shipping, the product page, checkout, and what breaks in month two — with the numbers you need to plan a budget.

1–3%

normal visitor-to-order conversion

70%

cart abandonment is the market baseline

$3k

realistic start for a store with integrations

2.5s

LCP threshold before mobile traffic drops off

Platform: three scenarios, not thirty

Comparing twenty content management systems wastes a week. The real choice collapses into three scenarios, plus a zeroth one — validate demand on a marketplace first. The deciding question is not "which platform is best" but "how many SKUs do I have and how unusual is my pricing logic".

OptionSetupRunning costWhen it is the right call
Hosted SaaS builder$0–500$30–120/mo plus a cut of revenueFirst 100 orders, under 200 products, standard logic
Off-the-shelf CMS with modules$1,500–4,000$20–60/mo hosting200–2,000 SKUs, you need control over templates and SEO
Custom or headless build$5,000–15,000$40–150/moComplex discounts, multiple warehouses, B2B pricing, speed targets
Marketplace instead of a site$010–20% commission per saleTesting demand before investing in your own store
2026 benchmarks, excluding content production, photography and advertising.

Payments and shipping: the underestimated node

This is the most common reason a launch date slips — not because the integration is hard, but because it depends on third parties and paperwork. Allow two to three calendar weeks even though the work itself is about five days.

  • Card acquiring — 1.8–2.8% per transaction. Approval takes 3 to 10 working days and requires a registered business entity, bank details, and a live site with published terms.
  • Cash on delivery — still 40–60% of orders in many categories. You need partial-prepayment logic, otherwise your collection rate drops.
  • Courier and parcel-locker integration — not "add an address field", but a live API for locations with autocomplete plus label generation from the admin. That saves 2–4 minutes per order.
  • Apple Pay and Google Pay — the cheapest available lift in mobile conversion, typically 5–12% more completed orders, because manual card entry disappears.
  • Instalments or buy-now-pay-later — worth it above an average order value of roughly $150. Below that the integration never repays the 15–25 hours it takes.

The product page: what actually moves a decision

The product page absorbs most of your search traffic and is where the decision happens. On projects where we rebuilt only that page and touched nothing else, conversion rose 15–30%. The cause is always the same: the buyer was missing facts, not persuasion.

The minimum a product page needs to work

  • 5–8 images: product on white, macro detail, scale next to a familiar object, product in use
  • Price and stock status above the fold — on mobile as well as desktop
  • Shipping cost and delivery window on the product page, not discovered at checkout
  • Specifications as a table, not a paragraph — people scan them, they do not read them
  • Returns policy in one sentence, next to the buy button
  • Product structured data covering price, availability and reviews so search results carry them
  • Related items below the fold — the cheapest way to hold a visitor who did not buy

On copy: a 200-word description paraphrasing the product name helps neither the buyer nor search. Write against the questions people actually type — "will it fit", "how do I clean it", "how is it different from". Gathering those queries is covered in our guide to SEO for online stores.

Cart and checkout: where the money leaks

Seventy percent cart abandonment is not a disaster, it is the market baseline. But roughly a quarter of those carts are recoverable through checkout mechanics alone, without discounting anything.

  1. 1

    The cart is a panel, not a separate page

    Adding an item should not eject the shopper from the catalogue. A slide-over panel with a "keep shopping" button typically adds 10–20% more line items to the average order.

  2. 2

    Guest checkout is the default

    Mandatory registration costs about 20% of orders. Create the account silently after payment and email credentials later, if an account is needed at all.

  3. 3

    One screen, 5–7 fields

    Name, phone, shipping method, pickup point, payment method. Drop middle names, postcodes and order comments — the postcode comes from the lookup and the comment matters on one order in twenty.

  4. 4

    Full total before the card form

    The single most common abandonment trigger is shipping cost appearing on the last step. Show the final number before you ask for money.

  5. 5

    Errors next to the field, never at the top

    Validate on blur and put the message under the input. A red banner at the top of the page frequently sits off-screen on a phone.

Checkout does not sell. Its only job is to stay out of the way of someone who has already decided to buy.

After launch, stop trusting intuition: wire cart and checkout events into analytics and watch which step people vanish on. The method for running those checks in sequence is in our guide to conversion rate optimisation.

What breaks in month two

The store you sign off and the store six weeks later are different systems. Here is the order in which problems usually appear, and what to build in ahead of time.

  1. 1Stock levels drift from reality. Manual updating survives up to about 20 orders a week; past that you need inventory sync every 15–30 minutes.
  2. 2Orders get lost between email and messenger threads. A CRM integration solves this: every order becomes a record with a status and an owner.
  3. 3Transactional emails land in spam. Configure SPF, DKIM and DMARC at launch rather than after the complaints — a day of work.
  4. 4Filtered catalogues slow down past 500 products, nearly always for the same reason: filtering pulls the full product list into memory instead of querying an index.
  5. 5Returns and partial cancellations were never designed into the admin. Work that scenario out before launch, or finance will run it in a spreadsheet.

Frequently asked questions about building an online store

How long does it take to build an online store?

A store on an existing platform with standard integrations launches in 6–10 weeks; a custom build takes 3 months or more. The critical path is set by external dependencies rather than code: payment approval takes up to 10 working days, and photography and descriptions for several hundred products is weeks of content work. Run those tracks in parallel with development.

Can I start on a hosted builder and move to a custom site later?

Yes, and it is often the sensible route: a builder validates demand for $30 a month instead of several thousand dollars. Two conditions make the move painless — use your own domain from day one, and confirm you can export products and customers. The migration then becomes a data transfer with preserved URLs rather than a fresh start.

How many products do I need for a store to make sense?

There is no technical minimum — a 15-item store can outperform a 3,000-item catalogue. What matters is whether search demand exists for your specific products and whether the average order covers payment fees and shipping. Below roughly $15 per order the economics rarely work without very high volume.

What should I do about product photography if I have none?

Supplier images are acceptable for launch, but every competitor has the identical files, so they give you no edge in image search. Your own shoot costs roughly $3–10 per item above a hundred products and pays back on the pages that receive the traffic. Start with your top 20 products by demand.

Why is my store slow when the hosting is expensive?

Store speed is almost never limited by server power. The usual culprits are uncompressed product images, a dozen third-party analytics and advertising scripts, and heavy database queries on filtered pages. The order in which to attack these, with acceptable thresholds, is set out in our breakdown of website loading speed.

In short

  • Choose a platform by SKU count and pricing complexity, not by fashion. Under 200 products a hosted builder usually wins on total cost.
  • Payments and shipping are a calendar risk, not a technical one. File the acquiring paperwork in week one.
  • The product page takes most of the traffic: images, stock status, shipping cost and specifications matter more than elegant copy.
  • Guest checkout on a single screen with the full total shown before the card form recovers part of that 70% abandonment.
  • Plan inventory sync and CRM before launch — manual handling collapses at around 20 orders a week.
Share
  • ecommerce
  • online store
  • web development

Related reading