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.
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 — since 2018, one six-person team.
Eden Technology
Visit the client’s siteEden 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.
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.
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.
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.
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.
Moving a significant portion of sales from marketplaces to Eden’s own channels required the ERP to support that shift operationally, not just commercially.
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 continuous evolution since 2018.
Stock, orders and customers live in the ERP; every other system reads from it instead of keeping its own copy.
Each channel is configuration on one integration layer, so adding a channel does not mean another codebase to maintain.
Elastic and Redis keep the back office responsive as the order and product volume grows.
Secure-by-design practices in specification, code review and release, applied to a system holding commercial data.
DevOps, QA/QC and technical writing sat inside the team, so the platform stayed handover-ready throughout.
“Six-person team covering ERP development, DevOps, QA/QC and technical documentation, with the client’s product owner setting direction.”
The ERP provides one place for business operations, so inventory, orders and administration are answered by the same system rather than reconciled between several.
A dedicated back office streamlines inventory management, order processing and day-to-day store administration for the people who work in it all day.
Sales channels are connected to the central system, so stock, prices and orders flow both ways instead of being maintained separately per channel.
Combined, the features optimise business processes and free staff time that used to go into moving data between systems by hand.
A meticulous focus on KPIs was the bedrock of consistent delivery across every release since 2018.
Sector experience translated into solutions that navigate retail-specific nuances instead of discovering them mid-project.
Client leadership set the direction, and the work aligned to Eden’s strategic vision rather than proposing a parallel one.
Transparent communication and proactive suggestions that went beyond the technical brief into how the business could work.
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.
This case · since 2018, ongoing
Inventory, orders, administration, and the integration layer to external sales channels.
Since 2018, ongoing
Product content, supplier content integration, and the rules that construct titles and specifications.
Read the PIM case2021–2024
The storefront and its back office, fully integrated with the ERP and consuming PIM content.
Read the webshop caseBecause 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.
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.
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.
Since 2018, ongoing, with six people covering ERP development, DevOps, QA/QC and technical documentation, delivering continuously.
PHP and Java, MongoDB, Redis for caching and Elastic for search, with DevOps inside the team covering environments, deployment and monitoring.
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.
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.
We reply within one business day.
We will get back to you within one business day with next steps.