ETL, Middleware and Real-Time Data Sync
Custom ETL and middleware engineering: we keep stock, price, order and customer data moving between your ERP, CRM, WMS and the systems your business runs on. Audit, pipeline, monitoring. Since 2010, on Magento, Sylius, Symfony and custom applications.
Let's talk about your data
Nobody buys their enterprise stack all at once. The ERP arrived when finance needed control, the CRM when sales expanded, the WMS when the warehouse scaled, and the storefront when online channels took off. Each was the right tool at the right time, and none of them were chosen for how well they would talk to each other.
That gap is where we step in. We build the data pipelines and middleware that keep your systems moving in sync at the precise rhythm each operational workflow requires, backed by robust error handling and reconciliation for when sources conflict.
No off-the-shelf connectors, no recurring subscription fees, and no rented middleware. Just custom engineering built directly against your architecture by experts who understand the nuances behind your data.
Since 2010, Sutunam has designed, built and monitored data integrations across commerce platforms, enterprise systems and business intelligence stacks. Stock, price, product, order and customer data, moving at the frequency each type actually needs.
Before you read on
Two things worth knowing
Most of this market sells a subscription with proprietary connectors. We do not, and it changes what you are buying.
You own what we build
The code, the documentation, the mapping rules and the infrastructure configuration are yours. There is no proprietary connector you keep paying to use, no runtime licence, and no clause that makes leaving expensive.
If your team wants to take the pipeline in-house next year, they can, and the documentation exists to make that realistic. Our application maintenance and support teams are available if you would rather not run it in-house, but that always remains your choice.
It starts with an audit, not a contract
The first step is mapping how your data moves today. That is a scoped piece of work with its own deliverable, and it stands on its own.
If the honest conclusion is that your existing integration is sound and simply needs monitoring around it, we will tell you that, and you will have the map either way.
Symptoms
You already know when you need this
Most of our pipeline projects don't start with someone asking for an ETL. They start with one of these.
Someone begins every day by exporting a file from one system and importing it into another.
Closing the month means reconciling two systems in a spreadsheet, and that spreadsheet has a maintainer.
Your reporting describes yesterday, so decisions get made on numbers everyone quietly distrusts.
The CRM and the ERP disagree about the same customer, and neither side will concede.
A value changes in the system of record and reaches everything downstream hours later, if it arrives at all.
Stock is accurate in the warehouse and wrong on the website, so you oversell.
An integration is running in production and nobody left in the company fully understands it.
One system going down takes something with it that has no business being coupled to it.
Positioning
ETL or PIM? Two different problems
The two get confused constantly. They are complementary rather than interchangeable, and the difference decides where you should start.
Which scenario matches your current operational challenge?
Companies with a product catalogue often need both, and they work well together. The one you need first depends on where the pain actually is.
A PIM problem
Product content is scattered, incomplete or inconsistent. Attributes differ per channel, translations are missing, media lives in five places. The data exists but nobody trusts its quality.
An ETL problem
The data is already correct somewhere, it just isn't where it needs to be yet. Stock, prices, orders and customer records are accurate in one system and stale in every other one.
What a PIM does
Centralises descriptions, attributes, translations and media, enriches them, and publishes a clean catalogue out to every channel.
What an ETL does
Moves operational data between systems on a rhythm tight enough that every system reflects the same reality, and reconciles it when something fails.
If the first column sounds familiar, start with Product Information Management. If the second one does, you're on the right page. The ETL is often what feeds the PIM in the first place.
Approach
Volume, distribution, and the shape of your data
Every data problem has a different shape. French retail chain Bébé9 handed us one of the harder ones: stock spread across more than a hundred independent franchise locations, each moving on its own, with no central point where any of it naturally comes together, and all of it needing to resolve into one number that the outside world can act on.
The reason we cite it isn't the sector. It's that a hundred autonomous sources with no natural consolidation point is the same engineering problem whether those sources are stores, depots, subsidiaries, plants, vehicles or field teams. The pipeline aggregates at the integration layer rather than waiting for a source system to do it, and the commercial definition of "available" gets settled before a single record moves.
Not every business needs that pipeline. A single-source organisation with a nightly update has a genuinely different problem, and pretending otherwise would cost you money. So we start by mapping how your data actually moves today, then define, with you, the frequency, the volume and the failure points that matter most to your business.
Our scope
Audit, build, then watch it
Three phases, from an undocumented data landscape to a sync your team can stop worrying about.
Data mapping and audit
Before any pipeline gets built, we need to understand where your data actually lives, who owns it, and how much of it can be trusted. This phase surfaces the undocumented rules, the manual workarounds and the gaps that a straight migration would otherwise carry forward into the new system, intact.
- Source system and data inventory
- Data quality and consistency review
- Business rule discovery, including the rules nobody wrote down
- Volume, frequency and peak profiling
- Source-of-truth definition, per data domain
- Risk and failure-point identification
Pipeline and integration architecture
Once we know what's moving and how often, we design the pipeline itself. The goal is an integration layer that holds up under real business volume and real failure conditions, not one that works in a demo.
- Pipeline and middleware design
- Product, price, stock, order and customer record synchronization
- Master and reference data alignment
- Document and media flow automation
- Multi-source, multi-destination sync across ERP, CRM, OMS, WMS, PIM and BI
- Event-driven versus batch strategy, defined per data type
- Error handling, retry and reconciliation logic
Monitoring and reliability
A pipeline that fails silently is worse than no pipeline at all. We build in the visibility your team needs to trust the data wherever it lands, and to catch problems before the business does.
- Sync monitoring and alerting
- Data validation checkpoints
- Reconciliation reporting between source and destination
- Performance and load testing under peak volume
- Rollback and recovery procedures
- Ongoing maintenance and evolution, if you want it
Systems
How we integrate, and what with
The competence is the integration pattern, not the logo on the box. We pick the transport based on what a system can actually offer, which is regularly less than its documentation claims, and we work with the systems you have rather than the ones we would prefer you had.
Integration patterns
Systems we sit between
Platforms we have delivered against
Listed as evidence of what we have shipped, not as a boundary on what we will connect to.
Start with a data flow audit
You don't have to commit to a pipeline to find out what's breaking. We map how your data moves today, where the manual steps are, which failures are currently silent, and which flow would pay for itself first. You keep the map whether or not you build it with us.
Data projects we have shipped
More than a hundred independent stock locations, no central point of aggregation, and a number that has to be right for the outside world. How the pipeline resolves a hundred autonomous sources into one trustworthy figure.
On a vehicle marketplace, inventory changes under you constantly. How our ETL keeps LS Group's inventory, availability and pricing consistent between their systems and the Sylius platform customers see.
Read the case studyBehind a Magento 1 to Magento 2 migration sat a data problem: consolidating product, stock and price information from multiple sources into a single centralised flow before anything could move.
Read the case studyFAQ
Questions we get asked
Do I need a PIM, an ETL, or both?
See our PIM expertise
Is this only for e-commerce?
What does "near real time" actually mean?
What's the difference between an ETL and an API integration?
What happens when one of my systems goes down?
Can you work with the integration we already have?
Do you work as a project team or as embedded engineers?
Who owns the pipeline once it's live?
Related
ETL and real-time sync, but also
Custom Developments
Bespoke engineering against your systems, where no product fits the problem.
Product Information Management
Centralise and enrich product content, then publish it everywhere it's needed.
Magento Integrations
Connecting a storefront to the ERP, OMS and CRM systems behind it.
Managed Hosting & IT Outsourcing
A pipeline is only as reliable as what runs underneath it.
Magento Development
Architecture built to carry high-volume, high-frequency data.
Web & Mobile Development
From analysis and architecture through to delivery, across every layer.
Tell us how your systems disagree
Bring us the flow that keeps breaking, the export nobody wants to own, or the integration you inherited. We have probably met the problem before, and if we haven't, we will say so.