E-Commerce

In e-commerce the visible part is the storefront; the weight of the work sits in the connections behind it. If inventory, accounting, shipping, marketplaces and returns are not properly wired, the operation stumbles no matter how good the store looks.

So in e-commerce projects we start not with the storefront but with where the inventory is held.

Scope

• Store infrastructure — setup, theme and flow design, product structure and variant management
• Payments — payment gateway and provider integration, installment structures
• Shipping integration — creating shipments, tracking numbers, displaying delivery times
• Marketplace integration — synchronizing products, prices and stock across channels
• ERP / accounting connection — order, invoice and account flows
• Returns and exchanges — as a working process, not just a page of text

Inventory consistency is the most expensive error

A product you sold but cannot ship costs you both the order and the customer. That risk compounds in marketplace scenarios where the same stock is consumed through several channels.

One-way, delayed synchronization does not hold up here. Which system is the source of truth, and how often and in which direction updates flow, must be decided upfront. The decision can be changed later, but at a high price.

Mobile is where the design starts

Most shopping happens on mobile. Even so, many stores carry mobile as a narrowed-down desktop; the result is familiar: filters hard to operate with a thumb, checkout spanning three screens, a button that disappears when the keyboard opens.

Where we focus:

• Reducing the number of fields in checkout (not just the number of steps)
• Moving address entry from typing to selection
• Putting search and filtering ahead of the category tree
• Serving images at resolutions matched to the screen

The last one gets overlooked but has the most concrete effect: a slow page is a sale lost before the customer sees the product.

Regulatory compliance is interface behavior

Legal compliance in e-commerce is not a matter of adding a contract page. A significant part of what is required concerns how the software behaves:

• Pre-contractual information given before order confirmation, with its own separate approval
• A button creating a payment obligation stating so explicitly
• The total price including shipping shown clearly before the order
• The right of withdrawal and its exceptions applied correctly per product
• A returns process that works the way the text says it does

Where the text and the system conflict is the first place anyone looks in a dispute, because the commitment written on your site binds you. Since the legal side is also ours, we check these two against each other — see our legal consultancy page for detail.

How we work

We start by mapping the existing operation: how orders arrive, where stock is held, how returns are handled. That flow is what gets digitalized.

After launch we look at measurement: cart abandonment, drop-off at the payment step, searches returning nothing. Those three figures settle most design debates on their own.

Our read on where the sector is heading is in our 2026 e-commerce article.