Webshop & ERP Systems

Who it's for

Businesses where the webshop works, but everything behind it is fragile — stock mismatches, manual fixes, unclear flows between systems, or constant edge cases nobody wants to touch. Especially where multiple tools have been added over time (storefront, ERP, payments, shipping) and nobody fully trusts how they interact anymore.

What we actually build

A working system around your webshop — not just the storefront. Designed so it keeps working under real conditions, not just in ideal flows.

• Order flow Checkout → backend → fulfillment, end to end, with every state change tracked and recoverable.
• Inventory synchronization Stock levels consistent across every system that touches them — not "eventually correct" hours later when someone notices.
• Payment & refund handling Payments, captures, refunds and disputes handled cleanly — including what happens when any of them fail mid-flight.
• Shipping & status updates Carrier integration, tracking, and status propagation back to the store and the customer without someone manually chasing it.
• Data consistency between systems Orders, stock, customers and statuses aligned everywhere — no silent divergence between what the store, ERP, and finance think is true.
• Failure handling What happens when something breaks — retries, dead letters, alerts, and recovery paths that actually work without a human stepping in every time.

What's included

• System design How storefront, backend, payments, and operations fit together — including the trade-offs we're making and why.
• Integration layer APIs, queues, or direct connections between systems — designed to avoid silent failures and half-committed state.
• Data consistency Orders, stock, and statuses that match across systems — not "eventually correct", not "usually fine".
• Failure handling What happens when payments fail, APIs time out, or systems desync — and how the system recovers on its own.
• Operational setup Monitoring, logging, and visibility into what's happening behind the scenes so problems show up early.
• Documentation & handover How the system actually works — not just how it was supposed to — so the next person can operate it without guesswork.

Typical problems we fix

Every webshop setup has its own quirks, but these show up almost every time. Most of them don't show up in dashboards — they show up in operations.

• Orders placed but not processed correctly Partial writes, missed webhooks, silent drops — a customer paid, but nothing happened downstream.
• Inventory drifting between webshop and ERP Stock levels out of sync, overselling, or phantom stock blocking legitimate orders.
• Manual fixes required daily Someone on the team quietly patching data by hand every morning just to keep the system running.
• Refunds or cancellations breaking flows The happy path works. The unhappy path leaves the system in a state nobody designed for.
• Shipping and tracking out of sync Customers asking where their order is, while the store says "fulfilled" and the carrier has nothing on record.
• Systems "working" but nobody trusts them Everything runs, but every change is terrifying because nobody knows what it'll break.

What you walk away with

What you have at the end of the engagement:

• Orders, stock and payments aligned across systems One source of truth per data type, with clear sync rules and explicit failure modes.
• A clear flow from checkout to fulfillment Every state transition visible, traceable, and recoverable.
• Fewer manual interventions The daily data-patching routine either disappears or turns into a short, boring weekly check.
• Issues visible early instead of discovered later Alerts tuned to the real failure modes, not to default metrics nobody looks at.
• A system your team actually understands No hidden glue logic, no fragile integrations, no "ask Marcel, he wrote that script three years ago".

Typical structure

Most setups end up looking something like this — regardless of which tools you choose:

• Storefront What the customer sees and interacts with.
• Backend / API Where orders, customers, and business logic live.
• ERP Inventory, suppliers, finance, and back-office operations.
• Payment provider Capturing, refunding and disputing — with proper state tracking on your side.
• Integration layer The part that makes all of the above actually work together reliably.

Tools we work with

Tool choice depends on your needs — the system design matters more than the platform. Common setups include:

Also external logistics · ERP backends · custom integration layers