When a business gets ready to build an ecommerce website, it is tempting to start from a feature list: product management, members, a cart, payments, shipping, coupons, inventory, reports… But the real question is not “how many features can an ecommerce site hold?” It is which features let the business complete its actual sales process.
A typical retail store may only need customers to pick products, add them to a cart, and pay. B2B, printing, manufacturing, or custom products can also involve product variants, special pricing, quote requests and quotes, online design, file uploads, order review, and integration with business systems.
So the sensible way to plan ecommerce features is not to build everything at once, but to confirm first:
How products are sold → how customers buy → how prices are set → how orders are handled → how the business runs afterward
Then decide which features you actually need based on that sales flow.
Key takeaways
- The core of an ecommerce website is a complete online sales process.
- Product variants and pricing logic directly affect how complex the system becomes.
- Payments, shipping, e-invoices, and order management should be planned together from the start.
- B2B ecommerce may need business accounts, dedicated pricing, quote requests and quotes, and permission management.
- Printing and custom products can use online design to connect design, orders, and production.
- Systems such as ERP, CRM, and POS don’t necessarily need to be integrated in the first phase.
- Finish the core sales process first, then expand step by step based on real operational needs.
- More features is not better. What matters most is features that genuinely support the business process.
What basic features does an ecommerce website need?
The basic features of an ecommerce website fall into five groups: product management, cart and checkout, payments, shipping and invoices, members, and back-office order management.
These five are the core shopping website features that let customers complete a purchase. Add other features based on your products and customers.

A complete ecommerce website should at least support the basic sales flow from browsing products to placing an order.
At its simplest, it looks like this:
Product → variant selection → cart → checkout → payment → delivery → order management
So the core features commonly found on an ecommerce website include:
- Product and category management
- Product variants and pricing
- Cart
- Checkout flow
- Member system
- Payments
- Shipping
- E-invoices
- Order management
- Inventory management
- Order and system notifications
- Basic marketing features
- SEO and data tracking
Together, these features make up a basic online sales system.
But not every business needs exactly the same features.
A brand selling ordinary retail goods may use fixed prices and go straight to checkout. Printing or custom products may require choosing size, material, quantity, and finishing first, with the system calculating the price. A B2B business may even need a quote request, a quote, and manual confirmation before an order is placed.
So what really matters is not checking:
“Does the site have a cart?”
But going a step further and checking:
“Does the whole sales process before and after the cart match how the business actually sells?”
This is the most important starting point when a business plans its ecommerce features.
Further resources: WooCommerce official documentation, What features does a business website need?, How to do website SEO
What features do product and variant management need?
At minimum, product management should let you list products and set variants, prices, and stock.
The more variants you have, such as size, material, and quantity all affecting price, the more the system needs to handle variant combinations and pricing rules.

Products are among the most central data on an ecommerce website, but product structures can differ enormously from one business to another.
A typical ecommerce website needs at least:
- Product name
- Product images
- Product description
- Product category
- Product price
- Product variants
- Product inventory
- Publishing and unpublishing products
- SEO settings
For ordinary retail products, these features usually cover the basics.
When the products themselves are more complex, you need to plan how variants and prices relate to each other.
Products with multiple variants
For example, a piece of clothing might have:
Color × size
But a printed or custom product might become:
Size × material × quantity × finishing × printing method
Different variant combinations can lead to different prices, different inventory, and even different available options.
So a business should check whether the system can handle:
- Multi-level product variants
- Prices per variant
- Inventory per variant
- Restrictions between variant choices
- Variant images
- Large numbers of variant combinations
At this point, “supports product variants” is no longer enough. What you really need to confirm is whether the system can express the business’s actual product logic.
Product prices and pricing methods
An ordinary product usually has one fixed price, but business ecommerce may involve many more pricing models.
For example:
- Fixed prices
- Variant surcharges
- Quantity tier pricing
- Member pricing
- Distributor pricing
- Customer-specific pricing
- Dynamic pricing
- Quotes after a quote request
Take printed products: the price may depend on size, paper, printing method, finishing, and quantity all at once.
In that case the price is not a single number stored on the product, but a set of pricing rules.
So if your products have special pricing logic, sort it out early in planning, rather than discovering after launch that a standard product price model can’t support it.
Product and inventory management
If products have physical stock, you also need to consider:
- Real-time inventory
- Safety stock
- Out-of-stock status
- Pre-orders
- Inventory per variant
- Inventory movements
- Inventory across multiple warehouses or stores
If the business runs both a website and physical stores, it may also need to consider POS and inventory sync.
But not every product needs traditional inventory management.
For printed or custom products made after an order comes in, what you really need to manage may not be “how many items are left,” but orders, production status, and material requirements.
So product features should still be planned around the actual business model, rather than copying how ordinary retail ecommerce does it.
What features do the cart and checkout flow need?
The cart should confirm variants and totals. Checkout should collect details and let customers choose payment and delivery.
If an order needs a file check or price confirmation first, checkout should support “submit now, pay after confirmation.”

Once products and variants are settled, the next step is letting customers complete their purchase smoothly.
The most common ecommerce flow is:
Choose product and variant → add to cart → review items → enter details → choose payment and delivery → complete the order
It looks simple, but the checkout flow directly affects whether customers can finish the transaction. So the point of planning is not that more steps make it more complete, but letting customers confirm the necessary information with as little friction as possible.
Cart features
A basic cart usually needs to support:
- Reviewing products and variants
- Adjusting quantities
- Removing items
- Item amounts
- Discounts
- Shipping fees
- Order total
If products have more complex variants, the cart should also let customers clearly see exactly what they selected.
For a printed product, for example, the cart can’t just show “Business cards × 1.” It may need to show:
Business cards / double-sided color / 250g coated card / matte laminate / 500 cards
That lets customers check the full specification once more before paying, lowering the risk of ordering the wrong thing.
Checkout flow
Checkout usually collects the information needed to complete the order, such as:
- Buyer details
- Recipient details
- Invoice information
- Delivery method
- Payment method
- Discount code
- Order notes
Businesses should avoid adding too many non-essential fields at checkout just to collect data.
If a piece of information doesn’t affect payment, delivery, or later order handling, consider whether you really need to ask customers for it at checkout.
Member checkout and guest checkout
Whether customers must register as members first also affects the checkout flow.
If the business relies heavily on membership, repeat purchases, and customer tiers, checkout after login can be worth more.
But if the main goal is to lower the barrier to a first purchase, you can consider guest checkout, so customers can buy without completing a full registration first.
The real deciding factor is still the business model. Not every ecommerce site has to take the same approach.
Discount and promotion rules
If the business runs promotions, the cart and checkout may also need to handle:
- Discount codes
- Spend-threshold discounts
- Free shipping over a threshold
- Discounts on specific products
- Member-only offers
- Bundle offers
- Campaign-period pricing
The more promotion rules you have, the more you need to watch whether different offers can be combined, and in what order discounts are calculated.
Otherwise the price shown on the storefront can easily differ from the actual order amount.
Not every order has to be paid immediately
A typical B2C store wants customers to pay right after checkout, but business transactions don’t always work that way.
B2B, printing, or custom products, for example, may require:
Submit order → confirm specs/files → staff review → confirm final price → customer pays
Some transactions even start with a quote request, and only then is it decided whether a formal order is placed.
So when planning checkout, first confirm:
“When the customer clicks submit, does this record represent an order, a quote request, or a transaction awaiting confirmation?”
Define that status clearly, and the payment, notification, and order management steps that follow won’t get muddled.
Further reading: Shopping website design: 7 essentials from product page to checkout
How should you plan payments, shipping, and e-invoices?
Plan payments, shipping, and e-invoices together from the start, because all three are tied to the order.
Find out which payment and delivery methods your customers use most, then decide which services to connect.
If an ecommerce website needs to complete transactions online, payments, shipping, and e-invoices are usually essential basic services.
But the website mostly doesn’t handle these itself. They are integrated with third-party providers, so planning means confirming not just the features, but also the providers, fees, and actual operating procedures.
Payment features
Common payment methods may include:
- Credit cards
- ATM / virtual account transfers
- Mobile payments
- Convenience store payment codes
- Cash on delivery
- Bank transfers
A business doesn’t need to adopt every method just to offer “lots of payment options.”
Decide which payment methods you really need to offer based on your main customers and transaction amounts.
For example, everyday B2C retail and high-value B2B orders may suit different payment methods.
Shipping features
When selling physical products, you usually also need to handle:
- Home delivery
- Convenience store pickup
- In-store pickup
- Shipping fee calculation
- Free shipping thresholds
- Delivery areas
- Shipment status
- Tracking numbers
If products have special sizes, weights, or delivery conditions, also confirm whether the platform can handle different shipping rules for different products.
So shipping isn’t just “which carrier to integrate.” You also need to confirm that the system can correctly express how the business actually ships.
E-invoices
If the website needs to issue e-invoices, plan them as part of the sales flow too.
For example, you need to confirm:
- Duplicate / triplicate invoices
- Tax ID number and company name
- Invoice carriers
- Invoice donation
- When the invoice is issued
- Handling cancellations and allowances
For B2B ecommerce, tax ID numbers, company details, and the invoicing process are especially important.
So it’s best not to leave payments, shipping, and e-invoices until after the website is built. Confirm them together at the sales flow design stage.
What features do member and customer management need?
The key question for member features is whether you give different prices and buying conditions to different customers.
Basic accounts are enough for most retail. B2B customers often need customer-specific pricing and several user accounts under one company.

The purpose of a member system isn’t just letting customers create accounts. It turns each transaction, step by step, into a customer relationship you can keep building.
A typical B2C store may focus mainly on registration, order history, and offers. For B2B or business ecommerce, a member account may also represent a different customer identity, pricing terms, and transaction permissions.
So before planning member features, first confirm:
Does the business only need to identify “who this customer is,” or does it need to offer different terms to different customers?
Basic member features
Member features common on ecommerce sites include:
- Member registration and login
- Profile management
- Shipping addresses
- Order history
- Order status lookup
- Saving frequently used details
- Password and account management
- Marketing notification settings
These features save returning customers from re-entering their details, and let customers look up their past transactions themselves.
Member tiers and offers
If the business wants to cultivate members, it can go further and set up:
- Member tiers
- Member-only discounts
- Coupons
- Points
- Spend-threshold offers
- Birthday offers
- Campaign eligibility by tier
But a more complex membership program isn’t necessarily better.
If the business has no clear membership strategy yet, building lots of tiers, points, and offer rules from the start only adds operational and system management costs.
Confirm which membership mechanisms you’ll actually use first, then decide which features you need.
B2B customer management
The member system for B2B ecommerce is usually more complex than for consumer ecommerce.
That’s because the same product may come with different terms for different business customers, such as:
- Customer-specific pricing
- Distributor pricing
- Pricing by member tier
- Minimum order quantities
- Exclusive products
- Different delivery methods
- Purchasing permissions
- Quote request and quote history
So in B2B ecommerce, a member account may really be more than a “member.” It may be a business customer identity.
This is one of the common differences between an ordinary shopping site and a business ecommerce system.
One company may have several users
More advanced B2B scenarios may also look like this:
One company → several buyers → different permissions
For example, buyers can create orders, but orders above a certain amount need a manager’s approval; or different departments can only buy specified products.
In that case you may need:
- Business accounts
- Sub-accounts
- User roles
- Purchasing permissions
- Order approval
- Department management
But these features don’t necessarily need to be introduced in the first phase. Decide based on the business’s actual sales process.
What features do back-office order and operations management need?
The back office should show your team where each order is and who handles the next step.
Order management, status flows, automatic notifications, permissions, and reports are the five most used back-office features.

The storefront answers “how do customers buy?” The back office has to answer:
“Once a customer places an order, how does the company get that order done?”
If you only perfect the storefront shopping flow without planning how orders are handled afterward, you may still end up sorting data by hand.
So an ecommerce website isn’t just a shopping site. It should also be a transaction management system that supports day-to-day operations.
Order management
Basic order management usually needs to include:
- Order number
- Customer details
- Products and variants
- Order amount
- Payment status
- Delivery status
- Invoice status
- Order notes
- Order creation time
- Order status
Administrators can search, filter, and view orders in the back office to see which orders currently need handling.
Order status and handling flow
Order flows can differ from business to business.
- Typical retail ecommerce might be: paid → preparing → shipped → completed
- Custom products might be: order placed → file check → design approval → production → shipped → completed
- B2B orders might be: quote request → quote → customer confirmation → order placed → payment → shipped
So order statuses should ideally reflect the business’s real handling process, rather than simply applying a fixed set of ecommerce statuses.
Automatic notifications
When an order’s status changes, the system can automatically notify the people involved.
For example:
- Order placed notification
- Payment completed notification
- Order confirmed notification
- Shipping notification
- Order cancellation notification
- New order notification for administrators
Depending on the business’s needs, it may also integrate email, SMS, LINE, or other notification channels.
The value of this automation isn’t only a better customer experience. It also cuts down on customer service repeatedly answering “Where is my order now?”
Admin permissions
When more than one person manages the website, you also need to consider which data each person can work with.
For example:
- Website administrators
- Product managers
- Order staff
- Customer service staff
- Marketing staff
- Store staff
Well-designed permissions reduce mistakes, and keep employees from accessing customer or operational data they don’t need.
Operations reports
The ecommerce back office should also help the business keep track of basic operations, such as:
- Number of orders
- Sales revenue
- Average order value
- Top-selling products
- Customer purchase history
- Order status
- Product sales performance
Which data you really need to track should still come back to the business’s operating model.
The point of an ecommerce back office isn’t to offer as many charts as possible, but to let managers quickly see:
What is happening right now, and what needs to be dealt with.
What marketing and data features does an ecommerce website need?
Marketing and data features bring in visitors and show which products and ads work.
Start with SEO settings, GA4, and conversion tracking. Add coupons and member marketing later.
Once the sales features are in place, an ecommerce website also needs to consider where customers come from, which products actually drive sales, and how to get existing customers to buy again.
So marketing and data capabilities should be part of the plan from the start of the build, not patched in after launch.
Common features include:
- SEO settings
- GA4
- Google Tag Manager
- Ad conversion tracking
- Product structured data
- Coupons and promotions
- Member marketing
- EDM or message notifications
- Remarketing data
- Product and order performance analysis
The most basic of these is recording key sales events correctly, for example:
View product → add to cart → begin checkout → complete purchase
Only then can the business work out whether the problem lies in insufficient traffic, products that don’t appeal enough, cart abandonment, or the checkout flow.
So the data features of an ecommerce website aren’t simply “installing GA4.” They mean setting up tracking that lets you understand the full sales funnel.
Why do custom products need online design features?
Custom products need print-ready content from the customer. Online design lets customers do that step on your website.
This cuts down on file back-and-forth and revisions, and the artwork is linked to the order.

In a typical ecommerce flow, customers choose a product and its variants and go straight to checkout. But for printing, promotional gifts, custom apparel, and similar products, there is often one more important step:
The customer has to provide design content that can actually be produced.
Without online design features, the usual process can look like this:
Choose product → ask about specs → send artwork via LINE/email → manual check → revise → proof again → confirm, then order or produce
As order volume grows, collecting artwork, revising, proofing, and organizing files can become a major source of manual work.
So for certain custom products, online design isn’t just adding an editor to the website. It brings the process that used to be scattered across customer service, design, and orders into the ecommerce website.
What is an online design editor?
An online design editor lets customers design the product directly on the website, for example:
- Choosing a design template
- Editing text
- Uploading images
- Adjusting the position of images and text
- Viewing the layout in real time
- Previewing how the finished product will look
- Saving their own designs
For example, when buying business cards, a customer can first choose the card size, paper, and finishing, then apply a template provided by the business and edit their name, job title, phone number, and logo.
Once finished, the design can be linked directly to the product variants and the order, with no need to send files separately via LINE or email.
The whole process can become:
Choose product → choose variants → design online → preview and confirm → add to cart → place order
What problems can online design solve?
The biggest value of online design isn’t replacing professional design software. It’s handling large volumes of custom requests that follow fixed layouts and repetitive processes.
For products like business cards, stickers, invitations, and promotional gifts, many orders really only change:
- Name
- Contact details
- Logo
- Images
- Colors
- Small amounts of layout content
If every order requires customer service to receive the details and then pass them to a designer to edit and send back for confirmation, manual work grows along with the number of orders.
With online design, customers can make the edits that suit standardization themselves, reducing the operating costs of:
- Collecting artwork manually
- Repeated revisions
- Customer service communication
- Organizing files
- Matching artwork to orders
All of these add up to operating costs.
Mockup product previews
Beyond flat design content, some custom products can also add Mockup previews.
For example, after finishing a design, the customer doesn’t just see a flat image. They can preview roughly how the design will look applied to:
- Business cards
- Packaging
- Paper bags
- Mugs
- Clothing
- Promotional gifts
once it’s produced.
This helps customers check the finished product more intuitively before ordering, and lowers the communication costs that come from “the design on screen not matching what they imagined the product would be.”
Artwork should be linked directly to the order
A truly complete online design process can’t stop at “the customer can draw.”
After the design is finished, the system also needs to know:
Which product, which set of variants, and which order this design belongs to.
So online design should be connected to product and order data.
For example, a single printing order can include all of the following:
Product: business cards Specs: 90 × 54 mm / double-sided color / coated card / 500 cards Artwork: customer-approved version Order: #202610001
When back-office staff handle the order, they can find the matching design data directly, without hunting for files in email, LINE, or different folders.
From online design to the production process
For printing ecommerce, the further value of online design is connecting the storefront design process with the back-end production process.
The ideal flow can look like this:
Product variants → online design → Mockup preview → customer confirmation → order → artwork linked to the order → PDF production file output → received by production
If the business already has its own production process, it can go further and use file export, FTP, or other system integrations to hand confirmed production data to the next stage of work.
This kind of process is usually called Web-to-Print.
For printing companies, what it really improves isn’t a single website feature. It gradually brings together:
Order intake → specs → design → proofing → order → production file
into one digital process.
That’s why printing ecommerce has clearly different needs from an ordinary shopping site.
How can regular orders, B2B ordering, and custom quote requests work together?

Many businesses have three kinds of customers: people buying standard products, business customers who reorder, and customers who need custom products.
All three flows can run on one website. They share one product back office and one order history, and the product or customer decides which path to take.
Standard products: order and pay right away
Standard products have a fixed price. Customers pick variants, add to cart, and pay.
Choose product → choose variants → add to cart → pay → ship
B2B ordering: log in and reorder at customer-specific prices
After logging in, business customers see their own prices and the products they can order.
One company can have several user accounts. For example, a buyer and a manager each log in, and all orders stay under the same company.
Frequent items can be reordered from past orders, with no need to ask for a price each time.
Log in to the company account → see your prices → choose products and quantities → submit the order
Custom quote requests: send specs, then turn the confirmed quote into an order
Some products can only be priced after you see the specs, quantity, or files, so a fixed price doesn’t work.
Customers fill in their needs and send a quote request on the website. After sales sends a quote and the customer confirms, the request becomes an order with no retyping.
Fill in specs → send a quote request → sales sends a quote → customer confirms → order created
How do the three flows fit on one website?
Three questions decide the path:
- Can this product show a fixed price? If yes, use the regular order flow. If not, use a quote request.
- Is this a business customer? If yes, show their prices after login.
- After the order comes in, does it ship right away, or does it need a file check or confirmation first?
Here’s how the three flows differ:
- Regular orders: for general customers. Fixed prices, paid at checkout, shipped directly.
- B2B ordering: for business customers. Prices set per customer, several accounts per company, shipped per order.
- Custom quote requests: for custom needs. Prices quoted by sales, paid after confirmation, produced to the confirmed specs.
Related reading: Print quotation system guide, What is a print order system?
What advanced features does business ecommerce have?
Common advanced features in business ecommerce are dynamic pricing, quote requests, B2B sales, special order flows, and system integration.
You don’t need all of them. It depends on how you sell and who your customers are.

When a business’s way of selling goes beyond the standard “choose product → add to cart → pay” flow, it may need more advanced business ecommerce features.
Common needs include:
Complex product variants and dynamic pricing
A product’s price may be determined by size, material, quantity, finishing, or other conditions together.
In that case the system has to handle a set of pricing logic, not just a product’s selling price.
Quote request and quote process
For products that can’t show a fixed price, collect needs with a quote request, then turn the confirmed quote into an order. See “How can regular orders, B2B ordering, and custom quote requests work together?” above for the full flow.
B2B and distributor sales
Business customers need customer-specific prices, exclusive products, minimum order quantities, and several user accounts per company. See “How can regular orders, B2B ordering, and custom quote requests work together?” above.
Special order flows
For some businesses, an order still has to go through these steps after it’s placed:
- Manual confirmation
- Design approval
- File review
- Manager approval
- Production
- Shipping in batches
In that case the order system needs to be designed around the business’s actual process, rather than forcing the business to switch to fixed ecommerce order statuses.
Integration with ERP, CRM, POS, and other systems
Once the ecommerce website becomes one of the business’s main sales channels, its data may also need to be exchanged with existing systems.
For example:
- ERP
- CRM
- POS
- Inventory systems
- Logistics systems
- Accounting or invoicing systems
- Internal business systems
But system integration shouldn’t all be built at the start just because “we might use it later.”
A more sensible approach is to build the core sales process first, then confirm which data really needs to sync across systems, and only then decide the scope of integration.
That keeps the business from investing a large budget in the first phase only to end up with features it rarely uses in day-to-day operations.
Further reading: How much does it cost to build an online store?
Which features don’t have to be built in the first phase?
In phase 1, finish the core flow that closes sales. Add other features after launch, based on real needs.
Member tiers, distributor systems, and ERP integration can usually wait for phase 2 or 3.
When planning an ecommerce website, it’s easy for a business to put every feature it “might need in the future” into the first phase.
For example:
- Member tiers
- Points programs
- Distributor systems
- Complex promotion rules
- Multiple languages
- Multiple currencies
- ERP/CRM integration
- POS integration
- Complex approval flows
- Lots of automation
There’s nothing wrong with these features in themselves. But if current transaction volume, operating processes, or the business model don’t actually call for them yet, building them too early can add project costs and make ongoing maintenance more complex.
So a more sensible approach is to divide requirements into:
Phase 1: Complete the core sales process
Prioritize the requirements without which the business can’t operate normally.
For a typical ecommerce store, that might be:
Products → variants → cart → payments and shipping → orders
For printing ecommerce, it might be:
Products → variant pricing → online design / file upload → order → artwork and order → production
For B2B ecommerce, it might be:
Products → business customers → quote request / quote → order → follow-up handling
The goal of the first phase should be getting the most important sales process genuinely working, not finishing every feature you can think of at once.
Phase 2: Improve operational efficiency
Once the website is up and running, add features based on the problems you actually run into.
For example:
- Automatic order notifications
- Member tiers
- Customer-specific pricing
- Batch processing
- Operations reports
- More complete inventory management
- Automating internal processes
The value of these features usually comes from operational problems that have already happened, so their return on investment is easier to judge than needs predicted at the start of a project.
Phase 3: System integration and scaling
When ecommerce starts generating steady orders and needs to work with the business’s other systems, go further and assess:
- ERP
- CRM
- POS
- Warehousing
- Production systems
- Logistics systems
- Other internal systems
This approach doesn’t ignore future needs. Instead:
The architecture keeps room to expand, but features are introduced gradually as real needs arise.
This usually makes costs easier to control than building a massive system on day one, and it fits better with how the business actually grows.
How should a business organize its ecommerce feature requirements?
To organize your feature needs, answer seven questions: how products are sold, how prices are set, who the customers are, how they buy, how orders are handled, where manual work piles up, and which systems must connect.
Once you answer these, the feature list is usually clear.
If you’re getting ready to look for an ecommerce platform or a website development company, you don’t need to know every technical specification up front.
What matters more is sorting out your own business process first.
You can start with the following seven questions.
1. How are products sold?
First, work out:
- What types of products are there?
- Do products have variants?
- How complex are the variants?
- Is customization needed?
- Are file uploads or online design needed?
- Is there inventory?
2. How are prices set?
Confirm whether products use:
- Fixed prices
- Variant surcharges
- Quantity-based pricing
- Dynamic pricing
- Member pricing
- Distributor pricing
- Customer-specific pricing
- Quotes after a quote request
Pricing logic usually has a direct impact on how complex the ecommerce system becomes.
3. Who are the customers?
Confirm whether your main buyers are:
- Consumers
- Business customers
- Distributors
- Members
- A mixed customer base
Also confirm whether different customers have different products, prices, and terms.
4. How do customers complete a purchase?
Write out the actual flow, for example:
Choose product → choose variants → add to cart → pay
Or:
Choose product → choose variants → design online → preview → order → production
Or it might be:
Submit requirements → quote request → quote → confirmation → order → payment
This step is usually more important than jumping straight to a feature list.
5. Once an order is placed, how does the company handle it?
Next, map out the internal process:
Once an order comes in, who is responsible? What happens next?
This may include confirming payment, reviewing files, preparing stock, production, shipping, issuing invoices, and customer service.
6. Which tasks currently take the most manual work?
For example:
- Repeated quoting
- Answering questions about product prices
- Collecting specs
- Receiving artwork
- Revising artwork by hand
- Searching for order files
- Creating orders
- Notifying customers
- Re-entering data
These are often the processes most worth digitizing first.
7. Which systems really need to be integrated?
Only at the end, confirm whether you already use:
- ERP
- CRM
- POS
- Inventory systems
- Production systems
- Logistics systems
And which data really needs to sync with the ecommerce website.
Once this groundwork is done, turning the requirements into website features is usually more accurate than ticking boxes on a ready-made “ecommerce feature list.”
Ecommerce website features: frequently asked questions
What are the most basic features an ecommerce website needs?▼
A typical ecommerce site needs at least product management, product variants, a cart, checkout, payments, shipping, order management, and basic website and data management features.
If membership programs, B2B, custom products, or special sales processes are involved, you’ll need to add the corresponding features.
Does an ecommerce website have to have a member system?▼
Not necessarily.
If the business mainly needs customers to complete one-off purchases quickly, you can consider guest checkout. If you need repeat purchases, member offers, customer tiers, or B2B transactions, a member system becomes more important.
Does an ecommerce website have to integrate with an ERP?
More features isn’t better. What matters is completing the business’s sales process
When planning an ecommerce website, what really matters isn’t comparing which system has the most features, but confirming whether those features can support the business’s actual products, customers, and sales process.
A typical business may only need standard products, a cart, payments and shipping, and order management. A B2B business may need quote requests and quotes, customer tiers, and dedicated pricing. Printing and custom products may go further and need multi-variant pricing, online design, artwork management, and production file output.
So before building an ecommerce website, a business should first sort out its own sales process, then decide which features it needs now and which can be added later.
Not sure which features your ecommerce website needs first? Book a free consultation and we will help you plan a build order based on your products and sales flow.




