Orders retyped by hand
Someone copies data from the store panel into the ERP. At thirty orders a day that is half a full-time job and a steady stream of mistakes in addresses, tax numbers and payment methods.
E-COMMERCE · STORES AND B2B PLATFORMS
An online store that stops creating
manual work.
The store sells, and your team still retypes orders into the ERP, reconciles stock with Allegro by hand and explains to B2B customers why they cannot see their own prices. We design and build PrestaShop stores and custom e-commerce platforms that connect to the systems you already run.
- PrestaShop, WooCommerce and custom platforms
- Integrations with ERP, marketplaces, payments and couriers
- 12 months of warranty and care after launch
FROM OUR PROJECTS
- 120,000
- products migrated along with eight years of order history
- 14
- stores connected to Comarch ERP Optima
- 47
- integrations in a single B2B system for a manufacturer
- 900+
- projects delivered since 2013
SOUND FAMILIAR?
The store works. The trouble starts
after the order is placed.
Stock levels drift apart
The store shows availability that is not in the warehouse, because Allegro and the wholesaler update on a different rhythm. The result: cancelled orders and a falling seller rating.
B2B customers cannot see their prices
Individual price lists, volume discounts and credit limits live in a spreadsheet rather than in the store. Every enquiry goes back to a salesperson instead of turning into an order.
The store runs on an unsupported version
Magento 1, an old PrestaShop or a theme nobody maintains. Every update is a risk, so you make none — and the debt keeps growing until it has to be repaid all at once.
Checkout loses customers
No BLIK, no deferred payment for companies, no parcel locker choice on the final step. The traffic is there, the carts fill up, the transactions do not happen.
Nobody knows what to change next
Analytics is installed but nobody reads it. Decisions about the store are made on instinct, and each change has no numbers to justify it.
If you recognise even two of these, it is usually not a store problem. It is a problem with the missing connections between the store and the rest of the company.
WHAT WE BUILD
Three routes to a store that handles sales and operations at once.
01
PrestaShop stores
We build and develop stores on PrestaShop 8 and 9 — from a first launch to taking over a store someone else built. We also migrate from older versions and other platforms, keeping redirects and search rankings intact.
- PrestaShop 8 and 9
- Modules and themes written for the project
- Migrations from Magento, Shoper, IdoSell, WooCommerce
- Taking over and developing an existing store
02
B2B and custom platforms
For when sales do not fit a standard store: individual price lists, credit limits, minimum order quantities, multi-level customer structures and ordering from your own catalogue or from a file.
- Individual price lists and volume discounts
- Credit limits and deferred payment
- Panels for sales representatives
- Fast ordering from a list or a CSV import
03
Integrations and automation
This is usually where a team gets its time back. We connect the store with the ERP, marketplaces, wholesalers, payments and couriers so an order moves through the company without being retyped.
- Two-way exchange with the ERP
- Stock and price synchronisation
- Automated shipping labels
- Integration monitoring and alerts
INTEGRATIONS
What we usually connect stores to.
Below are systems we have worked with on client projects. If yours is not on the list, it can usually still be connected — through an API or a file exchange.
ERP and warehouse
- Comarch ERP Optima
- Comarch ERP XL
- Subiekt GT
- Subiekt nexo
- enova365
- Symfonia
- WAPRO
Marketplaces and multichannel
- Allegro
- Amazon
- eBay
- BaseLinker
- Ceneo
- Google Merchant Center
Payments
- PayU
- Przelewy24
- Autopay
- BLIK
- tpay
- PayPal
- Instalments and deferred payment
Logistics and couriers
- InPost
- DPD
- DHL
- GLS
- Poczta Polska
- Furgonetka
- Apaczka
Migrations from
- Magento 1 and 2
- Shoper
- IdoSell
- WooCommerce
- Bespoke stores
Marketing and analytics
- Google Analytics 4
- Google Ads
- Meta
- GetResponse
- Mailchimp
- SALESmanago
Cannot see your system? Send us its name. We will check whether it exposes an API and tell you straight whether the integration makes sense.
OUR WORK
Stores we still maintain today.
We do not disappear after launch. Most of the stores we have launched we keep developing with our clients' teams for years afterwards.
Nautilus2
E-commerce · PrestaShop
Online store for e-commerce with a clear catalog and a smooth checkout experience.
Mavibo
E-commerce · PrestaShop · B2B · Manufacturing
Sales platform for a manufacturer, combining e-commerce with B2B customer processes.
Pyzowka
E-commerce · CMS · Manufacturing · Services
Project combining sales, CMS content and the presentation of a production and service offer.
SCOPE AND TIMING
Three typical ways this goes.
Every project is quoted individually, after a conversation about scope. Below are indicative timeframes from projects of a similar size — so you know what kind of horizon we are talking about.
Starter store
6–8 weeks
A new PrestaShop store, launched and ready to sell.
- UX design and theme implementation
- Payment and courier configuration
- Product catalogue import
- One integration: ERP or marketplace
- Team training and handover
Store with integrations
10–14 weeks
A store connected to the systems the company already runs.
- Everything in the starter scenario
- Two-way ERP integration
- Stock and price synchronisation
- Marketplaces and automated shipping
- Data migration from the old store
B2B or custom platform
from 4 months
Sales that do not fit into an off-the-shelf store.
- Sales process analysis and workshop
- Individual price lists and credit limits
- Sales rep and customer panels
- Integrations with multiple systems
- Staged development after launch
A reliable quote cannot be produced from a three-sentence brief. That is why the first step is always a conversation about scope — free and with no obligation.
OR START LIGHTER
Free store audit
Not ready to talk about a project? We will review your store against a twelve-point list: performance, checkout, integrations, SEO, accessibility and security. You get a list of concrete things to fix — including ones you can do without us.
- A twelve-point checklist
- 30 minutes to walk through the findings
- The report is yours, even if we never work together
QUESTIONS
What people ask us most often.
How long does it take to build an online store?
A PrestaShop store with a standard configuration usually launches in 6–8 weeks. A store with ERP and marketplace integrations is typically 10–14 weeks. A custom B2B platform starts from four months. The timeline depends mostly on the number of integrations and on how quickly we receive data and decisions from your side.
What drives the cost of a store?
Integrations and unusual sales logic, far more than the visual design. Two stores with an identical layout can differ several times over in cost if one sends orders to an ERP while the other handles individual price lists, credit limits and four marketplaces. We prepare a quote after a conversation about scope.
Do you integrate stores with Comarch Optima or Subiekt?
Yes. Comarch ERP Optima, Comarch ERP XL, Subiekt GT and nexo, enova365, Symfonia and WAPRO are systems we have worked with on client projects. The integration usually covers a two-way exchange: orders and contractors into the ERP, stock levels and prices into the store.
Will you take over a store built by someone else?
Yes, we do it regularly. We start with an audit of the code and infrastructure so we know what we are actually taking on. After the audit we say plainly whether the store is worth developing or whether migrating to a new version will cost less. Sometimes we recommend the latter.
Does migrating a store mean losing Google rankings?
It does not have to. During a migration we either preserve the URL structure or set up 301 redirects from the old addresses to the new ones, keep metadata and structured data, and watch performance. The largest migration we have delivered covered 120,000 products together with eight years of order history.
Who owns the code after launch?
The client. When the project ends we hand over the repository and the infrastructure access. We do not use licences that tie you to working with us — if you stay, it is because it suits you.
What happens after the store goes live?
Every launch includes 12 months of warranty. Beyond that we offer SUPPORT agreements with monitoring and a guaranteed response time. 78% of our clients stay with us for more than five years, and our longest relationship has run since 2016.
Do you only work in your own region?
Our office is in Rzeszów, but we run projects remotely across Poland and abroad. We work in Polish, English and German, and meetings are held online — with the option of an on-site visit for larger projects.
LET'S TALK
Tell us what does not add up.
Describe in a few sentences what the store runs on and what your team still does by hand. We reply within one working day — with specifics and questions, not a twenty-page proposal.