Everything you need
to sell
Storefront, marketplaces, wholesale, subscriptions, point of sale, loyalty, affiliates and AI — in one system, sharing one catalogue. No app store. Nothing else to subscribe to.
14 days free, no card required.
Not a storefront with somewhere to bolt the rest on
Every way you sell, running against one catalogue, one set of customers and one stock figure.
A shop published to the edge
Static files on a CDN, served from a node near your customer, with live stock fetched separately. No application and no database between the visitor and the page — or keep Shopify and Woo, and Qwikr will not publish one at all.
MarketplacesSix channels, one catalogue
Stock-only by default, so listings you spent years building keep their titles, ranking and feedback. Nothing is written to an account until its prior state has been captured.
B2BWholesale & trade
Per-account pricing, terms, credit limits and quotes — on the same stock as retail.
RecurringSubscriptions
Boxes, gifting and referrals, with customers who skip and pause themselves.
In personPoint of sale
Counter, stall or trade desk. Sales hit the same figure every channel reads.
RetentionLoyalty & affiliates
Points, memberships, stamp cards, and commission held until returns close.
Automation & AIThe work that does not need you
Repricing inside a margin floor it cannot cross, drafted product copy you approve, Amazon image compliance checked across the catalogue, and the customers who quietly stopped buying found and written to.
MoneyVAT & accounting
Rates per product, and orders reaching Xero, QuickBooks, Sage or FreeAgent once.
feature areas built and running — gift cards, bundles, returns, reviews, wishlists, flash sales, warehouses, carrier manifests, EU VAT OSS.
What this replaces
The usual way to get here is a storefront plus an app for everything it does not do. Each one is another subscription, another login, and another system with its own opinion about your catalogue.
A typical stack
Everything billed separately, integrated by you.
- A hosted storefront
- A subscriptions app
- A wholesale / B2B app
- A loyalty app
- An affiliates app
- A point of sale, usually charged per till
- A marketplace connector
- A reviews app
- A returns app
Qwikr
One system, one catalogue, one bill.
- Edge-delivered storefront, or keep Shopify or Woo
- Subscriptions, boxes, gifting and referrals
- Wholesale with terms, credit limits and quotes
- Loyalty, points, stamp cards and memberships
- Affiliates with tiers and held payouts
- Point of sale across as many locations as you have
- Amazon, eBay, Etsy, TikTok Shop and OnBuy
- Reviews, wishlists and upsells
- Returns, refunds and supplier disputes
Eight kinds of product, on the same catalogue
Most platforms do simple and variable well and treat everything else as a plugin. All of these share one stock record, one customer, one checkout and one set of reports.
Simple & variable
One product, or one with sizes, colours and per-variant stock, barcodes and prices.
Bundles & kits
Sell several products as one, priced together, drawing down each component’s stock.
Digital downloads
Files delivered on payment, with the download itself tracked rather than trusted.
Gift cards
Issued, redeemed and part-spent — online and at the till, against one balance.
Configure to order
Guided steps, options that rule each other in and out, and a build tracked to dispatch.
Subscriptions & boxes
Recurring orders that skip, pause, gift and customise, consuming stock on a schedule.
Hire & rental
Bookable assets with availability, deposits, inspections and damage claims.
Trade-only lines
Products a wholesale account can see and buy that never appear on your retail shop.
The features you would otherwise be buying one at a time
Email marketing with real flows, memberships, loyalty, referrals — plus the unglamorous machinery that decides whether a shop is actually runnable. All included, all against the same customers and the same catalogue.
Email that does the following up
Reasons to come back
Levers on the order
You sold the last one on eBay at 9:04. Amazon sold it again at 9:06.
This is what a stack of separate tools costs you, and it is the clearest test of whether a platform is genuinely one system. Both orders are real. You have one item. Every tool was correct at the moment it answered.
The one exception is deliberate: a channel is never told about a sale it made itself. It already knows, and echoing it back is how a sync starts oscillating.
One system holds the record
Your shop, or Qwikr. Everything else receives that figure and cannot argue with it, so there is no loop and no oscillation. A wholesale order, a till sale and a subscription shipment all decrement the same number.
Only a sale may change it
Not imports, not supplier feeds, not a bulk edit — those would overwrite the very figures being reconciled against. Enforced at the point every push passes through, not left as advice.
Everywhere else follows
The new figure reaches every other channel within seconds, and never goes back to the one that sold it. It already knows.
Every screen is a route. Every route is an API.
The admin and the storefront are built on the same HTTP API you get — so there is no second-class public surface that lags behind the real one. Bring your own front end, drive it from a script, or wire it into whatever you already run.
# Scoped key. This one may read orders and nothing else. curl -H "Authorization: Bearer qwk_live_…" \ "https://app.qwikr.store/api/orders/batch/pick-list" # Outbound webhooks are signed and retried. # X-Webhook-Event: order.created # X-Webhook-Signature: HMAC-SHA256 of the raw body # A configurator resolves server-side, so option rules and # pricing cannot be edited in the browser. POST /api/products/{slug}/configurator/resolve { "options": [14, 31, 62] } → { "price": "418.00", "valid": true }
Keys are scoped, and the scope is enforced
A key names what it may do — read_orders, write_orders, read_analytics — and it is checked on the request, not written in the docs and hoped for.
It fails closed, which is unusual
A protected endpoint added without declaring a required scope refuses the request and logs a misconfiguration rather than allowing it. The safe default for a missing rule is no; getting that backwards is how endpoints quietly become public.
Webhooks you can actually trust
Signed with HMAC-SHA256 over the raw body, delivered with attempts recorded and failures retried. A webhook you cannot verify is a webhook you have to poll around.
Documentation generated from the routes
Including which scope each one needs. A reference that has drifted from the code is worse than none, because it is trusted — that happened here, which is exactly why it is now derived rather than described.
Your front end, our commerce
Catalogue, orders, stock and the configurator over HTTP. Build the site in whatever you like and leave stock rules, VAT, marketplace sync and payments where they already work.
No developers? That is the better half of this.
Most merchants here have never made an API call and never will. The reason the API matters to you anyway is what it says about how the platform is built: everything is reachable, so almost everything is changeable.
Which is the actual offer. If Qwikr does not do something you need, ask. If it is reasonable and it would be useful to other merchants too, we will build it — and it becomes part of the platform everyone gets, not a bespoke fork you pay to maintain.
That is the advantage of not being a company with an app store. There is no marketplace to petition, no third-party developer to chase, and no queue behind ten thousand other requests. You tell us, we look at it, and we tell you either way.
Nearly everything on this page started as somebody asking for it.
Stop paying nine companies to run one shop
Fourteen days free, no card, your own catalogue. Connect a channel and see the whole thing working on your real products.