Ecommerce / Project preparation
How to prepare for an ecommerce website project.
You do not need a finished specification. You do need a truthful picture of the catalog, operations, customers, systems, and decisions.
Explain why the store needs to change
Describe the current situation, priority customers, products, markets, and the most important action the new site must support. Separate known problems from preferred solutions. “Customers cannot compare variants” is more useful than “we need a configurator” because the studio can assess several ways to solve it.
Share available evidence such as customer questions, support issues, analytics, search data, abandoned journeys, or operational bottlenecks. Do not manufacture certainty where the data is incomplete.
Prepare a representative view of the catalog and operations
Provide product types, variants, attributes, pricing rules, inventory sources, collections, bundles, subscriptions, and a sample of actual product data. Describe markets, currencies, taxes, payment methods, shipping rules, fulfillment, returns, and customer service.
Flag difficult cases: made-to-order products, split shipments, restricted regions, wholesale pricing, preorders, or products that require consultation. These often affect platform and design decisions early.
List every system the storefront must exchange information with
- Commerce: current platform, theme, applications, and custom code.
- Operations: inventory, ERP, fulfillment, shipping, tax, and accounting.
- Growth: analytics, consent, email, CRM, reviews, feeds, and advertising.
- Content: product copy, imagery, video, policies, guides, and translations.
- Access: domain, DNS, platform, repository, analytics, and vendor accounts.
Record which system owns each important field. The requirements guide explains what an ecommerce website should include across the full journey.
Make the project constraints visible
Name the decision-maker, reviewers, subject experts, content owners, and technical contacts. State the available budget range, target window, immovable events, procurement rules, and internal availability. If the current store must remain live, explain release restrictions.
A good discovery process resolves open decisions. Accurate source material and clear responsibility are more valuable than a long specification built on assumptions.
Before requesting estimates, review the factors that shape ecommerce website cost and decide which responsibilities your team can genuinely own.
Prepare the conversation
Ready to discuss the ecommerce project?
Send the current URL and a concise account of the products, operations, customers, and problem. Northform can help define the remaining scope.
Discuss your ecommerce project Explore ecommerce website design →