An honest inventory, verified against the codebase. “Needs configuration” means the feature ships and works, but requires credentials or setup before customers can use it.
Each needs merchant credentials; regional providers require their own approval.
Cash on Delivery
Available
Works out of the box when enabled.
Email notifications (orders, resets, shipping)
Needs configuration
SMTP settings required.
Taxes
Available
Rate rules configured per region.
Inventory & warehouses
Available
Stock, low-stock alerts, warehouse module.
Returns / refunds
Available
Request flow + admin processing.
Dashboards & administration
Feature
Status
Notes
Admin dashboard, analytics & reports
Available
Revenue, orders, vendors, exports.
RBAC (roles & permissions for staff)
Available
Granular permission system.
Vendor dashboard & approval workflow
Available
Commission and payout recording.
Storefront builder (homepage sections)
Available
Reorder/enable sections; empty ones auto-hide.
CMS pages, banners, blog, FAQ
Available
—
Media library & uploads
Available
Local-disk storage by default; external URLs supported.
Virtual try-on (image generation)
Needs configuration
Requires FASHN_API_KEY.
Not included
Live courier/carrier integrations — adapter ready, no pre-wired providers (see Payments & Shipping).
Automatic currency conversion of stored prices — display currency is platform-wide; amounts are not exchanged.
Delivery time-slot booking — order model has no slot concept.
Mobile app hosting and store publishing — a separate Flutter mobile app is available (see Mobile App Overview); you build it, host the backend, and publish it under your own store accounts.
Vercel/serverless-ready media storage — uploads assume a persistent server disk by default.
ℹ️
Anything reachable in the UI but dependent on third-party credentials (AI, live streaming, try-on, payment gateways) is marked “needs configuration”, not “available”, on purpose: it ships, but it will not do anything until you add real credentials.