Responsive storefront
A consistent, welcoming experience across desktop, tablet, and mobile.
Proposed scopePREPARED FOR SIMBIAT · DISCOVERY FOLLOW-UP
Proposed E-Commerce Website — Project Scope
Visual scope prepared following our initial discovery conversation.
AT A GLANCE
- Initial products
- ~15
- Product categories
- ~5
- Checkout approach
- Guest
- Project stage
- Scope review
Proposed direction. Final pricing follows scope confirmation.
This prototype is a visual project-scoping tool, not the final website.
The layout, imagery, wording, colors, technical architecture, integrations, and features may change after scope approval.
No real customer data or payments are processed by this prototype.
01
Project objective
Build a professional, secure, mobile-friendly e-commerce experience for approximately 15 initial African food products and snacks, with room for the catalog and content strategy to grow.
The aim is a clear, welcoming place to discover the business, understand the products, find cooking inspiration, and shop with confidence.
02
Proposed customer experience
A straightforward guest shopping journey. Select any step to preview its screen.
Recipe discovery
RecipesEducational contentRelevant products
Stories & education
BlogBusiness / educational contentStore discovery
03
Initial catalog assumptions
Approximately 15 products
Approximately 5 product categories
Product size variants where required
Dietary variants where required
Client supplies final product photos
Client supplies / approves product descriptions
Client supplies final prices
Client supplies shipping rules
Sample products and dietary labels illustrate possible configurations. They do not represent a confirmed inventory.
04
Included in proposed scope
These capabilities form the proposed starting point for discussion and pricing. Production integrations are represented visually here.
Home page
Introduce the business, collections, products, recipes, and stories.
Proposed scopeProduct catalog
An initial collection of approximately 15 products, with room to grow.
Proposed scopeProduct categories
Approximately five editable groups that make products easy to explore.
Proposed scopeProduct detail pages
Photography, descriptions, pricing, usage, and supporting information.
Proposed scopeProduct variants
Size and dietary options where applicable and approved.
Proposed scopeShopping cart
Add, review, adjust quantities, and remove selected items.
Proposed scopeCheckout experience
A clear guest flow for contact, delivery, and payment.
Proposed scopeThird-party payment integration
Proposed established provider; selection and setup to be confirmed.
Proposed scopeOrder confirmation
A clear post-purchase summary and expected next steps.
Proposed scopeRecipes
A recipe collection with ingredients, instructions, and relevant products.
Proposed scopeBlog
A separate home for education, sourcing stories, and business updates.
Proposed scopeContact form
A straightforward customer inquiry form; delivery integration to be confirmed.
Proposed scopeSearch
Help customers discover products, recipes, and articles.
Proposed scopeContent management capability
Routine product and content editing; the CMS is not yet selected.
Proposed scopeBasic technical SEO foundations
Page metadata, readable URLs, and appropriate indexability at launch.
Proposed scopeAnalytics foundations
An agreed approach to basic measurement and privacy choices.
Proposed scopeResponsive / mobile optimization
Readable content and usable forms and navigation on small screens.
Proposed scopeDeployment / setup
Launch setup and configuration on an approved hosting provider.
Proposed scopeSecurity best practices
Appropriate access controls and trusted providers for sensitive operations.
Proposed scopePayment provider, hosting provider, CMS, authentication approach, and analytics implementation are not finalized in this prototype. The prototype stack does not commit the production architecture.
05
A thoughtful approach to security
Handle less sensitive information. Rely on established providers.
The production implementation should minimize how much sensitive information the custom application handles directly.
Payment processing
Use an established third-party payment provider such as Stripe, subject to approval. Full card data should not be stored by the custom application.
Administrative access
Use established authentication and security practices for administrative access. The approach and provider remain to be confirmed.
Practical safeguards
Use appropriate security practices and trusted providers. Security cannot be represented as an absolute guarantee.
Customer privacy
Guest checkout is the default prototype flow. Customer accounts remain an open decision rather than a committed feature.
06
Content management
Everyday updates should be everyday work.
The production website is expected to support routine management of products, categories, recipes, and blog posts without requiring a developer for every ordinary content change. The content platform, administrative roles, and editing workflow will be agreed during scoping.
07
Client-provided materials
A checklist of materials needed to turn this neutral prototype into a store that feels like your business. Checkboxes are for this review session only.
08
Open items / decisions required
These decisions may affect the final project scope, timeline, and price.
- 01
Shipping regions
Which US states or other regions should the store serve?
- 02
Shipping calculation method
Flat rate, order value, weight, or another calculation?
- 03
Sales tax requirements
What tax requirements and calculation approach need to be supported?
- 04
Inventory tracking requirements
How should stock levels, low-stock alerts, and sold-out items work?
- 05
Guest checkout vs customer accounts
Is guest checkout sufficient initially, or are customer accounts needed?
- 06
Coupons / discount codes
Are promotions required at launch, and what rules should they follow?
- 07
Newsletter / email marketing
Is a mailing list required, and which service should connect to it?
- 08
Order management requirements
Who will manage orders, and which fulfillment and notification steps are needed?
- 09
Paid vs free recipes
Should all recipe content be freely available? Paid access is not assumed.
- 10
WhatsApp integration
Is a simple contact link enough, or is a deeper integration needed?
- 11
Final payment provider
Which established payment provider will be approved?
- 12
Hosting
Which hosting setup, ongoing costs, and support responsibilities are appropriate?
- 13
Required legal / policy pages
Which shipping, returns, privacy, and terms pages will the client supply?
- 14
Initial content entry
How many recipes and blog posts should be entered at launch?
- 15
Historical Shopify data
Does any historical customer or order data need to be migrated from Shopify?
09
Not included / not yet confirmed
The following capabilities should not automatically be assumed. Any additions need a separate scope discussion before they are included in pricing.
—Subscriptions
—Recurring payments
—Marketplace / multiple vendors
—Loyalty program
—Advanced customer accounts
—Wholesale portal
—Complex warehouse management
—Multi-currency
—Multi-language
—Native mobile app
—Advanced ERP integration
—Custom payment processing
—Shipping carrier API integrations
—Complex automated marketing
Scope Review
Please review the proposed pages, customer flow, and functionality. Features can be added, removed, or simplified before the project scope and price are finalized.