01Product information
Size, colour and quantity
Define variants, images, stock and availability rules around what you sell.
Websites and ecommerce
From the first category to an order you can manage. Connect storefront design with your products, selling rules, payment and fulfilment, not appearance alone.
Licensed packing illustration, not a Snuhy warehouse or customer order.
01 / Websites and ecommerce
A shopping journey and an operating workflow.
Define what is sold, how orders are fulfilled and who manages each step before choosing technology and features.
A store has two connected experiences: customers need to find, understand and order products, while the business needs to maintain its catalogue and manage orders. Begin with product types, variants, pricing, inventory and selling regions. Define categories, filters, product information and ordering steps. Check provider compatibility and activation requirements before promising payment or delivery integrations. Build the agreed scope and safely test availability, missing information, failed steps and status notices. Handover includes administration guidance and named operating responsibilities. Marketing, maintenance, external fees and migration are explicit proposal items, not assumptions.
- 01Catalogue and discovery
- Categories, subcategories, variants and filters with information and images that help customers compare.
- 02Orders and integrations
- Required details, costs, available payment and delivery options, with provider limits and activation requirements.
- 03Management and handover
- Products, stock, order states, permissions and operating guidance with named responsibilities.
Plan the order before drawing the buy button.
- 01
Map products and operations
Review product types, variants, stock, markets, currencies, languages and fulfilment. Assess data and integrations before selecting the solution.
- 02
Structure catalogue and ordering
Define categories, filters, product pages, cart, required details and visible costs. Approve design, policies and content before development.
- 03
Build, connect and verify
Implement agreed management, features and integrations. Safely test success, errors, duplicates and permissions with authorised methods.
- 04
Launch and hand over
Review deployment, links and settings. Explain catalogue updates and order management; assign renewal, support, backup and transition responsibilities.
The product changes what follows an order.
Choose a type to explore operating decisions. This illustration does not add to cart, test payments or send anything.
02Order and status
Address and delivery cost
Coverage, charges and order states without hiding costs until the final step.
03Delivery and access
Preparation and shipping
Fulfilment responsibilities, delivery provider, follow-up and approved returns policy.
A store may combine both types. Subscriptions, bookings and special orders need an explicit scope, not assumed features.
Understand the operation behind the storefront.
- Who maintains products?
- Define fields, sections, permissions and training, with responsibility for accurate pricing, stock and content.
- When does status change?
- Review order, payment, delivery and cancellation states, authorised editors and the agreed activity record.
- What do outside providers need?
- Payment, delivery and extension accounts, licences, fees and provider approvals.
- How is the store handed over?
- Administration, backups, access, ownership, maintenance and transition plans as agreed.
A discoverable catalogue and understandable steps.
Links from categories to products support navigation and search understanding. Clear fields and errors support form usability. These are planning references, not ranking guarantees or certification.
Show us how you sell today.
A complete specification is not required. Start with sample product information and your current order process, then identify what is missing.
- Product types, approximate volume, variants and physical, digital or made-to-order delivery.
- Actual selling regions, languages, currencies, payment and delivery options.
- Existing store or product files, identity, photography, content and usage rights.
- Inventory or accounting integrations, target date and initial budget.
Before agreement
Hosted platform or custom development?
Choose around products, functionality, integrations, budget and operation. Explain constraints, fees and responsibilities rather than forcing one technology or promising any platform can do everything.
Are payment and shipping automatically included?
Specify providers and integration functions after compatibility checks. Account opening, activation, approvals and charges depend on provider terms. Account acceptance or regional availability is not guaranteed without verification.
Will products be entered for me?
Define product, variant and language counts, data sources and responsibility for entry and approval. Copywriting, photography and cleaning legacy files are separately defined work.
Can you migrate an existing store?
Review source access, data, links and integrations. Agree transferable data, verification, cutover and rollback. Handle customer and order data with appropriate authority; do not transfer sensitive payment information without a justified authorised need.
Will the store guarantee sales or rankings?
No. Review agreed usability and technical foundations; sales also depend on products, pricing, marketing and operation. Ongoing SEO, advertising and advanced analytics need separate scopes, with no invented forecasts.
What about maintenance, tax and returns?
Define support, renewals and backups. Tax, delivery and returns follow your business, markets and approved policies. Technical configuration is not legal or tax advice, and we do not invent commercial terms.
Plan your store from products to operation.
Tell us what you sell, to whom and how orders are fulfilled. Clarify catalogue, functionality, integrations, outputs and cost before starting.
Discuss your ecommerce projectAll Snuhy services