We build it end to end
A defined scope, delivered in releases you can test. We own delivery from discovery to go-live.
Best for a new system or a rebuild
ServicesWeb applications
Storefronts, product catalogues and checkouts on Magento, WooCommerce or a headless setup, joined to the ERP, the marketplaces and the carriers behind them. For retailers and distributors whose store has outgrown its template, or whose stock and orders do not match between systems.
Request a quoteFrom our clients
An Italian pharma company brought KTree in to make their web applications fast.
What you get
A storefront designed for phones first, with your catalogue, categories, filters and product pages. We have built stores with several languages and store views, separate prices for wholesale and retail customer groups, gift cards, vouchers and delivery time slots. The code, the data and the hosting accounts are yours.
A short checkout connected to your payment provider and your carriers. Past stores were connected to Adyen, PayPal and Paytm for payments, and to bpost, DHL, FedEx and ShipStation for labels and tracking. Returns are handled through a returns (RMA) process in the store.
Products, prices, stock, orders and invoices move between the store and the ERP without retyping. We have linked Magento to Microsoft Navision and to Odoo, WooCommerce and Amazon to Odoo, and stores to Amazon, eBay and Bol.com so one catalogue sells on every channel. Stores have also been linked to point-of-sale systems in the shops.
Page caching, Redis, a tuned web server and a CDN, a network that serves images and files from a location near the shopper. Search on Elasticsearch where the catalogue is large. An admin dashboard with sales, tax, low stock and coupon reports, and support after launch.
How it works
A store sells well when the stock it shows is true, the checkout is short and the pages load quickly. We design those three things first and choose the platform to suit them.
Your options
Shopify and similar services are the quickest way to start selling, with hosting and security included. They are the right choice for a standard shop. They get harder when you need your own checkout rules, deep ERP links or pricing by customer group, and the monthly and per-sale fees grow with you.
Amazon and eBay bring buyers from the first day with no site to build. The marketplace owns the customer and sets the fees and the rules, so most sellers keep it as one channel and not the only one.
Low cost and fine for a small catalogue. The limits show when stock has to match an ERP, when traffic peaks, or when the one person who knows the store is not available.
One engineering team builds the store, the integrations and the hosting, and supports them after launch, at a fixed price when the scope is clear. You own the code, the data and the hosting accounts.
Not praise. The problem, what we built, and what changed.
Technology
Ways to work with us
A defined scope, delivered in releases you can test. We own delivery from discovery to go-live.
Best for a new system or a rebuild
Odoo, React, Node, React Native, AWS and PHP engineers who work as part of your team, month by month.
Best for a product that keeps growing
Maintenance, upgrades and urgent fixes for ERP, web and cloud systems, including ones we did not build.
Best for a system already live
Industries
Related reading
Before you ask
Short, straight answers. Anything else, ask in the form below and an engineer will reply.
It depends on the catalogue, the integrations and who will run the store. WooCommerce suits a smaller catalogue beside a content site. Magento suits a large catalogue with several stores, languages or customer groups. A headless build suits a business that wants its own storefront on top of a commerce back end. We recommend one after seeing your products and the systems the store must connect to.
Yes. Products, stock, prices, orders, invoices and shipments can sync in both directions, so nobody retypes an order. We have done this with Odoo and Microsoft Navision, and with point-of-sale systems.
Yes. We list the custom code, the extensions and the theme changes first, then move the database, replace or rewrite the extensions and test every scheduled job before the switch. We did this for a book publisher moving from Magento 1 to Magento 2.
Yes. The store or the ERP holds the products once and publishes them to each channel, and orders and stock from every channel come back to the same place.
You own the code, the data and the hosting accounts. After launch we can stay on for maintenance, upgrades and urgent fixes under a support plan, including for stores we did not build.
Request a quote
A senior engineer replies within one working day.