Online store end to end - JimmyNeuron concept

About the concept

JimmyNeuron built a concept platform for online stores - a full digital contour that shows how we assemble e-commerce end to end: design, UX, catalog, product card, configurator, cart, and a data layer for payment, delivery, and warehouse.

This is not a “we built a store for a client” case and not a commercial shop. It is our reference: UI/UX, filtered catalog, product card with SKU and price, compare, wishlist, mobile version, and readiness to connect PostgreSQL, payment gateways, and delivery services without rewriting the storefront.

Live prototype - jimmyneuron-forma.vercel.app: walk the buyer path from home to cart.

What we set out to solve

Many stores look good outside, but the configuration and price are clarified in chats with a manager
The catalog, product card, and cart must read one SKU model, or integrations break
Payment, delivery, and warehouse cannot be bolted on later; they need architecture from day one
The storefront must not be rewritten when acquiring or a new warehouse is connected

What the platform includes

E-commerce design and storefront

A home page with an offer and category navigation, a unified design system, and a mobile version. Not a catalog template from a site builder, but a cohesive branded e-commerce layer that can be adapted to your product range.

Catalog, filters, and product card

Section, material, configuration, search. A SKU grid with price, discount, and comparison. The product card has photos, description, specs, and configurations. Everything maps to one data model that the warehouse and CRM can later consume.

SKU configurator and live pricing

Using the Orbit sofa as an example: upholstery, legs, add-ons, configurations. The price and the ORB-SOF-... SKU code change with the selection, with no "message the manager and we will clarify the fabric." This shows how we build a complex product catalog.

Cart and integrations: payment, delivery, warehouse

Cart, favorites, comparison: the full buyer journey on the storefront. The data layer is separated from the UI, so the next step for a live store is PostgreSQL, acquiring (YooKassa, CloudPayments, and others), delivery services, and 1C/CRM, without rewriting the catalog and product card.

Gallery

JimmyNeuron · R&D E-commerce: R&D e-commerce platform concept - screenshot 1

JimmyNeuron · R&D E-commerce: R&D e-commerce platform concept - screenshot 2

JimmyNeuron · R&D E-commerce: R&D e-commerce platform concept - screenshot 3

JimmyNeuron · R&D E-commerce: R&D e-commerce platform concept - screenshot 4

JimmyNeuron · R&D E-commerce: R&D e-commerce platform concept - screenshot 5

JimmyNeuron · R&D E-commerce: R&D e-commerce platform concept - screenshot 6

How it works

User scenario

Opens the home page and understands the range and the store's logic
Goes to the catalog and filters by category and parameters
On the product card, builds a configuration and sees the SKU and price
Compares, saves to favorites, or adds to cart

Team / admin scenario

The catalog, product card, and cart read one SKU model
Configuration rules and prices live in data, not in website text
Payment, delivery, and warehouse connect through an API layer without changing the storefront

Technology

Format: e-commerce concept platform
Storefront: catalog · product card · cart
Data: SKU · configurator · API layer
Integrations: payment · delivery · warehouse · CRM
Live concept: jimmyneuron-forma.vercel.app

Timeline: concept: design and storefront → catalog and product card → SKU configurator → cart and integrations

Result and business effect

Shipped jimmyneuron-forma.vercel.app - an online store platform with catalog, filters, SKU configurator, compare, wishlist, and cart. A JimmyNeuron e-commerce reference - the buyer follows “saw the product → built a configuration → added to cart”, not “messaged a manager on WhatsApp”. Need a similar store? Send a request and we’ll adapt it to your catalog and integrations.

A fit if you need

an online store with a catalog, product card, and cart - Online stores and booking
a product configurator that calculates SKU and price - Online stores and booking
payment, delivery, warehouse, and CRM integrations without changing the storefront - Web applications

Frequently asked questions

Questions about this type of project, the same ones clients ask before a similar build.

How long does a turnkey online store take, and how is the price set?

As a guide: a standard storefront with cart and admin takes from 3–6 weeks. A large catalog with integrations takes longer. Price depends on the catalog, B2C or B2B flows and the number of integrations. You get an estimate within 1–2 days of the brief; the timeline is fixed in the spec.

Who adds the products?

We design the catalog structure and product pages and help migrate products from your old platform. Photos, descriptions and prices come from you. After launch, your team runs the range in the admin.

Can we change products, prices and promotions ourselves?

Yes. Products, categories, banners, promo codes and SEO fields are edited in the admin, no developer needed. At Areta Flo, the chain’s own team runs the catalog and orders.

Will the store show up in search?

We build for it from the start: server-side rendering, meta tags, Schema.org, optimized images and mobile speed. Promotion is separate work, but the storefront is ready for it.