Ecommerce: How Orders, Marketplaces, and Subscriptions Work
Ecommerce is defined by how the order is placed, not by whether the seller looks like an online retailer. It covers goods, digital products, and services ordered through internet-based systems, along with the money and data transfers needed to complete the transaction. That includes B2C, B2B, and C2C trade through websites, marketplaces, and mobile apps.
What ecommerce includes—and what it does not
Ecommerce is the broad umbrella for online buying and selling. Online retail is the narrower B2C subset in which a seller serves an end consumer. Digital commerce is broader in another direction: it includes the pre-purchase and post-purchase journey across digital touchpoints, while ecommerce refers to the transaction itself. Paystone and BigCommerce describe those boundaries.
M-commerce is ecommerce conducted on phones or tablets through mobile sites, apps, or SMS; it is a subset of ecommerce, not a competing category. Stripe’s comparison makes the channel distinction explicit. Ecommerce is also narrower than e-business, which includes digitized operations beyond buying and selling.
Common business-model labels include B2C, B2B, C2C, C2B, D2C, and B2B2C, alongside structural choices such as marketplaces and dropshipping. Shopify’s model overview describes B2C as the most common. The labels identify who transacts with whom; they do not by themselves tell you who owns inventory, controls fulfillment, or earns profit.
There is no single formula for ecommerce itself. Equations such as revenue equals orders multiplied by average order value describe sub-metrics, not the concept, and should not be presented as a definition.
Market-size and profitability figures need the same caution. Shopify’s summary of eMarketer data places ecommerce at about 20.5% of global retail sales in 2025, projects about 21.1% in 2026 and 22.5% by 2028, and notes that the share excluding China is closer to 12.8%. The headline is therefore not a universal market benchmark. Ecommerce can be profitable, but published net-margin ranges conflict—roughly 10–20% in some sources and 10–50% in others—because niche, model, and methodology differ. Bluehost’s overview is directional evidence, not a single agreed margin standard.
The order—not the storefront—sets the boundary
The order is the cleanest boundary for ecommerce. The OECD’s 2025 definition covers goods and services ordered through purpose-built systems over computer networks, even when payment or delivery happens offline. Web shops, apps, structured ordering features on social platforms, and electronic data interchange can qualify; a manually typed email does not under this statistical definition.
The OECD defines an ecommerce transaction by the method used to place or receive the order, not by the product, payment method, or delivery channel. Its 2025 guidance also addresses digital intermediaries and digitally ordered subscriptions.
That boundary matters because ecommerce is neither a synonym for digital marketing nor a single business model. A direct-to-consumer brand, a marketplace, a wholesaler receiving EDI orders, and a subscription service can all conduct ecommerce. What changes is who controls the offer, owns inventory, serves the customer, collects the money, and absorbs failure.
Merchant, marketplace, and subscription models allocate control differently
The consequential model choice is where control and risk should sit, not which storefront software to buy. An inventory-owning merchant gains more control over price, merchandising, and customer experience while taking on working capital, forecasting, fulfillment, and returns. A marketplace can widen selection without buying every item, but must attract both supply and demand and govern third-party quality. Subscription can make a recurring need easier to serve; it remains an overlay on the merchant or intermediary relationship rather than an automatic retention engine.
| Operating choice | Choose it when | Real strength | Real weakness | Primary economic lens |
|---|---|---|---|---|
| Inventory-owning merchant | Control of assortment, price, presentation, and service is central to the proposition | Direct control over the full customer experience and product margin | Cash is tied to inventory and the operator carries markdown, fulfillment, and return risk | Net sales and contribution after product and variable order costs |
| Marketplace or intermediary | Valuable supply is fragmented and buyers benefit from aggregated selection or matching | Selection can grow without the platform purchasing every item | Liquidity, seller quality, disputes, and role clarity become core operating problems | Fees or take rate; gross merchandise value is not automatically platform revenue |
| Subscription overlay | The underlying need recurs at a cadence customers genuinely value | Reordering becomes more convenient and future demand can be easier to plan | Cancellation, skips, failed payments, and unwanted replenishment can erase the apparent predictability | Cohort contribution and retention by billing or delivery period |
Accounting follows the actual contract, not the label placed on the website. Under IFRS 15’s principal-versus-agent framework, the central question is whether the entity controls the specified good or service before it reaches the customer. Primary fulfillment responsibility, inventory risk, and pricing discretion are indicators, but their weight depends on the arrangement.
IFRS guidance distinguishes a principal that controls the specified good or service before transfer from an agent that arranges for another party to provide it. The assessment is contract-specific rather than a generic rule that every marketplace reports revenue the same way.
Amazon’s 2024 Form 10-K is a concrete hybrid example. It says Amazon generally records gross revenue for items sold from its own inventory, while recording its net share from third-party seller items as service sales. It also says Amazon is not the seller of record in its seller-program transactions and earns combinations of fees, percentages of sales, per-unit fees, or interest.
Amazon’s disclosure shows why merchandise volume and reported revenue must remain separate in a hybrid model: the same storefront can contain inventory-owned retail and third-party intermediation with different revenue treatment.
One order moves through several state machines
A checkout confirmation is not the end of the transaction. Treat the order, payment, fulfillment, return, and cash ledgers as connected but distinct records, joined by durable identifiers.
| Stage | What changes | What the operator must preserve |
|---|---|---|
| Order | The buyer accepts an offer and the commerce system creates an order | Order ID, items, prices, discounts, taxes, customer, channel, and timestamp |
| Payment | The payment is authenticated, authorized, captured, processing, successful, or failed | Payment ID, amount, currency, status history, fees, and link to the order |
| Fulfillment | Inventory is allocated and goods or services are delivered, partially delivered, canceled, or otherwise resolved | Fulfillment ID, quantity, carrier or delivery evidence, cost, and order link |
| Adjustment | Returns, exchanges, refunds, and disputes change the customer’s outcome and the merchant’s economics | Reason, amount, item, restock state, variable cost, and original order link |
| Settlement | Processor balances become available and payouts reach the bank | Balance transaction, payout batch, fees, timing, and reconciliation status |
Payment authorization and capture are separate in some flows. Stripe’s PaymentIntent lifecycle can move through states requiring a payment method, confirmation, customer action, processing, capture, or success. Asynchronous methods may remain in processing before success is known.
In Stripe’s documented flow, a separately authorized payment can enter requires_capture, while a completed PaymentIntent enters succeeded. A failed attempt can return to requires_payment_method for another attempt.
Order operations need their own status model. Shopify’s order-status documentation separates order, payment, fulfillment, and return statuses. A voided authorization, canceled order, refunded payment, and completed return are therefore different events, even when a customer experiences them as one purchase.
Shopify documents payment states independently from fulfillment and return states; an open order can still require payment processing, fulfillment, or return work.
Cash arrival is another boundary. Stripe defines settlement time as the interval between a payment or funding transaction and the funds becoming available in the Stripe balance. Pending funds cannot be withdrawn or spent until they become available. A payout then needs to be reconciled to the transactions it contains.
Stripe’s balance documentation distinguishes pending from available funds. Payment success in the checkout flow should therefore not be used as a substitute for bank-payout reconciliation.
These systems answer different questions. Payment status says whether money collection progressed. Fulfillment status says whether the promise was delivered. Return and dispute records say how the outcome changed. Settlement says when processor funds became usable. Revenue recognition, tax, and legal obligations require the applicable contracts and jurisdiction; the operational state machine alone cannot decide them.
Repeat purchase matters only after variable economics
Revenue-based retention can make a weak ecommerce model look healthy. The useful unit is contribution: the money left from an order after costs that change with that order. A fuller customer lifetime value model then connects those cohort contributions to retention and acquisition payback.
Order contribution = net order revenue - product cost - payment cost - fulfillment cost - shipping subsidy - expected return/refund cost - other variable service cost
Define every term before comparing channels or cohorts. Net order revenue should already reflect discounts and refunds under the team’s stated reporting policy. Expected return cost should include more than the refunded price when the business also pays return shipping, inspection, repackaging, write-downs, or disposal. Fixed payroll and platform overhead belong in a later profitability view; mixing them selectively into some orders makes channel comparisons unstable.
Then group customers by first purchase and give every cohort the same observation window. Shopify’s customer cohort analysis uses the date of first order to form cohorts and can display customer retention, gross sales, net sales, or average order value across later periods.
Shopify’s report illustrates the essential cohort method: each row contains customers acquired in the same first-purchase period, while later columns show their activity at comparable elapsed intervals.
For a fixed horizon T, calculate:
Repeat purchase rate = customers with a second completed order by T / first-time customers in the cohort
Cumulative contribution per acquired customer = total realized order contribution through T / acquired customers in the cohort
Contribution after acquisition = cumulative contribution per acquired customer - customer acquisition cost
The acquisition investment has paid back within that horizon only when cumulative contribution per acquired customer reaches the acquisition cost. A high repeat rate does not guarantee this: later orders may be small, heavily discounted, expensive to ship, or frequently returned. Conversely, a lower-frequency category can still work if each repeat order contributes enough.
Three common shortcuts distort the picture. Returning-customer share can rise simply because new-customer acquisition fell. Average order value says nothing about purchase frequency or cost to serve. Revenue retention preserves neither gross margin nor acquisition payback. Keep all three as descriptive metrics, then make the decision with cohort contribution and time.
The operating trade-off is the decision
Choose an inventory-owning merchant model when control is worth the working-capital and fulfillment burden; choose a marketplace when aggregated supply creates value without ownership; add subscription only when the need recurs naturally—and approve growth spend only when fixed-horizon cohort contribution shows how acquisition is repaid.
Frequently asked questions
Is dropshipping a separate business model from ecommerce?
Dropshipping is a fulfillment method within ecommerce: the merchant accepts the customer’s order, while a supplier stores, packs, and ships the product. Shopify’s operating definition makes that division explicit. The merchant still needs a written responsibility map for product accuracy, support, returns, refunds, and delivery failures because outsourcing physical fulfillment does not automatically transfer the customer promise.
What is the difference between an abandoned cart and an abandoned checkout?
An abandoned cart records shopping intent before checkout identity or payment steps, while an abandoned checkout records a shopper who entered the checkout flow and left it incomplete. In Shopify’s platform model, contact information must be supplied and the checkout must remain incomplete for the defined period. Keep the two events separate in analytics and recovery rules because a cart view and an identified checkout support different messages, permissions, and conversion denominators.
How is a chargeback different from a refund?
A refund is initiated by the merchant through its payment flow; a chargeback or card dispute starts through the cardholder’s issuer and can reverse the payment while evidence is reviewed. Stripe documents that a dispute can debit the payment amount and add a fee. Route an open dispute through the provider’s evidence workflow and avoid issuing an uncoordinated second refund, which can create two separate adjustments against one order.
What should happen after a subscription payment fails?
Treat the failure as a recoverable billing state rather than an immediate cancellation or a license for endless retries. Stripe’s Smart Retries workflow combines bounded retries with failure events, customer notifications, and payment-method updates; a hard decline generally needs a new payment method before another attempt can succeed. Record retry attempts, service access, recovery, and final cancellation as separate events so retained subscriptions are not confused with recovered contribution.