The starting point
In 2010 an accountancy firm referred us to Mundo do Futebol. The company sold sporting goods online and faced a classic problem: the online shop, hosted on an e-commerce platform, and the ERP the company used did not talk to each other. Every order was retyped by hand. The stock on the site was permanently out of step with the real stock.
Another developer had already tried to solve it and could not.
The obstacle
The e-commerce platform’s API existed and was documented. The ERP was the problem.
The ERP vendor’s support did not cooperate. The documentation we received did not match the installed system. After weeks with no progress down that road, it was clear the integration would not come from there.
One alternative remained: understand the system from the inside.
The turning point
With the client’s authorisation, we began a complete mapping of the ERP’s SQL Server database — on the company’s own database, in its own environment.
There were hundreds of tables. Some with more than 150 fields. No data dictionary, no reliable reference.
The method was painstaking and stubborn: whole days beside an employee of the company, running test sales and entries while we watched, record by record, what the system wrote. That is how we identified the tables for products, grids, branches, sales, sale items, finance, stock movements and the internal sequence controls — along with the relationships and foreign keys that tied it all together.
At the end we had what the vendor never supplied: the ERP’s data model, documented.
What was built
Order Integrator. It pulls orders from the site through the API — including size and colour grids, personalisation, customer details and payment methods — and writes them straight into the ERP database. The order appears on the system screen ready to invoice and dispatch. The customer record arrives complete; if it already exists, it is updated automatically.
A detail of the business: Mundo do Futebol sells personalisation — the customer pays an extra fee and receives their team’s shirt with their own name on it. That piece of data has to cross the whole chain intact, from the basket to production.
Stock Monitor. It reads stock in the ERP and updates it on the site, for thousands of products, in two complementary modes: incremental mode processes only products with recent movement, keeping the site close to real time through the day; full mode sweeps the entire database, recording the queue of products to update in an auxiliary table — if anything interrupts it, the process knows exactly where it stopped and resumes from there.
Both modes respect the size and colour grid. And when the monitor finds a product that does not yet exist on the site, it automatically creates the skeleton of the record — leaving the person in charge only the photos and the description to complete.
The problem that nearly sank it
The platform’s API had an hourly request limit. Past the ceiling, access was blocked.
Left untreated, that would have meant tasks halted halfway, inconsistent updates and a solution nobody would trust.
The answer was architectural: the whole package — Integrator and Monitor — was built on controlled time cycles. When the API blocks, when the internet drops or when the server goes down, the system does not fail: it waits, retries at each interval and recovers on its own as soon as the environment returns, picking up from the exact point.
This was designed in 2010, long before any AI tool existed.
The real proof: fifteen years of change
A well-built integration is measured by what it withstands.
- 2010
First generation. Online shop on an e-commerce platform with an API, integrated with the client’s ERP on SQL Server. Built in C#.
- 2011
The client replaced the platform with their own site on MySQL. Integrator and Stock Monitor rebuilt for the new architecture.
- 2015
A major ERP upgrade to a new main version, with deep structural changes to the database. A new generation of systems was developed.
- 2024
Back to the Fast Commerce platform. Fourth generation of the integration, adapted to the current API.
Result
Since 2010, Mundo do Futebol has never retyped an order again.
Four platforms, two ERP versions, two different databases, fifteen years of continuous operation — and the same technical partner from the first day until today.
Have a similar scenario? Let us talk.
Talk to Expert