Online stores
A store with couriers, payments, and ERP connectivity. InPost, PayU, BLIK, and a catalog, rather than a template left on a shelf.
Transparent Investment Ranges // Engineering Standard
A fixed price agreed before work begins, based on the audit. No hidden costs or endless hourly billing.
The first tangible production result in your business. I focus on one critical process, eliminating risk and delivering working software in a fraction of the usual time.
- Custom e-commerce frontend (Next.js / Headless)
- B2B customer account with individual discounts
- Payment integration: PayU, BLIK, Stripe
- 30-day stability warranty and post-launch support
A comprehensive platform for the entire organization. Advanced decision loops, deep two-way database integrations, complete audit logging, and dedicated engineering support under an SLA.
- Custom e-commerce frontend (Next.js / Headless)
- B2B customer account with individual discounts
- Payment integration: PayU, BLIK, Stripe
- Delivery integration: InPost, DPD, Raben, Schenker
- Inventory synchronization with ERP
- Priority SLA, 24/7 monitoring, and architect support
Online Store / B2B E-Commerce in practice
Engineering approach and system architecture
I solve business problems by starting with the process. No rigid ready-made templates: I build software around your procedures.01 // MODULE
Who I build online stores for
For companies that want to sell through a real checkout: catalog, payment, courier, and, when needed, an ERP record. Not for someone looking for a brochure site with a PDF price list.
Scope Catalog and variants, customer account, cart, delivery, payments, feeds and an ERP connection if you already use that system. What you receive
02 // MODULE
A store that accepts an order and ships it
WooCommerce stays if it still supports sales. I build a custom store when the standard platform limits the checkout, shipping, or ERP integration. I choose the stack to fit the catalogue and what you already have.
Catalog, variants, account, and a cart customers can buy from
The couriers you already ship with, rather than a brochure list
03
Payments your accounting team will accept
BLIK, bank transfer, card or the payment provider you already use
04
ERP connection
when orders need to enter the system you already have. Process
03 // MODULE
How I take a store through to its first order
01
Purchase journey
I map the product range, prices, and every customer click from product page to confirmation.
02
Payments and couriers
One working checkout:
payments plus the courier or parcel locker provider you already use.
03
ERP or order dashboard
If an ERP exists, orders go to it.
If not, a dashboard for the office to manage shipments and statuses. Stores already in operation
04 // MODULE
These are real stores I have delivered, rather than a brochure offering
Below is only what appears in the case studies. I do not add brands from market comparisons. For a general explanation of store-to-ERP connections, see the separate post about integrating a store with a business management system.
01
RehaTop: A Custom Store Instead of Shoper
RehaTop moved from the closed Shoper platform to its own store: an Astro SSR storefront, an Express/Prisma API and a React dashboard. Customers can pay by bank transfer, BLIK, card and PayU. P24, PayPal and cash on delivery can also be added to checkout. Implemented delivery options include GLS courier, GLS cash on delivery, InPost parcel lockers and local pickup. Google Merchant and Ceneo and Facebook feeds are included. Subiekt is an API integration target, not a delivered accounting system. This case is relevant when Shoper or another off-the-shelf platform falls short at checkout, delivery or the dashboard. I start with a store your office can actually run, rather than a lecture about the stack.
02
WooCommerce for an Importer and Malta Trading
For a sportswear importer (NDA, 2023), I kept WooCommerce with Elementor.
I integrated Przelewy24, BLIK, and Stripe, along with InPost, DPD, and DHL. There was no ERP. The project also includes a catalog and RFQ requests, rather than just a single-item shopping cart. Malta Trading moved from its old WordPress/WooCommerce setup to its own store and CMS. Payments use Stripe. Delivery: courier service throughout Poland, free above a threshold, and collection from the showroom in Poznań; no courier brand is specified. Catalog: 627 products and 11 categories. This project has no ERP. Woo stays when it still sells. I build a custom store when an off-the-shelf platform blocks the cart, couriers, or ERP.
05 // MODULE
Do you have an ERP, or do you still need one?
An online store means a cart, delivery, payment and passing orders to the system already managing stock and invoices. I do not rewrite your accounting under the guise of e-commerce.
The post about connecting a store to ERP explains how it works in practice. Different paths If ERP already exists, I connect the orders.
If AI needs to work with that ERP, it is a separate implementation, described on the AI ERP/CRM integrations page. If there is no order and inventory system, you need a custom CRM/ERP system, rather than just a store.
Not sure whether Woo is enough, you need a custom store or just a Comarch connection? That is the first conversation, not a price-list choice.
Online store
06 // MODULE
Tell me about your products, courier, and ERP
Tell me what you sell, how you ship it, and whether orders need to enter an existing system. I will return with the scope for your first store, rather than a generic IT proposal.
Book a conversation about your store
What You Receive with the Implementation:
- Custom e-commerce frontend (Next.js / Headless)
- B2B customer account with individual discounts
- Payment integration: PayU, BLIK, Stripe
- Delivery integration: InPost, DPD, Raben, Schenker
- Inventory synchronization with ERP
Technologies and production standards:
I choose technologies for stability, speed, and reliability. No technical debt.
Online Store / B2B E-Commerce
FAQ
Frequently asked questions about online stores / B2B e-commerce — architecture, implementation, data security, costs, and technologies:
01 WooCommerce, a custom store or Shoper — which do you choose? +
WooCommerce stays if it still serves your sales. A custom store makes sense when a ready-made platform blocks checkout, delivery or the dashboard. Shoper only when it truly meets your needs.
02 Which couriers do you integrate? +
The delivery providers you already use. The first release includes one working route. I do not promise GLS, InPost, DPD and DHL in every store.
03 Which payment methods can be connected? +
The one your accounting team accepts and your customers actually use. Each project has a different setup: PayU, Przelewy24, Stripe, BLIK, bank transfer, or card. I do not add everything at once.
04 We already have an ERP. Are you building a new one or connecting the store? +
If an ERP is in place, the store sends orders to it. Adding AI to that ERP is a separate implementation, described on the AI integration with ERP/CRM page. A new system built from scratch belongs to the CRM/ERP system service. I do not build a new accounting system here.
05 How long does it take to reach the first order? +
First, a catalog, one delivery provider, one payment method and a decision on whether ERP receives orders from day one. Timing follows a product review, not a price list.
Start building.
First conversation free.
A free 30-minute technical consultation. After the call, I will provide an architecture proposal, timeline and transparent quote within 24 hours.