Getting Started with

E-Commerce

E-commerce decisions are rarely just about choosing a shopping cart. The right platform must support how you sell, how customers pay, how orders are fulfilled, how taxes and shipping are calculated, how accounting is updated, how customer data is protected, and how the system can be maintained over time. A good starting point is to identify the business model, payment requirements, integration needs, hosting responsibilities, security exposure, and accessibility expectations before committing to a platform.

Platform fit matters

A small catalog, subscription business, B2B ordering portal, digital-product shop, custom quote workflow, and high-volume retail store may all require different cart behavior, checkout rules, integrations, and support models.

Payments drive decisions

Before selecting a cart, confirm whether it supports your current payment provider, gateway, merchant account, wallet options, installment payments, fraud tools, refunds, and settlement workflow.

Operations determine success

The storefront is only one part of e-commerce. Accounting, shipping, taxes, inventory, customer service, analytics, security, accessibility, and support must also fit the business.

Starting your first online store

If you are evaluating your first online store, the most important question is not which platform is most popular. The better starting point is how the business needs to sell. A simple storefront for a few products has very different requirements than a large catalog, a B2B ordering portal, a subscription business, a digital-download store, or a system that needs custom quotes, deposits, shipping rules, or accounting integration.

Early e-commerce decisions tend to become expensive to change later. Payment provider compatibility, product structure, tax handling, shipping methods, inventory rules, accessibility, hosting responsibility, and data ownership should be considered before committing to a platform.

Questions to answer before choosing a cart

  • Are you selling physical products, digital products, services, subscriptions, bookings, or custom quotes?
  • How many products or variations will you offer now and later?
  • Do customers need a shopping cart, or would invoices and payment links be enough?
  • Will customers pay online, in person, by invoice, through installments, or through multiple methods?
  • Do you need shipping rates, tax calculation, inventory tracking, and / or fulfillment integration?
  • Will the store need customer accounts, order history, returns, coupons, and / or subscriptions?

Early decisions that shape the platform

  • SaaS platform versus self-hosted cart
  • Open source, commercial, or closed-source licensing model
  • Payment provider, gateway, and merchant account compatibility
  • Accounting, shipping, tax, inventory, and marketing integrations
  • Product data structure, images, variants, and search/filter needs
  • Security, PCI scope, accessibility, backups, and ongoing maintenance
Practical starting point: Define the selling model first, then choose the platform. This helps avoid selecting a cart that looks easy at launch but cannot support the payment methods, integrations, accessibility needs, or operational workflows the business will need later.

SaaS vs. self-hosted e-commerce

One of the most important decisions is whether to use a software-as-a-service (SaaS) platform or a self-hosted cart. SaaS platforms usually reduce hosting and maintenance responsibility, while self-hosted platforms often provide more control over code, data, integrations, hosting, and customization.

SaaS e-commerce platforms

A SaaS platform is hosted and maintained by the platform provider. This can be a good fit when the business wants faster launch, less server responsibility, built-in updates, hosted checkout, and a predictable operating model.

  • Lower hosting and server-administration burden
  • Provider-managed updates and platform availability
  • Often faster to launch for standard storefront needs
  • May include built-in themes, apps, payments, tax, and shipping options
  • Can limit deep customization, data portability, or unusual workflows
  • Ongoing platform fees, transaction rules, and app costs should be reviewed

Self-hosted e-commerce platforms

A self-hosted platform runs on hosting you control or manage. This can be valuable for custom integrations, unusual workflows, data ownership, specialized hosting, or deeper code-level customization.

  • More control over hosting, code, database, and integrations
  • Better fit for custom checkout, pricing, catalog, or business rules
  • Can support deeper technical ownership and portability
  • Requires hosting, patching, backups, monitoring, and security responsibility
  • May need developer support for updates and troubleshooting
  • Performance depends heavily on hosting, caching, database design, and maintenance
Hosting matters for self-hosted stores: If you are considering a self-hosted cart, review the Hosting getting started guide before assuming a low-cost shared, VPS, or dedicated plan is enough.

Open source vs. closed source is not always simple

“Open source” and “closed source” are useful labels, but they do not tell the whole story. Some so-called open source platforms are feature-restricted community editions of larger commercial offerings. Some commercial products are closed-source SaaS platforms with limited customization. Others are commercial licenses where the code is readable or modifiable under defined license terms.

The practical question is not only whether a platform is open source. It is whether your organization can access, modify, maintain, secure, and extend the parts of the system that matter to the business.

Questions to ask about source and licensing

  • Is the version you plan to use fully featured or intentionally limited?
  • Are important features only available in a paid commercial edition?
  • Can your team or developer inspect and modify the code?
  • Are modifications allowed under the license?
  • Are updates, security patches, and extensions actively maintained?
  • Can you export products, customers, orders, and content if you leave?

Practical tradeoffs

  • Open source can provide flexibility, but maintenance still has a cost.
  • Closed source can reduce maintenance, but may limit customization and introduce hidden security threats.
  • Readable commercial code may be useful even if the license is not open source.
  • Community editions may omit features the business eventually needs.
  • Extension ecosystems can enhance the value of the platform or introduce compatibility and security risks.
  • Vendor lock-in should be evaluated before product and order data grow too large.

Payment integrations should be checked early

Payment compatibility should be confirmed before committing to a cart. It is not enough for a platform to “accept credit cards.” The platform must support your actual payment provider, merchant account, gateway, wallet requirements, fraud tools, refund process, settlement workflow, and reporting needs. If you haven't yet settled on a payment platform, your ideal E-commerce platform may better inform your choice of payment platform.

Common mistake: Businesses sometimes choose a cart first and discover later that it does not support their current payment provider, charges extra transaction fees for outside processors, or requires changing merchant accounts to use preferred checkout features. This is more common with SaaS solutions.

Payment questions to answer

  • Does the cart support your current payment gateway or processor?
  • Does it support your merchant account, or only preferred providers?
  • Are there extra platform fees for using an outside payment provider?
  • Can it handle refunds, partial refunds, voids, captures, and failed payments?
  • Does it support Apple Pay, PayPal, Venmo, ACH, or installment options if needed?
  • Can payment status be reconciled with orders, accounting, and fulfillment?

PCI and checkout responsibility

PCI DSS stands for Payment Card Industry Data Security Standard. It applies to the handling and protection of payment-card data. The safest e-commerce implementation avoids storing or directly handling raw cardholder data.

  • Favor hosted fields, tokenization, or hosted checkout when appropriate.
  • Understand whether card data touches your server.
  • Keep payment extensions and checkout code updated.
  • Document who owns PCI compliance tasks.

If you only need to accept payments or send invoices, not operate a full storefront, review the Payments getting started guide.

Integrations with accounting, shipping, taxes, and operations

E-commerce platforms rarely operate alone. The storefront usually needs to exchange data with accounting systems, shipping carriers, tax engines, inventory tools, CRM systems, marketing platforms, fulfillment providers, analytics tools, and customer support workflows.

Security, PCI, and accessibility are not optional extras

E-commerce sites handle customer trust. Even a small store may process personal information, order history, payment-related data, shipping addresses, account credentials, and support communications. Security and accessibility should be considered before launch, not treated as cleanup projects after problems appear.

PCI

E-commerce payment design should minimize exposure to cardholder data. Hosted checkout, tokenization, gateway-supported fields, and clear responsibility boundaries can reduce risk.

Review payment guidance

Security

Stores need secure administration, patched software, protected customer data, safe extensions, monitored access, backups, malware prevention, and an incident response path.

Review security guidance

Accessibility

Customers should be able to browse products, use search and filters, add items to cart, enter shipping and payment details, and complete checkout with accessible interactions.

Review accessibility guidance

Choosing the right e-commerce path

A platform decision should be based on the business model and operational requirements, not simply popularity. The best platform is the one that supports the required customer experience, payment flow, product structure, integrations, hosting model, security posture, accessibility needs, and long-term maintenance plan.

1. Define the selling model

Products, services, subscriptions, bookings, quotes, B2B ordering, digital goods, marketplace sales, and custom workflows all change platform requirements.

2. Confirm payments

Verify compatibility with your payment provider, gateway, merchant account, wallet options, refunds, fraud tools, settlement, and reporting.

3. Map integrations

Identify accounting, tax, shipping, inventory, fulfillment, CRM, email, analytics, customer service, marketplace, and reporting requirements.

4. Evaluate ownership

Compare SaaS versus self-hosted responsibility, licensing, portability, support, hosting, maintenance, security, customization, and long-term cost.

Why e-commerce guidance is helpful

Many organizations arrive at an e-commerce decision because something is already difficult: the current cart is outdated, the payment provider is not supported, shipping rates are wrong, taxes are handled manually, product data is messy, the store is slow, accessibility has been ignored, or the business has outgrown a simple storefront.

Common business problems

  • The current cart does not support the preferred payment provider.
  • Manual order handling is consuming too much staff time.
  • Customers abandon checkout because the flow is confusing or unreliable.
  • Shipping, tax, or inventory rules are producing errors.
  • Accounting reconciliation requires too much manual cleanup.
  • The business needs B2B pricing, customer-specific catalogs, or quote workflows.
  • The store cannot support subscriptions, deposits, installments, or recurring orders.

Common technical problems

  • The platform is slow, fragile, or difficult to update.
  • Plug-ins or extensions conflict with checkout, shipping, or tax behavior.
  • The cart depends on unsupported software or poor hosting.
  • Payment, shipping, accounting, or tax integrations are unreliable.
  • PCI scope, security updates, and data exposure are not well understood.
  • The storefront is not accessible to keyboard, screen reader, or mobile users.
  • Analytics and conversion tracking do not accurately reflect the buying journey.

E-commerce assessment checklist

Before selecting, replacing, or heavily customizing an e-commerce platform, document the practical requirements. This reduces the risk of choosing a cart that looks good during a demo but fails under real business conditions.

Useful decision factors

  • Catalog size and product complexity
  • Payment provider and gateway compatibility
  • SaaS versus self-hosted responsibility
  • Open source, commercial, or closed-source licensing model
  • Shipping, tax, accounting, and inventory integrations
  • PCI scope and security maintenance
  • Accessibility of product browsing and checkout
  • Data ownership, exportability, and migration path
  • Total cost including apps, extensions, hosting, development, and support

Typical deliverables

  • E-commerce platform assessment
  • SaaS versus self-hosted comparison
  • Payment provider compatibility review
  • Open source and commercial licensing review
  • Integration map for accounting, shipping, taxes, and inventory
  • Checkout and conversion audit
  • PCI, security, and accessibility review
  • Migration, modernization, or implementation plan

When an e-commerce consultation makes sense

A consultation is most useful when you are choosing a new platform, replacing an old cart, moving from SaaS to self-hosted or the reverse, integrating a payment provider, improving checkout, or trying to understand whether the current platform can support the next stage of the business.

Good reasons to ask for help

  • You are unsure whether SaaS or self-hosted is the better fit.
  • Your preferred payment provider is not clearly supported.
  • You need accounting, shipping, tax, or inventory integration.
  • You are worried about PCI, security, or customer data exposure.
  • Your cart is slow, outdated, inaccessible, or difficult to maintain.
  • You need custom checkout, B2B pricing, subscriptions, or unusual order workflows.

Good questions to answer first

  • How do customers choose products and complete orders?
  • Which payment provider, gateway, or merchant account must be supported?
  • Which systems need to receive order, tax, shipping, inventory, or accounting data?
  • Who will maintain the platform, apply updates, and monitor security?
  • Can the business export product, customer, and order data if it changes platforms?
  • Can customers with disabilities complete the buying process?

Reference standards and useful sources

Use these references as starting points for payment security, web accessibility, search visibility, and performance planning.

Choose the platform around the business process

Whether you are choosing a new cart, replacing an old storefront, comparing SaaS and self-hosted options, validating payment-provider compatibility, or planning integrations with accounting, shipping, taxes, and inventory, we can help identify the practical path forward.