Total integration with the sales front end
The online shop had to be intricately connected to the ERP, with total integration for streamlined operations rather than a nightly file exchange between two versions of the truth.
Case study · ERP development · Channel integration
Eden ERP + Channels Module: one system at the centre of the business
Eden Technology runs on an ERP it owns rather than one it licenses. Bintime developed that system and the channels module that connects it to every place Eden sells — five years, one six-person team.
- 6
- People on the Bintime team
- 5 yrs
- Partnership period, 2018–2024
- 15K+
- Customers served by the client
- 3
- Systems built for Eden: ERP, PIM, webshop
About the client
A reseller that decided to own its core system
Eden Technology sells to consumers from Barcelona and serves more than 15,000 customers. Its operations run on an ERP built for the company rather than bought off the shelf — which is why every other system in the landscape has to be built around it.
This engagement is the foundation of the three Bintime projects for Eden. The ERP and its channels module came first, the PIM followed, and the B2C webshop was built last, consuming both.
- Industry
- E-commerce · B2C · Retail
- Location
- Barcelona, Spain
- Partnership period
- 2018 – 2024
- Team size
- 6 people
Services
Expertise delivered
Technologies
Business challenges
An operational core that has to serve every channel
An ERP is judged on what it prevents: double entry, wrong stock, orders that arrive somewhere nobody is looking. Eden needed all of that solved while the business kept trading across several channels.
Legacy system obsolescence
Outdated parts of the landscape had to be brought up to modern standards, improving functionality and the experience of the people working in the system daily.
Selling in several places at once
Stock, prices and orders across multiple channels cannot be maintained per channel by hand. The channels module had to make that one process instead of several.
Reducing marketplace dependency
Moving a significant portion of sales from marketplaces to Eden’s own channels required the ERP to support that shift operationally, not just commercially.
Approach
Client-centric design, security-minded engineering
The work was characterised by a client-centric design philosophy, with design taking place in close collaboration with Eden rather than at arm’s length. Development was meticulously aligned with the client’s specifications and requirements.
Security-minded design and development practices were ingrained throughout the lifecycle — an ERP holds the company’s commercial data, so robust measures belong at every stage rather than in a final review. Combined with iterative delivery, that is what carried the system through five years of continuous evolution.
Delivery modelSix-person team covering ERP development, DevOps, QA/QC and technical documentation, with the client's product owner setting direction.
- 01
One source of truth. Stock, orders and customers live in the ERP; every other system reads from it instead of keeping its own copy.
- 02
Channels as a module, not as forks. Each channel is configuration on one integration layer, so adding a channel does not mean another codebase to maintain.
- 03
Search and cache in front of the data. Elastic and Redis keep the back office responsive as the order and product volume grows.
- 04
Security at every stage. Secure-by-design practices in specification, code review and release, applied to a system holding commercial data.
- 05
Documented as it was built. DevOps, QA/QC and technical writing sat inside the team, so the platform stayed handover-ready throughout.
Value delivered
What the ERP and the channels module do
A centralised operational platform
The ERP provides one place for business operations, so inventory, orders and administration are answered by the same system rather than reconciled between several.
Efficient store management
A dedicated back office streamlines inventory management, order processing and day-to-day store administration for the people who work in it all day.
Channels module
Sales channels are connected to the central system, so stock, prices and orders flow both ways instead of being maintained separately per channel.
Operational streamlining
Combined, the features optimise business processes and free staff time that used to go into moving data between systems by hand.
What contributed to success
Four things that made the difference
Precision in KPIs
A meticulous focus on KPIs was the bedrock of consistent delivery across five years of releases.
eCommerce industry mastery
Sector experience translated into solutions that navigate retail-specific nuances instead of discovering them mid-project.
Client-centric navigation
Client leadership set the direction, and the work 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.
The wider landscape
Three systems, one team
The ERP is not a standalone deliverable. It is the layer the other two Eden projects were built against, which is why they integrate rather than exchange files.
ERP + channels module
Inventory, orders, administration, and the integration layer to external sales channels.
PIM
Product content, supplier content integration, and the rules that construct titles and specifications.
B2C webshop
The storefront and its back office, fully integrated with the ERP and consuming PIM content.
FAQ
Questions we get about ERP projects
Why build a custom ERP instead of buying one?
Because Eden’s operations — and later its PIM and webshop — were built around the ERP. Owning it means the process defines the software; a packaged system would mean fitting the process to somebody else’s model and paying for integration anyway.
What does the channels module do?
It connects the ERP to the channels Eden trades on, so stock, prices and orders move between the central system and each channel instead of being maintained per channel.
How does the ERP relate to the PIM and the webshop?
The ERP is the operational core, the PIM owns product content and its rules, and the webshop is the storefront consuming both. All three were built by the same team for the same client.
How long did the engagement run?
2018 to 2024: five years with six people covering ERP development, DevOps, QA/QC and technical documentation, delivering continuously.
Which technologies were used?
PHP and Java, MongoDB, Redis for caching and Elastic for search, with DevOps inside the team covering environments, deployment and monitoring.
Can you take over an ERP somebody else built?
Yes, and it is a common starting point. The first step is documenting what the system actually does today, which is usually where the surprises are.
Start a conversation
Is your ERP holding the business back?
Tell us what your ERP does today and where it stops. We come back with an integration approach, a modernisation path and a team shape.
- 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.