E-commerce
April 8, 2026
Under the term e-commerce features, we group all software capabilities that make online selling possible: displaying a catalog, managing a cart, processing a payment, tracking an order, administering prices and inventory, and connecting logistics and marketing tools. This is not a fixed list: depending on your model (B2C, B2B, marketplace, subscription), the relevant scope changes.
This Foundations guide sets out 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 Shopify integration as a reference ecosystem: menu names may differ, but the logic (product, variant, order, fulfillment) is largely shared across 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 gadgets before the foundations.
Technical teams appreciate clearly distinguishing business need (rule to apply) from solution (app A or B): the solution can change if the need is well 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.
Finance teams need accounting exports and cash receipt reconciliation: plan these exports within the scope from the tool-selection phase, not as a late addition.
Legal teams often validate legal notices, withdrawal rights, and proof of consent: involve them early to avoid blocking a commercial production launch at the last minute.
For brands that also sell in physical stores, unified inventory and seamless journey features (availability lookup, reservation) connect digital to the point of sale: a cross-functional IT and retail initiative.
Summary
Definition: front-end and back-end functionality and integrations
An e-commerce feature can be viewed at three levels: front office (what the visitor sees), back office (what the team configures), interconnections (ERP, carriers, CRM, email tools). A single capability like “one-click purchase” 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 a product page can wait if your traffic or catalog does not justify it.
Omnichannel consistency
Features must be aligned across site, email, and ads: displaying incorrect stock breaks trust faster than the 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
Maintaining a register of enabled features and their business owner makes audits and hiring easier: a newcomer understands why a given module exists.
User testing
Observing real customers go through 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 pricing. Search and filters become critical once you have a few dozen references.
Variants and options
SKUs, barcodes, stock by variant: modeling determines what comes next (targeted promotions, warehouse sync). To go further: e-commerce product catalog.
Rich content
Reviews, Q&A, buying guides: all blocks that increase conversion but require moderation and updates.
SEO and listings
Tags, internal linking, pagination: listing features influence discoverability: see e-commerce SEO.
Merchandising
Highlighting, “new” badges, sorting by margin or stock: digital merchandising extends the commercial work of the physical store.
Accessibility and mobile
Text zoom features, contrast, keyboard navigation, and readability on small screens are not reserved for “institutional” websites: 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 capability.
Cart, checkout funnel and payment
The cart keeps line items, applies discounts and promo codes, calculates taxes and shipping fees. The checkout collects addresses, delivery choices, payment method, and legal consents.
Friction and conversion
Each extra field can reduce conversion: see cart abandonment; the checkout flow design is detailed in the guide dedicated to e-commerce website design.
Payment
Card, wallet, bank transfer, installment payment depending on country: the gateway must handle 3-D Secure, failures, and partial refunds.
B2B and quotes
Cart with hierarchical approval, net prices according to contract, deferred payment terms: extensions are often specific to the professional segment.
Recurrence
Subscriptions and recurring debits add failed payment management, upgrades, and a self-service portal.
Guest checkout
Allowing purchase without an account reduces friction but makes later retention more complex: a trade-off to document.
Persistent cart
Finding a cart on another device or after a reminder email increases the recovery rate: configure durations and privacy.
Dynamic shipping fees
Real-time calculation based on cart and destination avoids surprises on the last screen, the main reason for abandonment.
Customer account, orders and self-service
The customer area provides order history, parcel tracking, downloads (invoices), saved addresses, and wish lists. Return and after-sales service features reduce support tickets.
Authentication
Email / password, SSO, social login: each option has a security and compliance impact.
GDPR
Data export and deletion, marketing preferences: to be integrated from the design stage, not as an afterthought.
B2B Profile
Multiple users per company account, buyer / approver roles: features often missing from standard pure B2C commerce.
Transactional communication
Confirmation, shipment, and delivery emails and SMS: editable and customizable templates are part of the expected “functional” scope.
Warranty portal
Report a breakdown, attach proof of purchase, track an exchange: a journey often forgotten during the scoping phase, yet a major consumer of support resources.
Invoices and credit notes
Compliant PDF download, automatic sending to B2B customer accounting: strong expectations as soon as the average cart value increases.
Communication preferences
Preferred channel, follow-up frequency: features that connect to your CRM or email tool.
Merchant back office: products, inventory, prices, promotions
Administration allows you to create and update products, manage collections, launch promotional campaigns, and adjust stock manually or via synchronization. Validation workflows (draft, publication) prevent errors in production.
Pricing rules
Automatic discounts, codes, B2B catalog pricing, quantity tiers: complexity quickly grows with the number of channels.
Multi-stock
Warehouses, stores, partners: reserving the right stock for the right order is a structuring feature for omnichannel.
Permissions
Who can change prices or issue refunds? Admin roles limit operational risks.
Audit log
Tracking changes to prices or product sheets helps in the event of disputes or human error.
Imports and feeds
CSV import or PIM connector: the import feature must handle line-by-line errors and usable reports.
Scheduling
Publish a collection at a specific time for a coordinated launch with PR and social media.
Logistics and fulfillment seen as functional building blocks
Beyond the website, features include shipping profiles, labels, tracking, and sometimes 3PL integration. See the dedicated guide on fulfillment services.
Displayed promises
Lead times by area, economy vs express methods: 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 parcel is ready: a cross-functional operational chain.
Tracking numbers
Passing tracking information to the customer and to the account area reduces “where is my parcel” requests.
Returns management
Request portals, prepaid labels: to be linked to your returns policy (see also the Qstomy 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
Shipping only part of the line items and canceling the rest or putting them on hold: rules to clarify on the functional side to avoid double shipping charges.
Donors and gifts
Card message, gift wrapping, sender anonymity: options that make picking more complex but increase perceived value.
Marketing: acquisition, loyalty and content
Many platforms offer building blocks for discounts, codes, loyalty points, and sometimes blogs and landing pages. Advanced marketing often 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 spanning accounting and support.
Social commerce
Catalogs connected to social networks, native checkout: the scope extends beyond the owned site.
Personalization
History-based recommendations: useful, but must be calibrated with privacy and data quality in mind.
Multi-touch attribution
Understanding which channels contribute to a sale requires tracking capabilities and attribution models, often outside the native platform.
Promo consistency
A site discount + influencer code + cashback must be calculated without negative margin: stacking rules need testing.
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 are sometimes rudimentary in the commerce admin; a headless CMS coupled with the front end may better serve marketing teams.
UGC
Customer photos, video reviews: moderation and image rights should be planned before opening the public feed.
International, taxes shown and local compliance
Selling abroad adds currencies, translations, VAT or sales tax rules, address formats, and local payment methods. Some features are built in 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 by market if necessary.
Regulated markets
Alcohol, health, gambling: age or prescription verification features may be required.
Performance by region
CDN and regional hosting: the perceived “functionality” includes loading speed.
Prices shown incl. / excl. tax
Depending on the B2B or B2C audience and country, display obligations vary: configure views without manually duplicating the entire catalog.
Geographic restrictions
Block sales to certain countries for licensing or shipping reasons: cart and checkout filters must be tested exhaustively.
Localized legal content
Manufacturer notices, sorting pictograms, 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 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 provider SLA
Uptime, maintenance windows: to be read in the cloud or platform contract.
Fraud
Order scoring, blocklists: features often connected via apps or the payment provider.
Logging
Keep records of admin access and sensitive operations for internal auditing.
Pentests and patches
For brands with high stakes, regular penetration testing campaigns complement vendor updates.
Secrets management
API keys and payment tokens must not be left lying around in shared spreadsheets: vaults and rotation.
Accessibility compliance
Frameworks such as WCAG guide contrast, visible focus, and text alternatives: an increasing requirement for high-traffic sites, certain public procurements, and an inclusive brand image internationally over the long term.
Integrations, API and app marketplace
Rare is the store that does not connect at least one email tool, an ERP, a helpdesk, or a BI. 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 middlewares speed up prototypes; high volumes require more robust pipelines.
Data quality
An API does not fix an upstream poorly named SKU: catalog governance comes before integration.
API versioning
Platform updates can break connectors: monitor changelogs and test environments.
Total cost
App subscriptions + technical time: recurring budget is often underestimated in the business plan.
Custom fields and metadata
Store specific attributes (serial number, end-of-series date) for search or after-sales service: 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 feature must be planned from the data architecture stage.
Platforms, headless, and personalization scope
SaaS solutions deliver a broad functional foundation and continuous updates. The headless approach decouples front and back ends for tailored experiences, at the cost of higher 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 comparison “e-commerce or marketplace” on the blog.
Business scope
A feature that is “standard elsewhere” may require development on your current stack: estimate it before making internal promises.
Scalability
Moving from a basic plan to advanced features (multi-store, B2B) may require migration or a partial redesign.
Order and order management
For OMS details 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?”: recurring intents that self-service does not always cover clearly.
Brand alignment
The chatbot’s tone should follow your editorial guidelines just like the main site.
Qstomy: conversational layer on top of core features
The features listed above do not replace dialogue 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 be maintained in parallel.
Measurement
Reducing repetitive tickets frees up time for complex incidents related to logistics or payment.
Analytics complement
Frequently asked questions in chat indicate functional friction that should be fixed in the product or funnel.
AI and limits
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-check with your analytics stack.
Competitive benchmark
Analyzing journeys from comparable brands provides 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 as much as the button itself.
Platform monitoring
Vendors' quarterly release notes can make a paid app obsolete: keep track of the native offering to streamline costs.
Enzo
April 8, 2026
