An online store that follows your business rules

Most shop platforms decide how you sell. If your customers are companies, your products are regulated, or you run more than one brand, you end up buying add-ons and hoping they fit. I build on Fluss, a commerce platform I wrote and maintain, so the rules of your business go into the checkout itself.

Fluss today runs MEEPLE (board-game rental) and this website. It is also the base on which, in my work at RGP, I delivered a regulated agricultural B2B marketplace; that project and its connections to state registers belong to RGP.

Is this for you?

Fluss is worth it when at least one of these is true:

You sell to companiesYour buyers order as a business, expect an invoice and pay by transfer or on agreed terms.
Your products are regulatedLicences, permits, state reporting or delivery restrictions decide who may buy what.
You run more than one brand or siteSeveral storefronts, country sites or partner stores that should share one back office.
Your customers speak several languagesLatvian, English, German, Russian: the store and its wording must exist in each.
Your selling model is unusualRental, subscriptions, orders fulfilled by several suppliers: the standard cart does not fit.
You want to own the platformNo monthly platform rent, no app fees, code and data in your hands.

Fluss next to Shopify, Magento and OpenCart

Plain answers to the questions buyers actually ask. This is not a feature race: where a rented platform is the better deal, the table says so.

Compare with:ShopifyMagentoOpenCart

	Fluss	Shopify	Magento	OpenCart
Companies buy and pay by invoice or later	✓ Company profiles, pay-later with reminders, invoice matched to the bank statement	◐ Only on the expensive Plus plan or via apps	◐ In the paid Adobe edition	◐ Extensions of mixed quality
Licences, permits and reporting to the state	✓ Licence checks and delivery rules built in; register connections built for your project	✗ Custom app, on their terms	◐ Custom work by a specialist agency	✗ Custom work, rarely done
Several brands or sites in one place	✓ Own address, admin and team per brand; one update for all	✗ One store per subscription	◐ Several websites, shared admin, heavy setup	◐ Multi-store with one admin, little separation
Your team changes texts and languages itself	✓ Every phrase editable per language in the admin	◐ Translation apps and markets, extra cost	◐ Language packs; changes need a specialist	◐ Language packs, patchy translations
Promotions by customer type, volume tiers, coupons	✓ Built in, targeted at companies, private or repeat buyers	◐ Basic discounts; segments need apps	✓ Strong promotion rules	◐ Basic coupons and specials
Rental, subscriptions, orders split between suppliers	✓ Modelled with product settings; supplier split built in	◐ Apps with monthly fees	◐ Extensions or custom work	◐ Extensions
Launching a new store or site	✓ From a saved copy; this site went live in a day	✓ Minutes, new subscription	✗ Days of setup per instance	◐ Manual setup per site
What you pay every month	◐ Hosting plus a quote for the work; no licence, no app fees	◐ Plan, transaction fees and apps	◐ Free core, expensive hosting and specialists; licence for the full edition	✓ Free; extensions and all upkeep on you
Who owns the code and data, who is responsible	✓ You own both; the engineer who built it answers	✗ Rented platform; you can export data	◐ Yours, but you depend on an agency and Adobe's roadmap	◐ Yours; support from extension vendors and forums

✓ built in · ◐ possible with add-ons, a higher plan or custom work · ✗ not available

Can my customers buy as a company and pay by invoice?

Yes. A buyer registers as a company with its registration and VAT numbers and a separate legal and delivery address. At checkout they pay by card or bank link, pay later by an agreed date with reminder e-mails before and after it, or by bank transfer against the invoice the shop creates when the order is placed. Paste the bank statement export (Swedbank today) and incoming payments match themselves to orders.

My products are regulated. Can the shop enforce the rules?

Yes. A buyer uploads a licence or permit, your staff approves it, and restricted products cannot be checked out without a valid one; orders that need a look wait in a review state instead of going through. Rules per product decide which delivery options a restricted item may use. Connections to specific state registers are built per project on top of that: the ones I built for the RGP marketplace belong to RGP, and yours would be built for the registers and reporting your business answers to.

Can I run several brands without several projects?

Each brand or site is a separate tenant: own domain, own admin, own staff and roles, own catalogue, customers, orders and files. The software underneath is one and is updated once. A plan decides which screens a tenant gets, so a content-only site never sees shop screens. MEEPLE and this website share one small server.

Do I need a developer for every wording or language change?

No. Every phrase in the store is a dictionary entry per language that your team edits in the admin. Languages live in the address (/de/, /lv/), each page has its own title and description per language, and pages and forms are assembled from blocks in the admin. This website is English, German and Latvian from one source, and it went from an empty repository to a live site in one day.

Can I run promotions the way my sales team thinks?

Volume tiers, percentage or fixed discounts, coupon codes with limits and validity windows, offers restricted to a category or a product group, and rules that apply only to companies, only to private buyers or only to repeat customers. Products can carry a dated special price and show the price per kilogram or litre.

What does daily operation look like?

Orders move from created to awaiting payment, paid, shipped and delivered, with the invoice PDF created at placement. Orders with lines from several suppliers split into one child order per supplier with a price-free packing slip. Each user builds their own dashboard from the metrics they care about, alerts arrive in the admin, by e-mail or in Telegram, and customer documents, buyer chat and login history are handled in the same place. Your team gets a handbook and training in Latvian.

Who answers when something breaks?

I do, and I wrote the platform. Work runs in two-week sprints with a demo at the end of each and a testing window for your team before anything goes live. A bug your tester finds is reproduced, traced to its cause and fixed, and the cause is written down so it does not come back.

One condition, any size

Fluss fits a five-product shop and an enterprise platform alike; what changes is how much gets configured and how much gets built. The one condition is an engineer on your side. Fluss is not a rented platform you set up from a menu: I configure it for your case, train your team and extend it wherever your business needs something the standard cart does not have. If you want to sell tomorrow without talking to anyone, a rented platform will serve you better. If you want a store that grows with the business, this is what I do.

What it costs

The price is a quote for your project, not a plan from a price list. It covers consulting, configuration, training your team and any development your case needs, and it depends on how much of each there is. There is no platform licence and no monthly fee per app on top of that. Hosting is a small server: MEEPLE and this site share one. The code and the data are yours, so another team could continue the work if you ever needed them to.

Want a store that will not need a rewrite in two years?

Tell me about your customers, your products and the rules you have to follow. I will tell you whether Fluss fits, what it would take, and what I would build first.

Discuss your project