Home / Development & Technology / E-commerce
Development & Technology — E-commerce solutions
Shop structure, product presentation, checkout and the integrations behind them — in Magento or WooCommerce. One team in Nijmegen, scope agreed before anyone writes code.
Let's start building →An e-commerce agency builds and maintains the shop: platform choice, catalogue structure, product presentation, checkout, and the connections to stock, prices and fulfilment. At Bumpp that means Magento or WooCommerce, chosen once the catalogue is clear, with the website and the shop handled by one team.
Products get added, prices change, orders are picked and returns come back. A webshop earns its keep when those jobs take minutes rather than an evening.
That is decided by the catalogue structure, the integrations and the admin — all of which are settled before any design is approved.
The build gets the shop live. The second half is what happens once orders start arriving.
Catalogue first, design second. How products group, what varies, where the price comes from and what the customer has to choose — those decisions shape every template that follows.
A shop is measured rather than finished. The work moves to the pages that carry the money: category, product, cart and checkout, in that order.
The platform is chosen once and paid for every month afterwards, so it follows the catalogue and the pricing rules.
Suits a content-led brand with a manageable catalogue and straightforward pricing, where the site and the shop are the same thing and your team already works in WordPress.
Suits a shop that is the business: thousands of products, pricing per customer group, several storefronts or languages, and stock and prices that live in an ERP.
Plenty of Dutch businesses sell to consumers and to trade accounts from the same catalogue. As a digital agency, e-commerce work like this is where the hours are won back — one catalogue underneath, two experiences on top.
No phase starts before the previous one is signed off, which is what keeps a build from drifting. Click through to see what happens and what we need from you.
A scope document, four signed-off templates, a shop filled with your own catalogue, and a set of test orders placed end to end. Each one is approved before the next phase opens.
Let's explore the opportunities to grow your business with a strategy built around your goals.
Different shape of project, run the same way.
Content-led sites in WordPress or Magento — structure, design, build and the SEO basics, handed over so your team can run it.
See websites → ServiceWhen the job is a process rather than a page — portals, dashboards and workflow tools, inside your systems or standalone.
See web applications → ServiceApps built around a customer journey or an internal process, from concept and testing through to optimisation.
See mobile apps →WooCommerce suits a manageable catalogue with straightforward pricing inside a content site your team already runs. Magento suits thousands of products, pricing per customer group, several storefronts or an ERP behind the shop. Catalogue size and pricing rules usually decide it, and the reasoning goes in the scope document.
Three things move the figure: catalogue complexity, how many systems the shop connects to, and whether B2B pricing is involved. A hundred products with one price each is a different project from customer-group pricing fed by an ERP. You get a fixed figure after the scope phase.
Product data usually sets the pace. Photographs, descriptions, variants and attributes have to exist before the shop can be filled, and that work often sits with you. The phase plan you receive after scoping includes the product-data deadlines alongside the build.
Yes, where an API or a scheduled export exists — and it is the first thing we check, because it shapes the whole build. Stock, prices, products and orders moving automatically is routine work. What gets decided early is which system is the source of truth for each.
Yes, and it is usually lighter to run than two separate shops. Customer groups give trade accounts their own prices, net or gross VAT display, payment terms and a login-only catalogue if you want one, while consumers see a normal shop. Magento handles this natively.
Rankings are handled with a redirect map built before launch: every category, product and content URL mapped to its new equivalent. Order history and customers are migrated as data, with their own testing round. Both are planned in the scope phase and scheduled into the launch.
A short call usually answers more than a form — platform, catalogue, integrations or timing.
Ask a question →