Services · frontzen.com
E-commerce tooling
Tools that take the manual work out of running a store — barcode scanning and label printing in the warehouse, configurators and product designers on the site, ERP and print-pipeline integration.
- Warehouse tools — scanning, labels
- Product configurators and designers
- ERP, inventory and accounting integration
- Print and production pipelines
Most of the money leaks around the store, not in it
Plenty of companies don’t need a new online store. They need less manual work around the one they have — orders retyped between systems, labels printed one at a time, exports to a spreadsheet, production files assembled by hand in a design tool.
That’s what I build. The store stays where it is. And when the platform itself is genuinely the constraint, I build the replacement too.
Tools for your operations team
- Warehouse and dispatch — barcode scanning on a phone or a handheld terminal, bulk label and packing-slip printing, receiving, cycle counts.
- Order operations — batch processing, statuses, notifications, returns. No retyping between systems.
- ERP and accounting integration — through an API, not a nightly CSV export.
- Production — straight from order to a print or production file in the right format, bleed and color space.
Tools for customers on the site
- Product configurators — customers assemble a variant and see the price and the result immediately.
- Print designers and personalization — upload artwork, position it, preview it on the product. Production receives a ready print file.
- Calculators and quote forms — for products that can’t be sold with a single “buy” button.
Experience from heavy traffic
I am the lead platform engineer on a multi-supplier ticketing platform whose catalogue runs to 27,000+ products across 720+ cities from four suppliers, with around 40,000 indexable URLs. I built its SSR engine and its edge routing. Checkout, payments, real-time inventory and SEO at that size are exactly where e-commerce breaks.
Custom commerce on Medusa
When processes have outgrown Shopify or WooCommerce, I build headless commerce on Medusa.js — open source, TypeScript, and a data model you can shape to the business instead of the other way round. I’ve written and published an open-source payment provider for Medusa v2, so the checkout and payment layer is a part of Medusa I’ve worked in at the source level rather than read about in the docs: capture and authorization flows, webhook verification, refunds, and reconciliation against the order. That gateway is a European one, but the provider interface is the same one Stripe and Stripe Connect implement — which is what a US build runs on.
How the engagement works
Fixed price against a written scope, billed 50/50 or across milestones. Intellectual property assigns to you on final payment, you keep the source code, and delivered scope carries a 30-day bug-fix warranty.
When it makes sense
- Manual work is piling up around your store and could be automated
- You need a configurator, product designer or print-ready output
- You want the store connected to ERP, inventory or production
How this works
- 01
Where the time goes
I walk through your operation and find where things get retyped, printed one by one, or exported to a spreadsheet.
- 02
Designing the tool
The smallest tool that removes that pain. With scope and price, not a wish list.
- 03
Iterative development
Working builds throughout — on real data and real devices, not a demo.
- 04
Rolling it out
Training the people who will use it daily. Warehouse and office alike.
- 05
Running and evolving it
I maintain it, or hand it cleanly to your team. The source code is yours.
What you get
- The tool deployed in your infrastructure
- Integration with your platform via API
- ERP, inventory, accounting and carrier integration
- Print and production files from the configurator
- Source code you own — IP assigns on final payment
FAQ
Do you build custom online stores?
Yes — headless commerce on Medusa.js when your processes have outgrown an off-the-shelf platform. But most of my e-commerce work is the tooling around a store you already run, because that's usually where the money is leaking. I'll tell you which of the two you're actually looking at before you spend anything.
What counts as an "e-commerce tool"?
Anything around selling that removes manual work. In the warehouse: barcode scanning, bulk label and packing-slip printing, receiving. On the site: a product configurator or print designer that shows the customer the result and sends production a ready print file. Behind it: integration with ERP, accounting or carriers.
Does this work with my existing platform?
Yes — that's the whole point. I build on top of what you already run, through your platform's API. The store stays where it is; the manual work around it goes away.
Can you handle print and production files?
Yes. Generating production data from a configurator — vectors, print-quality PDFs, correct bleed and color space — is one of the places this most often breaks, and where manual work costs the most.
How much does e-commerce tooling cost?
Tooling projects start at $10,000; a full headless commerce build starts at $20,000. Fixed price against a written scope after a short consultation, billed across milestones.