Questions, answered properly.

A commerce engine in two parts. A Laravel package that installs into your website and runs catalog, cart, checkout, orders, reviews and payments against your own database. And a central control plane, operated by Folowise, that manages your license, your feature grants, and your site's health. Your shop runs in your house; we govern from a distance.

No. One flat license fee per site. No revenue share, no transaction fees, no platform tax. You sell more, you pay the same.

A Laravel site on PHP 8.4 with any database Laravel speaks: SQLite, MySQL or Postgres. Install the package with Composer, run two artisan commands, and commerce is live the same day. If you do not have a site yet, Folowise builds the whole storefront around the engine as a full package.

FoloEngine is invite-only for now. Send a message through the contact page or email info@folowise.com. We reply within one business day, mint your license, and ship a sandbox the same week. The license key is shown once, then stored hashed; treat it like a password.

Yes. That is the other half of what Folowise does. You bring the brand and the vision; we design the storefront, build it, install FoloEngine inside, and run the marketing after launch. You end up owning a complete shop and its data without writing a line of code.

In your own database, on your own server. Products, orders, customers and reviews never leave it. The engine only ever receives counts and health signals, for example "128 products, 46 orders, queue healthy". It cannot read a single row, by architecture, not by promise.

Your shop rides it out. Pages are served from your own database, and the engine's permission checks answer from a signed local cache, so a brief outage on our side is invisible to your customers. If your site stays cut off from us for longer than its cache allows, the storefront pauses politely and your admin shows exactly why, instead of the shop running unlicensed. Nothing is lost: your data is in your database, and everything resumes on its own the moment the connection returns.

Yes, and you have to: FoloEngine ships zero frontend opinions. No theme, no template, no CSS to fight. Your storefront is your own Laravel app with your own design system. The engine gives it commerce; it never decides what a page looks like.

Cash on delivery, CliQ instant payments, and bank transfer work out of the box, with manual reconciliation in your own admin. You enable or disable methods per site without redeploying anything.

Promo codes, loyalty points, gift cards, product bundles and a public order-tracking page with carrier links. Each is a capability the engine grants per site, so you turn on exactly what your store needs and nothing it does not.

Customers get real accounts with order history, and optional one-tap Google sign-in for a faster checkout. Notifications reach owners and customers across email, Telegram, web push, SMS and an in-app feed, each channel switched on independently.

Yes. The engine is built bilingual from the ground up, English and Arabic with full right-to-left support, and your storefront can run in either. Because the storefront is your own Laravel app, you can add more languages without waiting on us.

Yes. Turn on advanced analytics and your admin shows traffic, conversion funnels, customer journeys, campaign attribution and a weekly email digest. Like everything else, that data lives in your own database, never on the engine.

Yes. Switch on the marketplace capability and products belong to vendors, the cart groups items by vendor, and checkout splits one basket into one order per vendor automatically. The same engine powers a single-brand shop or a full marketplace; you choose per site.

Yes. The booking vertical ships properties, destinations, live availability calendars and binding nightly quotes, with reservations linked to real orders for the money side. Hosts get their own back office, and a multi-host marketplace works the same way the multi-vendor store does. Same license, same signed engine.

Yes. Members post and edit ads, a moderation queue keeps quality up, and faceted search with autocomplete keeps everything findable. When you want revenue on top, paid promotion tiers, verified badges and dealer subscriptions are built in as capabilities you switch on.

Yes. The mobile API capability exposes a hardened HTTP API for native iOS and Android apps: token auth, guest browsing, device carts that merge on login, catalog, checkout, orders, loyalty and profile, plus push notifications to your customers' phones. Your app talks to your own site, and the data stays in your database.