A shop that is open day and night, and that is yours.

There are several ways to sell online, and your own shop is one of them. Selling on a marketplace brings instant reach: people come by who were already searching. In return the customer is not yours, the platform’s rules and fees apply, and you stand beside dozens of sellers of the same item, where price is often the only visible difference.

Your own webshop turns that around. You decide how products are shown, what story goes with them, how the customer is treated and what happens after the order. You keep the customer contact, may email those who consented and can build repeat business. That comes with work: visitors do not arrive by themselves and the shop needs maintenance.

For many businesses the honest conclusion is that both exist side by side. A marketplace as a shop window for the well-known items, your own store for the full range, the explanations, the bundles and the customers who return. Anyone with a physical shop often uses the webshop as an extension too: reserving, collecting, or simply showing what is on the shelves.

The question that comes first is simpler than it looks: what do you sell, to whom, and why would they buy it from you? A shop with a clear answer to those three does better than a shop with ten payment methods and no reason to stay.

A webshop can come about in four ways, and the choice mostly determines how much freedom you have and how much you arrange yourself. No form always wins; there is, however, a form that fits best per situation.

An off-the-shelf shop platform takes a lot off your hands: payments, shipping and administration are already in it. That works well for a manageable range without unusual requirements. The limit becomes visible as soon as your way of selling differs from what the platform expects — then you are building detours around rules you did not make.

An open package gives more room: the range, the screens and the integrations can be adapted extensively. Maintenance comes with it, because an open package left untouched becomes a risk. For many shops with their own requirements this is the middle ground.

A bespoke webshop is the fourth form and applies when the selling process itself is unusual: configurations, quotes, volume pricing, subscriptions to products, business customers with their own agreed prices, or an integration with a system the shop has to follow. Plaincodelab picks the form and the technologies that suit each project, and explains why — including what it means for maintenance and for the freedom to switch later.

The range is the heart of the shop, and immediately the place where most time goes. A product is rarely one thing: there are sizes, colours, flavours, editions, pack sizes. Every variant has its own stock, sometimes its own price, its own photo and its own article number. How those variants are set up determines whether administration later takes minutes or hours.

Stock is the second decision. Is it kept in the shop, or does it come from a till system, a wholesaler or an accounting package? As long as one place holds the truth, things stay calm. As soon as two systems both think they know, the familiar problems appear: sold items that turn out to be unavailable, or items on the shelf that are invisible online.

Then there is how customers search the range. Categories, filters on properties, a search that still works with a typo, and sorting that makes sense. With a handful of products none of this shows; from a few dozen onward it is the difference between finding and getting lost. Filters added afterwards also require every product to be given the matching properties after the fact.

Finally the product page itself deserves attention. It has to answer the questions a customer would ask an assistant in a shop: is this right for me, what is it made of, how big is it, what if I do not like it. A page that does this sells better and produces fewer returns and fewer emails.

Of all visitors who put something in the basket, a sizeable share drops out during checkout. That is not a law but a sum of small irritations, and those are exactly the fixable kind. Checkout is therefore the part where attention pays off fastest.

The best-known causes are always the same. Forcing an account before payment is allowed. Shipping costs that only appear in the final step. A form asking for details nobody needs. A missing payment method. A page that is awkward on a phone, while most orders come from there. Vagueness about when something is delivered or what applies on a return.

What works is almost boring: let people order without an account, show the total including shipping as early as possible, ask only what is needed to deliver and invoice, offer the payment methods your customers actually use, and show right after the order what will happen next. A confirmation that is accurate prevents half of all customer questions.

For business customers there is more: ordering on account, adding a purchase order number, entering a VAT number, or delivering to a different address than the invoice. Anyone serving business customers without supporting this sees those orders arrive by email — or not at all.

Payments in almost every webshop run through a payment provider. It handles the connection to the various methods, keeps payment details out of your own system and reports back whether a payment succeeded. The shop then only has to remember which order belongs to which payment and what happens on failure, cancellation or chargeback.

Which methods you need depends on your customers and where they are. In the Netherlands direct bank payment is common, alongside cards, pay-later, payment requests and, for business customers, payment on account. Every method brings its own behaviour: pay-later often lifts conversion but also returns, and payment on account requires agreements about reminders.

The administration should add up without manual work. An invoice that automatically matches the order, VAT calculated correctly per product type, shipping on the right line and an export or integration to the bookkeeping. This is the kind of work that is invisible at ten orders a week and becomes a day job at a hundred.

Finally the exceptions should be arranged before they occur: a payment that breaks off halfway, a customer who pays twice, an order to be cancelled after payment, a partial refund when one item out of three is returned. Those are the cases otherwise solved by email, every week again.

After the order begins the part the customer remembers best. Shipping is partly a choice — which carrier, which rates, which options such as collection or a delivery window — and partly a matter of having the process in order. Anyone making labels by hand per order and emailing the customer themselves keeps that up to about ten orders a day.

The shop can take over most of that work. An integration with a shipping party creates labels based on weight and dimensions, sends track & trace to the customer and marks the order as shipped. Packing slips print in batches, return labels take one action. That saves not only time but also the mistakes that come from retyping.

Returns deserve their own place in the setup, because they are not an exception but part of selling at a distance. A customer has the legal right to withdraw within the statutory period; how you arrange that decides whether it is a burden or a selling point. Clarity up front — how long, who pays the return postage, how quickly is money refunded — prevents argument and lifts sales, because it gets hesitant buyers over the line.

For shops with premises, collection is often the underrated option. No shipping costs, no waiting, and the customer is standing in your shop. Reserve and collect is technically simple to add and changes the webshop’s role from channel to shop window.

Selling to consumers online is bound by rules. They are not complicated, but they are scattered and often discovered only when a complaint arrives. The easiest route is to take them along during the build; afterwards almost always means changing several places.

The core is about clarity up front. The customer should know who the seller is, what the total is including VAT and shipping, how payment works, when delivery happens and what rights apply when withdrawing from the purchase. For consumers there is a statutory cooling-off period, with a model form and a deadline for refunds.

On top of that come obligations unrelated to the order: company details and chamber of commerce number that can be found, terms available before the order, a privacy statement that matches what actually happens, and consent before non-essential cookies are placed. Anyone sending a newsletter needs consent for it and must make unsubscribing easy.

Certain products add requirements: age verification, labelling, safety information, warranty terms or food regulations. Those should be known before the shop is set up, because they affect the product page and the order process.

A shop without visitors sells nothing, and visitors rarely arrive by themselves. For webshops the opportunities differ from ordinary sites: people search for products, brands, sizes and combinations of those. That means category and product pages do the work, not the homepage.

Category pages are often underestimated. Somebody searching for a product type would rather land on an overview with filters and explanation than on one arbitrary item. A short, genuine text above or below such an overview — what there is to choose here, where the differences lie, what to watch for — helps both the visitor and the search engine.

Product pages have their own points: a unique description instead of the supplier text a hundred other shops also use, clear titles, photos that match, and structured data allowing price, stock and reviews to appear in the search result. That last one is exactly what makes a shop stand out in a list.

Beyond that the ordinary rules apply: a shop that loads fast, works well on a phone, does not create duplicate pages through filters, and whose old addresses keep working after a move. Assistants summarising on a user’s behalf also take their information from those pages: the clearer it says what you sell, to whom and on what terms, the greater the chance of being mentioned.

A customer cannot pick anything up. Everything they would feel, weigh or try on in a shop has to be replaced by image and text. That is not a side issue to be arranged after the build, but the part that decides between looking and buying.

With photos, honesty and repetition matter most: several angles, something for scale, close-ups of material or finish, and where possible the product in use. One supplier photo on a white background does exactly the same for you as for every other shop using it.

Text does not have to be long, but it does have to be complete. What is it, who is it for, what is included, which size or quantity, what is it made of, what should you know before ordering. Anyone who writes down the questions arriving by phone or email has, within a week, the best source for product text there is.

It pays to treat this content as part of the shop rather than an attachment. A shop with fifty products needs fifty of these pages, and that work is real. Underestimate it and you open a shop with empty shelves that looks technically fine.

The customer pays in advance to a shop they do not know. Anything lowering that barrier sells. It starts with the basics: real company details, an address, a phone number or a contact form that gets answered, and a shop that looks cared for. A missing address stands out more than most owners think.

Reviews are the strongest instrument, provided they are genuine. A shop with a handful of honest reviews, including a critical one, inspires more confidence than a shop with fifty perfect scores. Reviews at product level also help with doubts about size, quality or use.

Beyond that it is about clarity on what happens when things go wrong. What if it does not fit, what if it arrives damaged, what if it is late. A shop that is calm and concrete about this beats a shop that hides it. The same goes for delivery: an indication you can rely on does more than a promise that is sometimes missed.

Finally it helps when the shop shows there are people behind it. A page about the business, a photo of the premises or workshop, an explanation of where products come from. That is not marketing but information, and it is exactly what a customer looks for before entering their details.

A webshop rarely stands alone. There is usually already a till system, a stock administration, an accounting package or a wholesaler supplying the items. The question is which system leads and which way the data moves. Without that answer two truths appear, and two truths cost time every week.

The most common integrations are predictable: stock from till or warehouse to the shop, orders from the shop to the administration, invoices to the bookkeeping, shipping instructions to the carrier, and product data from the supplier to the shop. Every integration that works well removes manual work that would otherwise grow with the number of orders.

What to watch: how often data is exchanged, what happens when a system is briefly unreachable, and who wins in a conflict. An integration running once a night is fine for product data and risky for stock of scarce items. Choices like that should be made deliberately rather than by accident.

For shops with premises the till integration is often the most important: one stock, whether you sell online or over the counter. That prevents the most annoying situation there is — selling an item online that went over the counter an hour earlier.

For a shop, speed is not a luxury. Visitors click through lists, open products, go back, filter again. Every step that feels slow costs a share of visitors, and the effect compounds during checkout. Heavy imagery is the best-known culprit: full-resolution product photos on a category page with thirty items.

Most traffic comes from phones, which is immediately the screen most shops are least tested on. Filters that fill half the page on a small screen, buttons too close together, form fields that do not open the right keyboard, a basket you lose when going back. These are not cosmetic flaws but direct reasons to leave.

On top of that comes everyday operation. Can a colleague quickly add a product, adjust a price, find an order or help a customer calling about their delivery? A shop designed from the customer’s side but not from the owner’s costs time every day that nobody budgeted for.

Finally: things occasionally break. A payment provider hiccups, an integration errors, an order hangs. A shop should then behave predictably and make the problem visible instead of swallowing it silently, so an order never disappears unnoticed.

The first order is the most expensive. Anyone who never hears from you again has been a customer rather than being a customer. Repeat business is therefore where your own shop cashes in its advantage over a marketplace — provided something is set up for it.

It starts with the order itself: an accurate confirmation, a message on dispatch and, if wanted, a short question afterwards about whether everything was right. That is service rather than marketing, and it produces the reviews that pull the next customers over the line.

Then come the usual instruments: a newsletter for those who sign up, an account holding earlier orders, one-action reordering for consumables, or a notice when something is back in stock. Which of these make sense depends entirely on what you sell: one-off purchases call for something different than items that run out monthly.

What matters is that consent and unsubscribing are handled properly. People who sign up want something worth receiving; people who unsubscribe should manage it in one click. A list full of people who would rather leave does more harm than a short list of people who stay.

A webshop is technically reachable everywhere, but selling in another country is more than a translate button. Choices arrive around language, currency, VAT, shipping costs, return addresses and customer questions in a language you have to be able to answer.

Language is the visible side. A half-translated shop inspires less confidence than a shop honestly in one language. Translating means not only the buttons, but product texts, terms, emails and the pages people land on. That work grows with the range.

The administrative side needs preparation. Selling to consumers in the European Union brings rules about where VAT belongs once you pass certain thresholds, with a declaration system you can register for. Return periods, packaging and labelling rules and the usual payment methods also differ per country.

The practical side matters just as much. What does shipping cost, how long does it take, who pays for a return from abroad and where does that parcel end up? Many shops therefore start with one or two neighbouring countries and only expand once that process runs smoothly.

Not everything sold fits in a box. More and more shops sell services, digital files, gift credit, tickets or deliveries that repeat alongside their articles. Technically that resembles an ordinary order, but the ordering process and the administration behind it work differently.

With digital products shipping disappears and a new question appears: how does the customer get it, how long does it stay available and what happens with a new version. A download link that stops working after a year produces as many customer questions as a lost parcel. The right of withdrawal also works differently for digital delivery, and the customer should be told clearly in advance.

With services it is usually an appointment rather than an article: a moment, a number of hours, a slot in the calendar. Availability then comes into play, along with the question of what happens on cancellation or rescheduling. A shop that arranges this properly replaces a lot of back-and-forth by email.

Repeat deliveries — the same package every month, fresh stock every quarter — are the strongest form for some ranges. They do require the shop to understand a standing arrangement: when is the next delivery, when is it paid, how does a customer pause or stop, and what happens when a payment fails. Working that out in advance keeps it from becoming manual work.

A webshop holds data others find worthwhile: names, addresses, order history and sometimes accounts with saved preferences. Payment details should not be in there — those stay with the payment provider — but the rest deserves protection that goes beyond a good password.

The basics are well known and not complicated: a secure connection across the whole shop, passwords stored hashed, sessions that expire, limits on sign-in attempts and forms, and an admin environment that is not open to everyone. Components that age should be updated; a shop standing still for two years becomes a target by itself.

There is also abuse that has nothing to do with break-ins. Orders with stolen card details, customers who systematically return everything, automated traffic snapping up scarce stock, or fake reviews. Simple measures help: checks on unusual orders, limits per customer, and the ability to hold an order before it leaves.

Finally the data itself. Keep what is needed and no more, be clear about what happens to what you keep, and make sure a customer can view and delete their data. That is not only a legal requirement, it is exactly what a customer looks at before leaving their address.

Most shops that do not perform have no technical problem. They have a shop that looks fine, with products nobody can find, text taken from the supplier and a checkout asking one step too many.

The second category is underestimating the work afterwards. A webshop is not a job that finishes: products are added, prices change, photos have to be taken, questions answered and returns handled. Without time set aside for that, within six months you have a shop with outdated stock and unanswered email.

The third is wanting too much at once. Five payment methods, three carriers, two languages and a till integration, while there have not been ten orders yet. Starting with what your customers actually use and expanding when there is reason to works almost always better.

The rest of the list below shows up in nearly every shop. Each can be prevented by recognising it in advance.

A webshop comes to life faster when the range and the rules are already sharp. Not because building is impossible otherwise, but because every unanswered question later becomes a screen that does not fit.

It comes down to a handful of things. Which products there will be and which variants belong to them. Where stock comes from. How you ship and what that costs the customer. Which payment methods your customers use. What your returns policy is. And whether there are business customers with their own requirements such as ordering on account or agreed prices.

It also helps to know what already exists: a till system, an accounting package, a file of articles, photos, an existing site with traffic and links. That determines what can be reused and what has to be made new — and whether old addresses need proper redirects so findability is preserved.

Plaincodelab chooses the form and the technologies that suit each shop, and explains that choice in plain language. What is needed depends on your range, your way of selling and the systems already in place — not on one fixed preference laid over everything.