Reetail

A no-code visual editor that allows users to construct e-commerce storefronts by dragging pre-built components (product cards, hero sections, navigation bars, checkout flows) onto a canvas without writing HTML/CSS/JavaScript. The builder likely uses a component-based architecture with a WYSIWYG renderer that translates visual edits into underlying template markup, enabling real-time preview and mobile responsiveness constraints enforced at the design level.

Direct integration with Stripe's payment API that handles credit card processing, payment authorization, and settlement without requiring merchants to configure webhooks, API keys, or custom payment logic. The integration likely uses Stripe's hosted checkout or embedded payment forms (Stripe Elements) to tokenize card data client-side, reducing PCI compliance burden, and manages transaction state through Stripe's webhook system for order confirmation and fulfillment triggers.

Built-in SEO features that allow merchants to customize page titles, meta descriptions, and URL slugs for products and pages to improve search engine visibility. The system likely generates default SEO metadata from product names and descriptions, but allows manual override. Sitemaps are auto-generated and submitted to search engines, and the platform may include basic SEO recommendations (e.g., 'add meta description to this page').

Built-in social sharing buttons on product pages that allow customers to share products on Facebook, Twitter, Instagram, and Pinterest, with auto-generated preview images and descriptions. The system likely uses Open Graph meta tags to control how products appear when shared, and may include social media pixel tracking (Facebook Pixel, Pinterest Tag) for retargeting. Merchants can optionally connect social media accounts to display social feeds or product reviews from social platforms.

A pre-built library of e-commerce templates (likely 5-15 designs) that are optimized for mobile devices first, with desktop layouts derived from mobile constraints rather than the reverse. Templates use CSS media queries and flexible grid layouts (CSS Grid or Flexbox) to adapt to screen sizes, and the builder enforces mobile viewport constraints during design to prevent merchants from creating desktop-only experiences. This approach ensures storefronts render correctly on phones where most e-commerce conversions occur.

A structured product database interface that allows merchants to create and organize products with metadata fields (name, description, price, SKU, images, categories, tags). The system likely uses a relational database (PostgreSQL or similar) to store products and categories, with a UI for bulk import/export (CSV) and individual product editing. Products are indexed for search and filtering, enabling customers to browse by category or search by name/description.

A dashboard that displays incoming orders with customer details, items purchased, and payment status, allowing merchants to mark orders as shipped and send fulfillment notifications to customers. The system likely stores orders in a database linked to Stripe transactions via webhook events, and integrates with email services to send order confirmation and shipping notification emails. Merchants can manually update order status (pending, shipped, delivered) without API integration.

A customer authentication system that allows buyers to create accounts, log in, and view their order history with past purchases and payment status. The system likely uses session-based authentication (cookies or JWT tokens) to maintain login state, stores customer profiles in a database, and links orders to customer accounts via foreign keys. Customers can view order details, download invoices, and potentially initiate returns or refunds through their account dashboard.

A streamlined checkout experience that collects customer information (email, billing address, shipping address) and calculates shipping costs before payment. The checkout likely uses a multi-step form (cart review → shipping address → payment) with client-side validation and server-side verification, and integrates with Stripe for payment processing. Shipping costs may be calculated based on predefined rules (flat rate, weight-based, or zone-based) rather than real-time carrier rates.

A dashboard displaying key metrics (total sales, order count, average order value, revenue by product) with optional date range filtering and export to CSV. Analytics are likely calculated from order data stored in the database, aggregated in real-time or via scheduled batch jobs, and displayed as simple charts or tables. The system may track page views and conversion rates using a lightweight analytics script (similar to Plausible or Fathom) embedded in the storefront.

Automated email triggers that send transactional emails (order confirmation, shipping notification, payment receipt) to customers based on order events. The system likely uses an email service provider (SendGrid, Mailgun, or in-house SMTP) to send emails, with templates for each notification type. Triggers are configured server-side (e.g., 'send confirmation email when order is created', 'send shipping email when order status changes to shipped') and execute asynchronously to avoid blocking the checkout flow.

Ability to connect a custom domain (e.g., mystore.com) to the Reetail storefront and customize basic branding elements (store name, logo, colors, favicon) through the dashboard. The system likely uses DNS CNAME or A record configuration to route custom domains to Reetail's servers, and stores branding settings in the database to be applied to all pages. SSL/TLS certificates are likely auto-provisioned via Let's Encrypt to enable HTTPS on custom domains.