Connector set-up
Individual quote
from 2 working days
When a ready connector between the store and Holded or Odoo covers your case.
- Connector chosen and set up
- Series, taxes and payment methods
- Test on real orders
- Short handover
Holded, Odoo, A3 or your ERP · WooCommerce, PrestaShop, Shopify
Paid orders become invoices in Holded, Odoo or A3, stock and prices stay the same in the store and in the back office, and payments from Redsys, Stripe or Bizum are matched automatically. Your team handles exceptions instead of retyping.
Individual quote
Free first call. I usually reply within 2 hours.
Ready-made connectors work until your store does something slightly different: company invoices, bundles, several warehouses, partial refunds. I check what a connector can do, set it up if it is enough, and build the missing part on the Holded, Odoo or store API when it is not. You talk to the person who builds it.
What moves, in which direction and when.
| Data | Direction | When |
|---|---|---|
| Paid order → invoice | store → Holded | on payment |
| Refund → corrective invoice | store → Holded | on refund |
| Stock | Holded → store | every 15 minutes |
| Prices for companies | Holded → store | on change |
Decided per flow, not for the whole project.
What breaks integrations in practice.
The same sale is invoiced twice, and the numbering in the books does not match.
What to do: One place issues invoices: Holded. The store plugin only sends the data.
Orders silently miss the books and stock drifts apart.
What to do: Error alerts to the team channel and a daily check of orders against invoices.
You can run it with me, with your team or with another developer.
Scope, price and timeline are agreed in writing before work starts. Connector and tool subscriptions are paid separately.
Individual quote
from 2 working days
When a ready connector between the store and Holded or Odoo covers your case.
Individual quote
from 1 week
Orders, refunds, stock and payments synced, with the missing parts built on the API.
Individual quote
from 3 weeks
A3, Sage or another ERP, several warehouses, marketplaces or B2B prices.
Furniture store (NDA)Two WooCommerce furniture stores: delivery costs, availability and lead times, Apple Pay and Google Pay, emails, and a shared module that keeps both stores in sync.
Ekspres ParkingAirport parking in Warsaw: online booking with packages, VAT invoices and online payment, and automated handling of bookings.„We worked with Vlad on a Next.js project. He knew what he was doing from day one, didn't overcomplicate things and came up with better approaches on his own. I especially value his work on the site's performance. Everything was delivered as agreed.”
George B. CEO, finance company
„We needed to build an MVP fast to test our idea in practice. Vlad helped us choose sensible solutions and focus on what we really needed for launch. We didn't try to build everything at once, yet he made sure the project could grow later without starting from scratch.”
Alex N. Product Manager at StartupX
„Vlad got up to speed with our project quickly and pointed out several problems we hadn't treated as priorities. He sorted out our database and security issues. I liked that he didn't just complete tasks but clearly explained why something was worth changing and what the consequences could be.”
Michał R. CTO at TechCorp
„We had an app where every bigger change was becoming a problem. Vlad helped us clean up the code, rebuild some of the older parts and introduce automated tests. Working on new features is much easier now. I also appreciate his patience in explaining technical topics to people outside the development team.”
Sara K. Product Owner at WebSolutions
Two sentences are enough: the store, the back office and what is retyped today. I reply within 2 hours as a rule and tell you whether a connector is enough, with price and timeline.
Often you do not, and then I only set the connector up properly. A developer is needed for refunds and partial refunds, bundles, company price lists, several warehouses or a custom store, which ready connectors usually miss.
Stores: WooCommerce, PrestaShop, Shopify and custom stores. Back office: Holded, Odoo, A3, Sage and other ERPs with an API or a file exchange. Payments: Redsys, Stripe, Bizum through the gateway, PayPal. I check what each system's API allows before quoting.
Yes, if the shop's stock lives in Holded, Odoo or your ERP. The store reads it on a schedule or on change, so it does not sell products that are gone.
Yes. If Holded or your ERP already complies with VeriFactu, issuing all invoices there and letting the store send it orders and refunds is usually the simplest path. The details are on the VeriFactu integration page.
Tool subscriptions are paid separately.
With care, I update the integration. Without it, the documentation shows another developer what to change. Alerts tell you straight away when a sync fails.
You do. API keys, accounts and code are in your name, and each flow is documented.