Back to all workDate range1 to 7 May Data views3 System statusReady
E-commerce & systems integration
Publisher data sync hub
Making a difficult external data source practical for everyday reporting.
An older third-party platform made repeated reporting awkward and unreliable. We built a secure application that controls the synchronisation, shows progress and gives the team a searchable local copy of the information they need.
Reporting operations
Synchronisation centre
ActivityPeriodStatus
Reporting records1 to 7 MayComplete
Campaign details1 to 7 MayComplete
Banner details1 to 7 MayChecking
Daily scheduled run8 MayQueued
Illustrative sync activity
The requirement
Reporting could not depend on a fragile external interface.
The source could be slow, limit requests or stop part way through a large date range. The business needed a controlled process that could recover sensibly and leave people with a consistent local reporting view.
- Give authorised users control over the reporting date range
- Make progress and recoverable problems visible while a sync runs
- Avoid duplicate or incomplete local reporting data
- Provide searchable click, banner and campaign views
- Keep a clear history of manual and scheduled activity
What we built
Synchronisation treated as a visible business process.
Users can see and control the work instead of starting a hidden import and hoping it completes.
Controlled synchronisation
Users choose a date range, preview the scope and start or cancel the run from one secure workspace.
Visible progress
The interface shows what is happening as information is requested, checked and prepared for local reporting.
Dependable local records
Duplicates and interrupted runs are handled carefully so reporting does not rely on a partial import.
Useful reporting
Locally stored clicks, banners and campaigns can be searched, reviewed and exported when needed.
Current synchronisation
CheckingProgress people can follow
A clear status view shows the selected period, the part currently being handled and whether any action is needed.
- Date range1 to 7 May
- Current stageBanner details
- Local dataProtected until complete
- Next actionContinue synchronisation
Fictional example
The workflow
From external source to local reporting.
The application handles the awkward connection in the background while keeping progress, results and audit history understandable to the people using it.
- 01
Choose a date range
An authorised user selects the reporting period and previews the expected synchronisation.
- 02
Retrieve the records
The application works through the external source in manageable stages and reports progress.
- 03
Check and store
The incoming records are cleaned, deduplicated and written safely to the local reporting database.
- 04
Search and export
Users work from fast local views instead of depending on the external interface for everyday reporting.
The outcome
A difficult data source became a manageable reporting workflow.
The hub gives authorised users control over synchronisation, visibility while it runs and dependable local views for everyday review and export.
Controlled runs
Date ranges, previews and cancellation
Visible progress
Clear status while work continues
Consistent local data
Safe records for search and export
Audit history
Manual and scheduled activity recorded
Technology
The technology behind the work.
Next.js- TypeScript
- MySQL
- Docker
- Live progress
- Scheduled jobs
About this project
- Sector
- Digital publishing
- Services
- Systems integration, data synchronisation and operational reporting
- Project type
- Internal integration application
Need an awkward data source to become useful?
Tell us how the source behaves and what your team needs from it. We will help turn it into a controlled, maintainable workflow.