Total integration with an own ERP system
Eden grappled with the intricate task of developing an online shop intricately connected to their ERP system, so operations stay streamlined and business efficiency is not traded away for a nicer front end.
Case study · B2C e-commerce · ERP integration
Eden Online Shop: a custom B2C webshop built around the client's own ERP
Eden Technology, a Barcelona-based reseller, was selling through marketplaces on top of an obsolete eCommerce system. Bintime built a new webshop from scratch, wired it into Eden's own ERP, and gave the business a sales channel it controls.
- 6
- People on the Bintime team
- 2 yrs
- Partnership period, 2021–2024
- 15K+
- Customers served by the client
- 1 ERP
- Own system, fully integrated
About the client
A Spanish reseller that outgrew its platform
Eden Technology sells to consumers from Barcelona and serves more than 15,000 customers. Its operations run on an ERP system the company built for itself, which is an advantage for control and a constraint for anything that has to talk to it.
By 2021 the existing eCommerce system had fallen behind modern standards, and a growing share of orders was arriving through marketplaces. The brief was not a redesign. It was a new shop that Eden owns, integrated end to end with the systems already running the business.
- Industry
- E-commerce · B2C · Retail
- Location
- Barcelona, Spain
- Partnership period
- 2021 – 2024
- Team size
- 6 people + 0.25 FTE tech writer
Services
Expertise delivered
Technologies
Business challenge
A new shop, an own ERP, and a legacy system to leave behind
Each of these is a project on its own. Eden needed them solved together, on a business that had to keep selling while the work happened.
Legacy system obsolescence
The outdated eCommerce system had to be brought up to modern standards — better functionality and a user experience that matches what shoppers now expect.
Building a new webshop from scratch
Starting with a blank slate meant careful planning and technical expertise were needed for the transition to be both successful and seamless.
Reducing marketplace dependency
A significant portion of sales had to move from marketplaces to the new webshop, diversifying channels and reducing dependence on external platforms.
Approach
Client-centric design, security-minded engineering
The approach was characterised by a client-centric design philosophy, with design work taking place in close collaboration with Eden’s product owner and designer rather than at arm’s length.
Development was meticulously aligned with the client’s specifications and project requirements. Security-minded design and development practices were ingrained throughout the lifecycle, so robust measures were implemented at every stage rather than reviewed at the end. Client collaboration, iterative delivery and that security emphasis are what carried the project through two years of continuous evolution.
Team compositionBintime: team lead, 2 PHP developers, 1 frontend developer, manual QA, project manager, technical writer (0.25 FTE).
Eden: 1 product owner, 1 designer.
- 01
MVP first. A working shop in production early, then features added release by release instead of one long build with a single launch date.
- 02
Design with the client. Eden’s designer and product owner worked directly with the team, so decisions were made once and not re-litigated in review.
- 03
ERP as the source of truth. RabbitMQ messaging between shop and ERP, with Redis caching and Elastic search so the storefront stays fast without duplicating data.
- 04
Security at every stage. Secure-by-design practices in specification, code review and release, not a penetration test bolted on at the end.
- 05
Documented as it was built. A technical writer on the team meant the platform stayed handover-ready throughout, not documented retroactively.
Value delivered
A shop, a back office, and one platform behind both
Four outcomes, each of which removed manual work from somebody’s day.
Enhanced user experience
Standard webshop features, implemented properly, add up to an online shopping experience customers can actually complete.
Efficient store management
A dedicated back office streamlines inventory management, order processing and day-to-day store administration.
Integrated ERP system
The ERP integrated into the webshop’s backend gives one centralised platform for business operations instead of two that need reconciling.
Operational streamlining
Combined, the features optimise business processes and free staff time that used to go into moving data between systems.
What contributed to success
Four things that made the difference
eCommerce industry mastery
Sector experience translated into tailored solutions that navigate the nuances of retail commerce instead of discovering them mid-project.
Precision in KPIs
Agreed KPIs were the reference point for every release, which is what keeps a two-year engagement pointed at business outcomes.
Client-centric navigation
Client leadership set direction; the team aligned to Eden’s strategic vision rather than proposing a parallel one.
Collaboration with proactive clarity
Transparent communication and proactive suggestions that went beyond the technical brief into how the business could work.
Expanding cooperation
Where the project stands now
With release behind it, the focus has shifted to the customer profile: order history and the other personalised elements that make a returning shopper’s second visit easier than their first.
Purchase history in particular is there to deepen engagement and loyalty — a more personal, user-centric shop, developed on the platform already in place.
FAQ
Questions we get about webshop and ERP projects
Why integrate with an own ERP instead of using a standard connector?
Because stock, pricing, orders and customers already live there. The ERP stays the single source of truth and the shop reads and writes to it, which removes duplicate data entry and manual reconciliation.
How long did the project take?
2021 to 2024: roughly two years of active development, starting from an MVP, followed by continuous delivery.
What did the team look like?
Six people from Bintime — team lead, 2 PHP developers, 1 frontend developer, manual QA, project manager, plus a technical writer at 0.25 FTE — with a product owner and designer on the client side.
Which technologies were used?
PHP and JavaScript, MongoDB, RabbitMQ for messaging with the ERP, Redis for caching and Elastic for search, with DevOps as a service covering environments and deployment.
Can a new webshop really reduce marketplace dependency?
That was an explicit goal here: move a significant portion of sales from marketplaces to Eden’s own shop, diversifying channels and reducing exposure to external platforms and their fees.
Do you replace a legacy shop in one release?
No. An MVP goes live first, then functionality is added incrementally, so the business is never waiting on a single cut-over date.
Start a conversation
Own ERP, ageing shop, sales locked into marketplaces?
Tell us what your stack looks like today. We come back with an integration approach, a team shape and a first release you can put in front of customers.
- Reply within 24 hours from someone who can scope it
- Reference calls with existing clients, where they agree
- NDA signed before any detail is shared
Thank you
We will get back to you within 24 hours with next steps.