How you sell
We start with your process: where the products come from, who packs them, what happens on a return. The store has to fit that, not the other way round.
A store asa system you run,not a template you buy.
Catalogue, cart, payments and an order panel built around the way your sales actually work, not around what an off-the-shelf package happens to do.
Scope What exactly
What exactly
you get.
A store is not a page with a buy button. It is a daily working tool, where someone takes orders, corrects stock levels and explains to a customer where the parcel is.
| Catalogue | Categories, variants, sizes, colours and promo prices without working around the system |
|---|---|
| Cart and checkout | A short path to purchase, without forcing people to register before they buy |
| Payments | A payment gateway, BLIK and bank transfer, with refunds handled properly |
| Delivery | Courier, parcel lockers and pickup in person, with real costs instead of one flat rate |
| Order panel | Statuses, search, invoices and customer history in one place |
| Integrations | Warehouse, accounting or a wholesaler, if something already runs on your side |
| Hosting | On our server, with a certificate and uptime monitoring. You do not buy it separately |
| Backups and data | Daily backups of the order database checked for restore, updates and keeping an eye on access |
Process This is how
This is how
we will
work together.
Catalogue and path
We lay out the categories and the road from landing to payment. This is where most of the things that later cost you sales show up.
Build
You work on a running store from the first days. We place test orders together, before anything goes public.
Launch and care
Turning on payments, moving the domain, training on the panel. After launch we stay for the first weeks, when the real cases appear.
Price What the quote
What the quote
depends on.
| Number of products | Thirty items is different work than a few thousand with variants |
|---|---|
| Variants | Sizes, colours and bundles complicate both the catalogue and the stock |
| Integrations | Hooking up a wholesaler, a warehouse or accounting can be bigger than the store itself |
| Data import | Moving products and customers from the old store, if there is one |
| Payments and delivery | How many methods, and whether real shipping costs have to be calculated |
We quote a store after a conversation about how you sell, not by the number of pages. The conversation and the quote are free and commit you to nothing.
Questions What people ask
What people ask
most often.
Why not Shopify or Shoper?
If you sell in a standard way and the subscription suits you, that is often a good choice and we will tell you so. A custom store makes sense when the process is unusual, the integrations are specific, or the commissions and limits start to cost real money.
Who is responsible if the store goes down on Black Friday?
We are, because the server is ours and so is the monitoring. Response time is set in the contract, and for dates like that it is worth setting separately.
Do I have to buy hosting separately?
No. The store runs on our server, and hosting, the certificate and the backups are on us. With a store that carries one more meaning: when something breaks on a Friday afternoon, we are not sending you to another provider’s helpline.
What about order and customer data?
The order database has a daily backup that we check for restore, not only for completion. The server is not shared, and panel accounts are personal, so it is visible who changed what.
Will the store comply with GDPR and consumer law?
Terms and policies are a lawyer’s ground, not ours. On the store side we provide what the rules require technically: consents, order data, the right to delete an account and access to invoices.