E-commerce setup checklist

What an e-commerce setup has to deliver

An e-commerce setup is not a single technical event, it is the sum of the decisions that make a shop sellable. That includes the legal form of the mandatory disclosures, the choice of payment methods, the structure of the product data and the question of how orders will actually be processed later. Work through these points in order and you end up with a shop that can grow. Skip them and you pay twice, because fixing product data or payment logic later almost always costs more than deciding it properly the first time.

The most useful piece of advice up front: treat the setup as a project with one owner and an end date, not as a side task. A shop that goes live half finished loses its first visitors, and with them exactly the data you wanted to learn from.

The twelve steps at a glance

The order is not arbitrary. Legal and payment have to come before the data import because they define its requirements, and testing only makes sense once content and prices are complete.

1. Clarify the business model: B2C or B2B, own shop or marketplace, and what role the shop plays overall.
2. Prepare the mandatory legal pages: imprint, terms, cancellation policy, privacy notice.
3. Choose the platform: shop system, hosting, domain, and separate development and production environments.
4. Decide on payment methods, driven by audience and average basket size.
5. Define shipping logic: flat rates, weight tiers, delivery times, bulky goods.
6. Configure tax and prices, including gross and net display.
7. Structure the product data: categories, attributes, variants, properties.
8. Write the content: homepage, category pages, product copy, legal texts.
9. Set up tracking and analytics, with consent for anything that is not strictly necessary.
10. Define order processing: who sees orders, who picks, who ships.
11. Run a test order, from the product page through to the invoice and the return.
12. Plan the launch: redirects, sitemap, monitoring, and someone on call that day.

Phase 1: the foundation

Mandatory legal pages

Legal texts are where mistakes are most expensive, because in the worst case each infringement carries a formal warning with costs. A generic template from the internet is usually not enough once you deviate from the standard case, for instance with digital products, subscriptions or B2B business. As a frame for that review we suggest the Legal & Compliance seminar, because it works through the typical problem cases of a shop systematically.

Check at least these points: a complete imprint naming the authorised representative and an email contact, terms that clearly describe how a contract is formed, a cancellation policy including the model withdrawal form, correct price information with unit pricing where required, delivery time statements, and a privacy notice that names the services you actually use. A right of withdrawal that exists in the text but cannot be found in the checkout remains a risk.

Platform and hosting

The platform choice determines how much you can change yourself later. For a shop with its own processes you want a system that models product data rather than merely storing it, because variants, tiered prices and B2B logic hit limits quickly otherwise. We build on Shopware because categories, properties and price rules are all expressible through standard mechanisms. If you want to take that route with us, E-Commerce Setup describes exactly that path from planning to launch.

Set up two environments, one for development and one for live traffic. Never work directly on the live system. Enable HTTPS before the first visitor arrives rather than afterwards, and make sure backups run automatically and that a restore has actually been tested once.

Payment and shipping

Payment methods decide your checkout abandonment rate. The rule of thumb is to offer the two or three methods your audience genuinely expects and to add the rest only after the first hundred orders. Every additional method costs fees and adds complexity to refunds.

• Invoice lifts conversion noticeably but moves the default risk onto you.
• SEPA direct debit is cheap but needs a mandate and only works with an established relationship.
• Card and wallets are expected and should always be present.
• Prepayment carries no fees but is rarely chosen and slows the order down.

The same pragmatism applies to shipping. Flat rates are predictable, weight tiers are more accurate but more error prone. If you use flat rates, check once a quarter whether the real postage still matches.

Phase 2: data and content

The effort behind product data is almost always underestimated. A workable structure starts with the properties customers need in order to filter and ends with the attributes that are actually rendered on the product page. Everything in between is ballast.

Decide which source leads. If prices and stock are maintained in an ERP, there must not be a second truth in the shop. For day to day operations this matters more than which shop system you picked.

For content there is one simple rule: write the text your audience searches for before buying, not the text you want to tell about yourself. A category page needs to answer how the products differ, and a product page needs the information that actually secures a purchase decision: dimensions, materials, delivery time, accessories, limitations.

Phase 3: before launch

The test order is the step most often skipped under time pressure, and the step that most often saves a launch. Test not only the order itself but the whole chain: order confirmation email, invoice with correct VAT, picking in the warehouse, shipping notification with tracking, return registration, credit note.

Also verify that an order stays visible even when the confirmation mail lands in spam, and that a refund is possible without touching the database by hand. Once those two cases work, the shop is operational.

Cost and timeline

The figures below are ranges from projects in the German mid market. They move with catalogue depth and the number of integrations, but they work as a planning frame.

For a shop with a manageable catalogue and standard processes, eight to twelve weeks is realistic. As soon as an ERP is connected and B2B logic with customer group pricing is required, five to seven months is the honest expectation. Planning for four weeks is not planning tightly, it is planning wrongly.

The five most common mistakes

1. Payment methods chosen by availability instead of by audience. Result: a high drop off rate at the checkout.
2. Product data imported without a property structure. Result: filters and category pages nobody can use.
3. Legal texts not adapted to your own processes. Result: warning risk and disputes in refund cases.
4. No test order before launch. Result: a whole batch of incorrect invoices.
5. No monitoring after launch. Result: missing payments or missing orders only surface through annoyed customers.

Frequently asked questions

How long does an e-commerce setup take?

For a standard business with up to 500 products and no ERP integration, eight to twelve weeks is realistic. With ERP integration, B2B pricing and multiple languages the effort lands at five to seven months. The bottleneck is almost never the technology, it is the time you can personally contribute to decisions and data maintenance.

What does an e-commerce setup cost?

For a shop with standard requirements the effort usually sits between 20,000 and 60,000 EUR, including concept, build, data import and integrations. Add ongoing costs for hosting, payment providers and maintenance, which range from roughly 500 to 2,500 EUR per month depending on size.

Do I need my own shop to start, or is a marketplace enough?

This is not an either or decision, it is a sequence. A marketplace delivers visibility and demand but takes commission and gives you little control over customer data and brand presentation. Your own shop builds an asset but needs traffic. The pragmatic route is often to start with your own shop and add marketplaces as an extra channel once processes are stable.

Which comes first, technology or legal?

Legal comes first, because it defines the requirements for technology and data. Anyone who builds first and then checks whether the checkout transports the cancellation terms correctly usually builds parts of it twice.

Conclusion

An e-commerce setup succeeds when you keep the order: legal and business model first, then platform and payment, then data and content, and testing and launch last. The most expensive mistake in the whole project is the one saved on the test order. After launch the task list does not get shorter, it gets more operational, which is why looking at day to day processes early, as covered in the E-Commerce Operations seminar, pays off before you start.