\n\n## Overview\n\nStorefront is the commerce extension for Fleetbase. It combines a Laravel API package with an Ember engine for the Fleetbase Console, giving operators the tools to manage stores, products, carts, checkout, customers, marketplace networks, and fulfillment workflows from one logistics-native system.\n\nUnlike a generic e-commerce plugin, Storefront is built around the handoff from purchase to delivery. A checkout can create Fleet-Ops orders, attach storefront order metadata, expose customer and commerce details in the Fleetbase Console, and keep operators close to the real delivery lifecycle.\n\nRead the official guide at [fleetbase.io/docs/storefront](https://www.fleetbase.io/docs/storefront).\n\n## Features\n\n- **Store and marketplace management**: run a single store or organize many stores into Storefront networks.\n- **Product catalog**: manage products, categories, variants, variant options, addons, addon categories, images, pricing, tags, and availability hours.\n- **Locations and mobile commerce**: configure store locations, service areas, food trucks, Fleet-Ops vehicle links, and catalogs assigned to mobile stores.\n- **Carts and checkout**: support persistent carts, line items, variants, addons, scheduled items, service quotes, checkout initialization, and order capture.\n- **Payments**: configure Stripe, QPay, and cash-on-delivery flows through Storefront gateways.\n- **Customers**: support customer registration, login, SMS verification, social login hooks, saved customer metadata, device registration, order history, and account closure flows.\n- **Orders and fulfillment**: manage Storefront orders in the console, advance order activity, assign/unassign drivers, mark preparation states, complete pickups, and inspect commerce details alongside route and tracking data.\n- **Reviews and votes**: expose API resources for customer reviews and voting.\n- **Promotions and notifications**: manage notification channels and send broadcast or transactional push notifications through APNs, FCM, and related Storefront notification classes.\n- **Dashboard analytics**: ship Storefront widgets for revenue, order volume, average order value, active orders, completed orders, customers, cart conversion, cancellation rate, revenue trends, top products, customer insights, order status mix, recent orders, and recent customers.\n- **Fleet-Ops integration**: register Storefront summaries inside Fleet-Ops order details and add product-as-entity tooling to Fleet-Ops order creation.\n- **Internationalization**: include translations for multiple locales through the extension translation files.\n\n## Architecture\n\nThis repository contains both sides of the Storefront extension:\n\n| Area | Path | Purpose |\n| --- | --- | --- |\n| Ember engine | `addon/`, `app/`, `config/`, `translations/` | Fleetbase Console UI, routes, models, components, services, widgets, and translations. |\n| Laravel API | `server/src/`, `server/config/`, `server/migrations/` | Storefront API controllers, models, resources, middleware, providers, observers, notifications, jobs, and database migrations. |\n| Tests | `tests/`, `server/tests/` | Ember integration tests and backend test scaffolding. |\n\nThe Ember package is published as `@fleetbase/storefront-engine`. The Laravel package is published as `fleetbase/storefront-api`.\n\n## Console Modules\n\nStorefront registers a Console entry under the `storefront` route and exposes these primary work areas:\n\n- **Dashboard**: Storefront-specific operational and analytics widgets.\n- **Products**: product catalog, categories, variants, addons, import processing, and product entity creation.\n- **Orders**: incoming Storefront orders, activity actions, customer details, commerce summary, documents, route/tracking context, and comments.\n- **Customers**: customer records and order history.\n- **Networks**: multi-store marketplace networks, store assignment, categories, invitations, and network-level views for stores, customers, and orders.\n- **Catalogs**: product bundles and catalog categories, including food truck catalog assignment.\n- **Food Trucks**: Fleet-Ops vehicle-linked mobile stores with service area and zone support.\n- **Promotions**: push notification campaigns and notification channel workflows.\n- **Settings**: store profile, API keys, locations, gateways, and notifications.\n\n## API Surface\n\nStorefront exposes two API families.\n\n### Public Storefront API\n\nThe public customer-facing API is mounted under `storefront/v1` and protected by Storefront API middleware. It includes:\n\n- Store lookup, store/network information, locations, gateways, search, tags, and network stores.\n- Categories, products, food trucks, reviews, and customer-facing catalog browsing.\n- Persistent carts with add, update, remove, empty, and delete operations.\n- Service quotes from carts.\n- Checkout initialization, status, capture, Stripe setup intents, Stripe payment intent updates, and QPay capture callbacks.\n- Customer registration, login, SMS code verification, social login endpoints, device registration, saved places, customer orders, phone verification, Stripe customer helpers, and account closure flows.\n- Order pickup completion and receipt generation.\n\n### Marketplace network contract\n\nA public `network_...` key uses accepted `network_stores` membership as its marketplace authorization boundary, including member stores owned by another company. Marketplace responses expose only public Storefront resources; they do not expose member customers, internal API keys, or gateway credentials.\n\n- `GET storefront/v1/stores` supports search, online/tag/category/ID filters, rating/age/popularity/trending/nearest sorts, distance filtering in meters, and limit/offset pagination.\n- Categories and published products can be scoped to a member store. Product responses include public merchant context for marketplace search and cards.\n- Cart line items preserve both merchant and store-location identity. Product and location substitution across stores is rejected.\n- Checkout revalidates active membership, store availability, published products, location ownership, the network multi-cart policy, and one-cart currency before payment begins.\n- Network delivery quotes resolve one origin per represented store and reject missing, foreign, or mismatched locations with `422`.\n- When `Customer-Token` is present, it is authoritative; a conflicting checkout customer ID returns `403`.\n\n### Internal Console API\n\nThe protected internal API is mounted under `storefront/int/v1`. It powers the Fleetbase Console and includes:\n\n- CRUD resources for orders, customers, stores, store hours, store locations, products, product hours, variants, variant options, addons, addon categories, gateways, notification channels, reviews, votes, food trucks, catalogs, catalog categories, and catalog hours.\n- Order actions for accept, preparing, ready, completed, cancel, and unassign driver.\n- Network actions for adding stores, removing stores, categories, invitations, and network lookup.\n- Analytics endpoints for overview, revenue trends, order status mix, top products, and customer insights.\n- Metrics and operational action endpoints.\n\n## Getting Started\n\nStorefront is designed to run inside a Fleetbase installation with `fleetbase/core-api` and `fleetbase/fleetops-api` available.\n\n### Requirements\n\n- PHP `^8.0`\n- Node.js `>=18`\n- pnpm\n- Composer\n- Fleetbase Core API\n- Fleetbase FleetOps API\n\n### Install Dependencies\n\n```bash\npnpm install\ncomposer install\n```\n\n### Backend Package\n\n```bash\ncomposer require fleetbase/core-api\ncomposer require fleetbase/fleetops-api\ncomposer require fleetbase/storefront-api\n```\n\n### Frontend Package\n\n```bash\npnpm install @fleetbase/storefront-engine\n```\n\n## Development\n\nFor the full local Fleetbase workflow, see the [Fleetbase Development Setup guide](https://www.fleetbase.io/docs/platform/quickstart/development-setup). That guide covers cloning the main repository with submodules, mounting live package source, linking extensions, running the Console dev server, and reloading the API after backend changes.\n\n### Use Local Storefront Source in Fleetbase\n\nWhen developing Storefront inside the Fleetbase monorepo, run the package linker from the repository root so the local `packages/storefront` source replaces the published Storefront packages used by Console and API:\n\n```bash\nflb-package-linker enable storefront\nflb-package-linker install storefront\n```\n\nThe linker updates the local Console and API manifests for development. To inspect the current link state:\n\n```bash\nflb-package-linker status\nflb-package-linker doctor\n```\n\nIf the linker is not installed yet, install it once from the Fleetbase repository root:\n\n```bash\nnpm link\n```\n\nAfter linking backend package changes, reload the running API worker so Laravel Octane picks up PHP changes:\n\n```bash\ndocker compose exec application php artisan octane:reload\n```\n\nFor frontend changes, run the Fleetbase Console dev server as described in the development setup guide; linked Ember packages are watched and live-reloaded by the dev server.\n\n### Package Commands\n\nRun the Ember engine locally:\n\n```bash\npnpm start\n```\n\nBuild the Ember engine:\n\n```bash\npnpm build\n```\n\nRun frontend lint and tests:\n\n```bash\npnpm lint\npnpm test\npnpm test:ember\n```\n\nRun backend checks:\n\n```bash\ncomposer test:lint\ncomposer test:types\ncomposer test:unit\ncomposer test\n```\n\nGenerate and summarize the full backend Clover baseline with Xdebug or PCOV:\n\n```bash\nXDEBUG_MODE=coverage composer test:coverage:clover\ncomposer coverage:summary\n```\n\nMarketplace changes on `dev-v0.4.19` must retain 100% backend statement coverage. Focused success and failure-path contracts should be added before regenerating the baseline.\n\n## Configuration\n\nStorefront configuration is provided through the Laravel package config files and environment variables:\n\n- `server/config/storefront.php`: API routing, Storefront app verification settings, database connection, and request throttling.\n- `server/config/api.php`: Storefront API configuration.\n- `server/config/database.connections.php`: Storefront database connection defaults.\n\nImportant environment variables include:\n\n| Variable | Purpose |\n| --- | --- |\n| `STOREFRONT_DB_CONNECTION` | Database connection name for Storefront models. |\n| `STOREFRONT_BYPASS_VERIFICATION_CODE` | Development bypass code for Storefront app verification flows. |\n| `STOREFRONT_THROTTLE_REQUESTS_PER_MINUTE` | Public Storefront API request limit. |\n| `STOREFRONT_THROTTLE_DECAY_MINUTES` | Public Storefront API throttle decay window. |\n\nFor customer app configuration, see the [Storefront App configuration docs](https://www.fleetbase.io/docs/storefront/app/configuration).\n\n## Documentation\n\n- [Storefront documentation](https://www.fleetbase.io/docs/storefront)\n- [Products and catalog](https://docs.fleetbase.io/guides/storefront/products/)\n- [Orders and checkout](https://www.fleetbase.io/docs/storefront/orders/overview)\n- [Checkout flow](https://www.fleetbase.io/docs/storefront/orders/checkout)\n- [Store locations](https://www.fleetbase.io/docs/storefront/stores/store-locations)\n- [Storefront App configuration](https://www.fleetbase.io/docs/storefront/app/configuration)\n\n## Contributing\n\nStorefront follows the same review expectations as the rest of Fleetbase:\n\n- Keep changes small and reviewable.\n- Preserve existing architecture and naming conventions.\n- Add or update tests when practical.\n- Run the relevant frontend or backend validation commands before opening a pull request.\n- For API behavior changes, check whether the API specification and public documentation also need updates.\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md) for general contribution guidance.\n\n## License\n\nFleetbase Storefront is open-source software licensed under the [AGPL-3.0-or-later](LICENSE.md).\n","readmeFilename":"README.md"}
![\"Fleetbase](\"https://flb-assets.s3.ap-southeast-1.amazonaws.com/static/storefront-logo.svg\"){kind=logo}
\n![\"License:](\"https://img.shields.io/badge/license-AGPL--3.0--or--later-blue\"){kind=icon}
![\"Coverage\"](\"https://codecov.io/gh/fleetbase/storefront/branch/main/graph/badge.svg\"){kind=icon}
\n ![\"PHP](\"https://img.shields.io/badge/php-%5E8.0-777bb4\"){kind=icon}
![\"Node](\"https://img.shields.io/badge/node-%3E%3D18-339933\"){kind=icon}
![\"Ember](\"https://img.shields.io/badge/ember-engine-e04e39\"){kind=icon}
![\"Fleetbase](\"https://www.fleetbase.io/images/screenshots/storefront/storefront-dashboard.webp\")
\n