Orders and payments
The customer chooses and orders. The business receives products, quantities and payment status together.
Variants, delivery, cancellations, stock, processor and post-payment steps. Payout is tracked separately.
Software that fits the way you work.
We begin with a real process: what the customer does, which information reaches the business and what needs to happen next.
Describe the system you needCustom software
from 199 EUR
Project / setup · one-time paymentOnline appointments, management tools or new features for an existing website. We start with a solution that fits your needs and can expand it over time.
One possible starting pointOnline appointments for a salon or barbershop: customers choose a service and an available time, while you manage appointments in one place.
The starting offer covers a focused working solution. A complete presentation website, a bespoke ecommerce platform and the other demonstrated features are quoted separately.
The final price depends on the functionality and the tools that need to connect.
Management · from 99 RON/month
For systems I operate and support.
Management for systems with ordering, payments, bookings or integrations starts from 99 RON/month and is scoped to the project.
Management for a more demanding setup may start from 149 RON/month. The final cost depends on the project's needs.
Any licences and provider fees are explained separately in the proposal.
Try an order
Interactive example — no real payments.
Fictional store. Orders and payments are simulated.
The everyday collection
Simple things. Well chosen.
Objects for ideas, journeys and the little rituals in between.
RON 49
Terracotta cloth cover. Dotted or plain pages.RON 89
500ml. Matte finish, screw cap.RON 79
Natural canvas, reinforced handles.RON 119
Everyday accessories, all in one place.RON 159
Charcoal felt. For a 13-inch format.RON 59
Three aluminium pens with a matte finish.RON 39
Snap closure. Cable included in the example.RON 69
Natural oak, rounded edges.On the business side
Complete an order above. The same products, quantities and customer details appear here, ready to process.
In the project, we define who handles the order, the notifications they receive and how changes are handled. Confirmed payment and payout to the account are distinct states.
The confirmed order will appear here.
Direct orders, on your restaurant’s terms.
I also build the system that handles orders, payments and administration.
From a conversation to a tested project.
We define the scope before implementation: what the project should do, who uses it and what a correct result looks like.
Discovery and structure
We review the current process, materials and constraints. We choose the necessary features and separate options that can follow later.
Design and review
I prepare the structure and examples with relevant content. You review the information, rules and direction before completion.
Implementation and testing
I build the agreed features and test primary journeys, errors and relevant screen sizes. I also check data exchange between applications in the available test environments.
Setup, launch and support
We prepare the required domain, hosting or equipment. Launch follows approval; maintenance, updates and support are agreed for the project.
What I need from you
An example of the current process, important rules and the people who use it. Access to applications and data is granted only as needed for implementation.
What the proposal defines
Deliverables, responsibilities, required materials, acceptance criteria and support. Accounts, licences, hosting, equipment and third-party fees are clarified before choosing the solution.
Budget and schedule depend on that scope and the available information. You do not need a technical specification for the first conversation.
Before we begin.
Must all existing applications be replaced?
No. We check what can stay and where a suitable connection is available. Sometimes an integration or smaller tool addresses the process without replacing the whole system.
How are errors and changes handled?
We define states, permissions and correction cases: cancellations, incomplete data, unconfirmed payments or unavailable capacity. Scope changes and later support are discussed separately.
What happens with maintenance after launch?
Management covers hosting, operation and routine content updates. The appropriate level and any further development are explained in the proposal, based on the solution.
What recurring costs might there be?
Alongside management, there may be licences or fees from payment and messaging providers. The proposal explains the services needed and their costs before implementation.
Does every website include payments?
No. A presentation website and an ordering system have different requirements. Functionality, providers and recurring costs are agreed for the project.
How do I receive and manage orders?
Depending on the project, orders can arrive in an administration view or a system you already use. We establish who sees them, which statuses are useful and which notifications are needed.