E-commerce
April 8, 2026
Under the term e-commerce features, we group together all the software capabilities that make it possible to sell online: display a catalog, manage a cart, process payment, track an order, administer prices and stock, connect logistics and marketing tools. This is not a fixed list: depending on your model (B2C, B2B, marketplace, subscription), the useful scope changes.
This Foundations guide provides a clear framework for prioritizing a project: which building blocks are standard on a modern platform, which fall under extensions or integrations, and how to avoid confusing a “visible feature” (button on the site) with a “hidden feature” (business rules, APIs). It extends the operation of an e-commerce business. The examples often rely on the Shopify integration as a reference ecosystem: menu names may differ, but the logic (product, variant, order, fulfillment) is widely shared among mature platforms.
Qstomy is added as a conversational layer: not a substitute for the catalog or payment, but a complement for support and assisted selling when customer journeys require it.
In product workshops, classify needs into legal blockers (consent, invoicing), business blockers (payment in the target currency), then differentiators (advanced personalization). This framework prevents funding gimmicks before the foundations.
Technical teams appreciate when we distinguish between business need (rule to apply) and solution (app A or B): the solution can change if the need is clearly defined.
Finally, remember that a disabled feature still exposed in the code or theme can create front-end bugs: clean up unused modules and experimental flags after A/B testing.
The finance teams need accounting exports and cash reconciliation: plan for these exports in scope from the tool-selection phase, not as a late addition.
The legal teams often validate legal notices, withdrawal rights and proof of consent: involve them early to avoid blocking a commercial launch at the last minute.
For brands that also sell in physical stores, unified stock and seamless journeys features (availability search, reservation) connect digital to the point of sale: a cross-functional IT and retail effort.
Summary
Definition: front-end, back-end, and integrations functionality
An e-commerce feature can be read on three levels: front office (what the visitor sees), back office (what the team configures), interconnections (ERP, carriers, CRM, email tools). A single “buy in one click” capability often relies on several technical building blocks behind the interface.
Must-have vs nice-to-have
A reliable cart and secure payment are foundations; augmented reality on the product page can wait if your traffic or catalog does not justify it.
Omnichannel consistency
Features must align across the site, email, and ads: a falsely displayed stock level breaks trust faster than a lack of an aesthetic filter.
Functional debt
Stacking apps without governance creates duplicates (two review modules) or conflicts (two consent pop-ups). An annual inventory of extensions limits this debt.
Roadmap
Prioritize by business impact and total cost of ownership: team time, subscriptions, maintenance.
Internal documentation
Keeping a record of activated features and their business owner makes audits and hiring easier: a new hire understands why a given module exists.
User testing
Observing real customers browse search and checkout reveals gaps between product intent and actual usability.
Showcase: catalog, search, navigation and product pages
The visible core remains the catalog: categories, lists, detailed product pages with media, attributes (size, color), availability, and price. Search and filters become critical once you have just a few dozen items.
Variants and variations
SKU, barcodes, stock by variant: modeling determines what follows (targeted promotions, warehouse synchronization). To go further: e-commerce product catalog.
Rich content
Reviews, Q&A, buying guides: all blocks that increase conversion but require moderation and updating.
SEO and lists
Tags, internal linking, pagination: listing features influence discoverability: see e-commerce SEO.
Merchandising
Featured placement, badges «new», sorting by margin or by stock: digital merchandising extends the commercial work of the physical store.
Accessibility and mobile
Text zoom, contrast, keyboard navigation, and readability on small screens are not reserved for «institutional» sites: they also influence conversion and technical SEO.
Media and performance
Lazy loading, WebP or AVIF formats, video transcoding: settings that are part of the product experience perceived as «modern» or «slow».
Syndication
Google Merchant feeds, affiliate partners: exporting the catalog properly is a cross-functional data and marketing feature.
Cart, checkout and payment
The cart keeps the line items, applies discounts and promo codes, calculates taxes and shipping costs. The checkout collects addresses, shipping options, payment method, and legal consents.
Friction and conversion
Each extra field can reduce conversion: see cart abandonment; the funnel design is detailed in the dedicated guide to e-commerce site design.
Payment
Card, wallet, bank transfer, installment payments depending on the country: the gateway must handle 3-D Secure, failures, partial refunds.
B2B and quotes
Cart with hierarchical approval, net prices according to contract, deferred payment terms: extensions often specific to the business segment.
Recurring billing
Subscriptions and recurring direct debits add failure handling, upgrades, and a self-service portal.
Guest checkout
Allowing purchase without an account reduces friction but makes later loyalty more difficult: a trade-off to document.
Persistent cart
Retrieving a cart on another device or after a reminder email increases the recovery rate: configure retention periods and privacy.
Dynamic shipping costs
Real-time calculation based on the cart and destination avoids surprises on the final screen, the main reason for abandonment.
Customer account, orders and self-service
The customer area provides order history, parcel tracking, downloads (invoices), saved addresses, wishlists. Returns and after-sales support features reduce support tickets.
Authentication
Email / password, SSO, social login: each option has an impact on security and compliance.
GDPR
Data export and deletion, marketing preferences: to be built in from the design stage, not as an afterthought.
B2B Profile
Multiple users per company account, buyer / approver roles: features often absent from standard pure B2C commerce.
Transactional Communication
Confirmation, shipping, and delivery emails and SMS: editable and customizable templates are part of the expected functional scope.
Warranty Portal
Report a fault, attach proof of purchase, track an exchange: journeys often forgotten during scoping, yet a major driver of support requests.
Invoices and Credit Notes
Compliant PDF downloads, automatic sending to B2B customer accounting: strong expectations as soon as the average basket size increases.
Communication Preferences
Preferred channel, follow-up frequency: features that connect to your CRM or email tool.
Merchant back office: products, stock, prices, promotions
The administration allows you to create and update products, manage collections, launch promotional campaigns, and adjust inventory manually or via synchronization. Validation workflows (draft, publication) help avoid errors in production.
Pricing rules
Automatic discounts, codes, B2B catalog pricing, quantity tiers: complexity grows quickly with the number of channels.
Multi-stock
Warehouses, stores, partners: reserving the right stock for the right order is a foundational feature for omnichannel.
Permissions
Who can modify prices or issue refunds? Admin roles limit operational risk.
Audit log
Tracking changes to prices or product listings helps in case of disputes or human error.
Imports and feeds
CSV import or PIM connector: the import feature must handle line-by-line errors and provide actionable reports.
Scheduling
Publish a collection at a specific time for a launch coordinated with PR and social media.
Logistics and fulfillment seen as functional building blocks
Beyond the site, the features include shipping profiles, labels, tracking, and sometimes 3PL integration. See the dedicated guide to fulfillment services.
Displayed promises
Lead times by zone, eco vs express modes: the front end must reflect the rules that are actually executable in the back end.
Click and collect
Store selection, time slots, notification when the package is ready: a cross-functional workflow.
Tracking numbers
Surfacing tracking to the customer and the account area reduces requests for "where is my package".
Returns management
Request portals, prepaid labels: to be linked to your returns policy (see also Qstomy's blog article on returns management in e-commerce).
Order preparation
Picking slip, wave picking, warehouse list printing: sometimes managed in an external WMS, but statuses must be sent back to the store to inform the customer.
Partial fulfillment
Ship only part of the line items and cancel the rest or put it on hold: rules to clarify on the functional side to avoid duplicate shipping charges.
Gift givers and gifts
Card message, gift wrapping, sender anonymity: options that complicate picking but increase perceived value.
Marketing: acquisition, loyalty and content
Many platforms expose building blocks for discounts, codes, loyalty points, sometimes blogs and landing pages. Often, advanced marketing relies on connectors (email, SMS, ads) rather than on the core alone.
Pixels and audiences
Event tracking (product view, purchase) powers personalization and ROAS measurement.
Referral programs
Unique code per customer, automatic credit: a cross-functional feature for accounting and support.
Social commerce
Catalogs connected to networks, native checkout: the scope extends beyond the owned site.
Personalization
History-based recommendations: useful but to be calibrated with privacy and data quality.
Multi-touch attribution
Understanding which channels contribute to the sale requires tracking features and attribution models, often outside the native platform.
Promotion consistency
A site discount + influencer code + cashback must be calculated without negative margin: stacking rules to test.
Loyalty and CRM
Linking loyalty points, VIP tiers, and segmented email campaigns requires stable customer identifiers and non-stacking rules consistent with checkout.
Editorial content
Blog, guides, lookbooks: CMS features sometimes are rudimentary in the commerce admin; a headless CMS paired with the front end can better serve marketing teams.
UGC
Customer photos, video reviews: moderation and image rights to plan for before opening the public feed.
International, displayed taxes, and local compliance
Selling abroad adds currencies, translations, VAT or sales tax rules, address formats, local payment methods. Some features are natively supported by the platform, others come from specialized apps.
Geolocation and consent
Adapt content and cookies according to the visitor's country without hurting SEO or performance.
Legal notices
Terms and Conditions, privacy policy, right of withdrawal: version them by market if necessary.
Regulated markets
Alcohol, health, games: age verification or prescription verification features may be required.
Performance by region
CDN and regional hosting: the perceived “feature” includes loading speed.
Prices shown incl. / excl. tax
Depending on B2B or B2C audience and country, the display requirement varies: configure the views without manually duplicating the entire catalog.
Geographic restrictions
Block sales to certain countries for licensing or shipping reasons: cart and checkout filters to test thoroughly.
Localized legal content
Manufacturer information, sorting icons, instructions: display on the product page without weighing down the purchase journey.
Security, availability, and access governance
SSL, PCI compliance for payments, login attempt limiting, backups: all these are requirements that are not visible from a marketing perspective but determine business continuity.
SSO and MFA
For admin teams, stronger authentication limits account takeovers.
Hosting SLA
Uptime, maintenance windows: read the cloud or platform contract.
Fraud
Order scoring, blocklists: features often plugged in via apps or a payment provider.
Logging
Keep records of admin access and sensitive operations for internal audit.
Pentests and patches
For high-stakes retailers, regular penetration testing campaigns complement vendor updates.
Secrets management
API keys and payment tokens should not be left lying around in shared spreadsheets: vaults and rotation.
Accessibility compliance
Standards such as WCAG guide contrasts, visible focus, and text alternatives: a growing requirement for high-traffic sites, certain public-sector orders, and inclusive brand image on an international scale over the long term.
Integrations, API and app marketplace
It is rare for a store not to connect at least one email tool, an ERP, a helpdesk or a BI tool. APIs and webhooks make it possible to synchronize orders, inventory, and customers. E-commerce automation relies on these flows.
iPaaS and connectors
Zapier, Make, or dedicated middleware speed up prototypes; high volumes require more robust pipelines.
Data quality
An API does not fix a poorly named SKU upstream: catalog governance before integration.
API versioning
Platform updates can break connectors: monitor changelogs and test environments.
Total cost
App subscriptions + technical time: recurring budget often underestimated in the business plan.
Custom fields and metadata
Store specific attributes (serial number, end-of-series date) for search or after-sales support: often via metafields or auxiliary tables.
Sandbox
Test environment to validate a new app before production: essential as soon as the catalog is critical.
Multi-store
Distinct brands or subsidiaries with partial catalogs: the separation functionality must be considered from the data architecture stage.
Platforms, headless, and personalization scope
SaaS solutions provide a broad functional foundation and continuous updates. The headless approach decouples front end and back end for bespoke experiences at the cost of greater integration complexity.
Shopify and apps
The extension ecosystem covers most common use cases; check theme compatibility and performance.
Marketplace vs store
Features are not interchangeable between a proprietary store and a marketplace: see the “e-commerce or marketplace” comparison on the blog.
Business scope
A feature “standard elsewhere” may require development on your current stack: estimate it before promising it internally.
Scalability
Moving from a basic plan to advanced features (multi-store, B2B) may require migration or a partial redesign.
Orders and order management
For details on OMS and advanced statuses, see the “e-commerce order management” guide on the Qstomy blog.
Support use cases
“Where is my discount?”, “Can I change the address?”: recurrent intents that self-service does not always cover clearly.
Brand alignment
The chatbot’s tone must follow your editorial guidelines, just like the main site.
Qstomy: conversational layer on top of core features
The features listed above do not replace conversation when the customer is lost, in a hurry, or mobile-first. Qstomy adds contextualized answers about orders, products, and policies, with escalation to a human.
Consistency with the site
The chatbot must repeat the same rules as the legal pages and checkout: content to keep in sync.
Measurement
Reducing repetitive tickets frees up time for complex incidents related to logistics or payment.
Analytics complement
Frequent questions in chat signal functional friction to fix in the product or funnel.
AI and limitations
For the general positioning of a conversational assistant, see the article «why an AI chatbot for e-commerce» on the blog; for site metrics, cross-reference with your analytics stack.
Competitive benchmarking
Analyzing the journeys of comparable brands gives ideas, but copying a feature without the associated back end often leads to a frustrating half-measure.
UX debt
A feature that is poorly integrated visually can be ignored by customers: design and wording matter just as much as the button itself.
Platform monitoring
Quarterly vendor release notes can make a paid app obsolete: keep an eye on native offerings to streamline costs.
Enzo
April 8, 2026
