Simple e-commerce websites you own completely
A focused catalogue, cart and checkout. Not a marketplace.
You make things people want: ceramics from your workshop, the book you finished last winter, spare parts for the machines you keep running, this season's honey. Selling them online should not mean renting your shop from a platform, and it should not mean a marketplace where your products compete for attention on someone else's shelf. It should mean your own focused store: your catalogue, your cart, your checkout.
That is what we build. A focused online store — catalogue, cart and checkout — on an open stack, delivered with everything a DevPowers build carries: the code, the repository, the delivery pipeline, your configured AI agent and the training to run the shop yourself. Fixed scope, fixed price, quoted without a call. First draft in 5 working days, deposit refundable if the draft does not fit the agreed brief.
- No calls — A human replies within one business hour.
- 5 working days — Your first working draft, ready to review.
- You own it — The code, repository and delivery pipeline.
- Never alone. Hand work back to us anytime, in credits.
Focused shops for boutiques, makers and specialists
This is one of the five DevPowers site shapes, and it is exactly what the name says: a shop for one seller. A boutique with a seasonal range. A maker with a product line. An author selling the book directly. A specialist with the parts nobody else stocks. Your catalogue is one you know by heart, not one a warehouse system manages for you. If your plan is a platform where thousands of vendors list products, that is a marketplace — a different product, and not ours.
The foundations are the same as in every DevPowers build — mobile-first accessible design, technical SEO, analytics, the gated pipeline, the handover and the live training — and they are described in full on the core website packages page. This page is about what is different when the site sells things.
What the shop includes
- A product catalogue with pages built for selling: name, photo, price, description, and the details your products carry — sizes, editions, compatibilities.
- Cart and checkout, with a payment gateway integrated into your shop. Which gateway suits your market is agreed in discovery and written into the scope.
- An admin panel for the shopkeeping: orders in, stock down, prices changed — by you, without a developer.
- Structured product data, so search engines and AI assistants can read your catalogue correctly.
- Hosting on our standard infrastructure, and your domain connected.
- Everything from the every-build list, including your configured AI agent and the training session.
You bring the product photos and texts — as in every build, copywriting from scratch and photography are excluded — and our agents help shape what you have.
The price change you ship on a Sunday night
The moment a shop owner finds out what their website is really for: Sunday night, and one line has been sold out since Friday. You do not open a ticket. You do not wait for a quote for "a small change". You type it — update all prices from the new list, mark the medium jars as sold out — your agent makes the change, the pipeline tests it, and you publish.
The same path handles the bigger ordinary changes: a new product page, a Christmas collection section, a shipping-cost update. You ask in plain language; your agent works on a branch; automated end-to-end tests, accessibility checks and an AI review gate what can reach your visitors. Rollback to the previous deployment is always available. You will never open the code if you do not want to.
You are not renting your own shop.
How checkout and payments work
Checkout is part of your shop, not a detour through a platform account. The payment gateway — which providers, which currencies, which markets — is agreed during discovery and written into your scope before you commit. The provider's fees are between you and the provider. There is no DevPowers platform in the middle of your transactions: no proprietary platform, no licence fee, no lock-in.
Your customer data stays in your store. The order history, the customer records and the product catalogue live in your code and your database, and if you ever move the shop, they move with it. You are not building someone else's marketplace. You are building your own trade.
Orders and stock without app subscriptions
Shopkeeping happens in an admin panel built for the ordinary work: see the orders, change the stock, adjust the prices, mark a line as sold out. The panel is part of your build — not an add-on rented monthly, and not a developer ticket for every price change. Exactly which screens your shop needs is written in the scope before work starts.
When the ordinary stops being enough — orders flowing into your accounting, fulfilment notifications, stock alerts — that is where the order processing automations service comes in: workflows that connect your shop to the rest of your business.
Why we build shops on an open stack you own
You can rent a shop from a hosted platform, and for some sellers that is a reasonable answer. This service is for the ones who would rather own. A DevPowers store runs on an open stack: the source code is yours, there is no DevPowers licence fee, no proprietary platform, and you can take the store to another provider at any time. Your domain registration always stays yours.
What we will not do is tell you our way is cheaper than someone else's. We do not publish other platforms' prices — that is a claim about another company's business, and we do not make it. We do not promise rankings, traffic, conversions or revenue either; that boundary is stated in the next section. What we stand behind is in your written scope and on the home page: the build is finished, properly engineered, and yours.
What we will NOT build
Clear scope protects the deadline, the quote and the handover. These exclusions are shop-specific; the exclusions every build shares — no copywriting from scratch, no photography, no logo and brand design, no ongoing marketing management, no AI subscriptions — are listed on the core website packages page.
- Multi-vendor marketplaces. One seller per shop: you. A site where anyone can open a stall is a platform, and platforms are outside our scope.
- Enterprise logistics. Catalogues that need ERP or warehouse-system integrations, auction sites, and supply chains that need their own consultant. We say no rather than quote them.
- Complex application logic beyond the agreed scope. Larger features exist — bought as change credits or quoted as a project.
- Performance and outcome promises. We do not promise rankings, traffic, conversions or revenue.
The commercial terms, in writing
- If the first draft does not fit the agreed brief, the deposit is refunded in full and the engagement ends. This applies only to the first draft and is our only guarantee.
- Payment has three stages: deposit before work, payment on first-draft acceptance, and final payment on handover.
- The first working draft arrives within 5 working days of the deposit and your content or written content plan. The number of revision rounds is stated in your scope.
- Shop projects carry a small monthly hosting fee, stated in the scope before you commit. Terms are renegotiated after 12 months. DNS is managed by DevPowers; your domain registration always stays yours.
- After launch: content and product changes are yours, unlimited and free. Ordinary code changes are yours too, through your AI agent and the gated pipeline. Larger work, and repairs of damage you cause yourself, are bought as change credits or quoted as a project; unused credits expire after two months. Failures caused by DevPowers are repaired free of charge. Infrastructure, CI/CD configuration, DNS and secrets are managed by DevPowers and are not client-modifiable.
Small changes are yours to make, free and unlimited, after handover. That is the whole idea.
The full payment milestones and terms — the safety model, the stop-and-warn rules and the complete support boundary — are on the how we work page.
Flying solo does not mean flying alone.
You can do it yourself - or hand it to us. Both stay open, permanently.
When a change is bigger than a prompt, or the hour is better spent on your own work, hand it to us by email or chat, the same way you reached us during the build. The work is bought as change credits: you receive an estimate in credits before anything starts, and you accept or decline it. Failures caused by DevPowers are repaired free of charge and consume no credits.
Every change is estimated in credits, and you accept or decline the estimate before work starts. Credit pack prices are being set with the first clients and published once they are measured, not guessed.
E-commerce FAQ: Products, payment gateways, taxes, and shipping
What kind of online shop does DevPowers build?
A focused shop for one seller: a product catalogue, a cart, a checkout and an admin panel for orders and stock. This shape fits boutique retailers, makers, authors selling directly, and specialists with a narrow, deep range. It is not a marketplace: there is one seller per shop, and that seller is you. If you are unsure whether your range fits, write to us — we acknowledge your email instantly and a human replies within one business hour.
What shops do you not build?
We do not build multi-vendor marketplaces, enterprise-scale catalogues with ERP or warehouse-system integrations, or auction sites. If the project needs a supply-chain consultant, it is outside our scope, and we will say so during discovery instead of quoting it. Complex application logic beyond the agreed scope is excluded from every DevPowers build.
How do payments and checkout work?
Checkout is built into your shop, and payment runs through a gateway integrated with it. Which gateway fits your market is agreed during discovery and written into the scope. The provider's fees are between you and the provider. There is no DevPowers platform between your customers and you: the shop, the order history and the customer records are your code and your data.
How do I manage orders, stock and prices?
In the shop's admin panel. The ordinary work — orders, stock levels, prices, sold-out marks — is yours to do directly, with no developer and no ticket. Exactly which screens and options your panel includes is written in the scope before work starts. Bigger changes go through your AI agent and the gated pipeline, and larger features are bought as change credits or quoted as a project.
Why own the code instead of using a hosted platform?
Because ownership changes what happens afterwards. You own the source code, there is no DevPowers licence fee, and you can move the store to another provider at any time; your domain registration always stays yours. We do not publish comparisons of other platforms' prices, and we do not promise sales, traffic or rankings — a supplier who promises sales numbers is promising something nobody can guarantee.
Do you handle taxes, invoices and shipping?
Only what is written in your scope. Tax rules, invoicing and courier integrations differ by country and by shop, so they are quoted individually where we can build them, and named as exclusions where we cannot. You will know which is which before you commit — nothing is discovered mid-project.
How fast is the first draft?
Within 5 working days. The clock starts when we have received your deposit and either your content or a written content plan. No other turnaround time is guaranteed.
What if I do not like the first draft?
If the first draft does not fit the agreed brief, the deposit is refunded in full and the engagement ends. This applies only to the first draft and is our only guarantee. The judgement is made against the agreed brief, and the condition is written into the agreement.
What does hosting cost?
Shop projects carry a small monthly hosting fee, stated in the scope — you will know the number before you commit. Terms are renegotiated after 12 months. DNS is managed by DevPowers, and your domain registration always stays yours.
What can I change myself after launch?
Product texts, prices and stock: you, unlimited, free. Ordinary code and layout changes: you, through your AI agent and the automated pipeline, free. Larger work, and repairs of damage you cause yourself: change credits or a quoted project; unused credits expire after two months. Failures caused by DevPowers are repaired free. The full boundary is on the how we work page.
Am I left without help after handover?
No. Doing it yourself is the default after handover - it is not a duty. Any change you would rather not make yourself, from a small edit to a new feature, you can hand to DevPowers by email or chat: the option stays open, it is simply not the default. The work is bought as change credits, and you receive an estimate in credits before any work starts; you accept or decline it. Failures caused by DevPowers are repaired free of charge and consume no credits.
What is a change credit?
A change credit is a unit of paid work you buy in advance and spend whenever DevPowers does work on your site. You buy a credit pack; packs cost less as a short subscription than bought one-off. Each change consumes credits by its complexity, not by the time it takes. Credits carry an expiry date and unused credits expire after two months. Credits cover new work and repairs of damage you caused yourself. Failures caused by DevPowers are repaired free of charge and consume no credits. Credit pack prices are being set with the first clients and published once they are measured.
What if I break the site myself?
A change that fails the automated gates cannot reach your live site, and rollback to the previous deployment is always available - most accidents stop before they happen. If you override a stop-and-warn and the site is damaged, DevPowers repairs it and the repair is paid in credits: you receive an estimate first and accept or decline it. Failures caused by DevPowers are repaired free of charge and consume no credits.
What if I just want DevPowers to do it?
Then we do it. Doing it yourself is the default because it is cheaper and faster for you, not because we stop working with you at handover. Send the change by email or chat, you receive an estimate in credits, and you accept or decline before anything starts. Nothing about the handover closes that door.
Your move, hero.
Tell us what you sell and what the shop must do. We acknowledge your email instantly and a human replies within one business hour — no call, form or booking calendar. The fixed quote follows as soon as discovery is complete.