Pattern Grid engagement · Drinks importation and distribution

Ledrop

Connecting sales and field data to improve distribution visibility.

A trader pushing a loaded cart at Mile 12 market, Lagos

Photograph for context: market trade in Lagos. Not a client site.

At a glance

Connecting sales and field data to improve distribution visibility

Sales and field data held in two platforms, with inconsistent product and customer names, became one reporting foundation in Power BI, giving Ledrop clearer visibility into sales, distribution gaps, menu listings and reported out-of-stock issues.

SourcesUwanjani (field)QuickBooks (sales) PipelineAzure Data Factory OutputsSales by customer, product, periodDistribution and menu gapsOut-of-stock reporting
Focus

What the engagement set out to fix.

  • Data integration
  • Data standardisation
  • Sales reporting
  • Distribution gaps
  • Menu listing gaps
  • Out-of-stock reporting
Tools and platforms

What the solution runs on.

  • Uwanjani
  • QuickBooks
  • Azure
  • Azure Data Factory
  • Power BI
01

The problem

Ledrop’s sales and field operations data were held across two platforms: Uwanjani and QuickBooks. Each captured important business information, but differences in how products and customers were recorded made it difficult to connect the data and produce consistent reports.

The same product or customer could appear under different names, which complicated matching records, consolidating sales and comparing field observations with business transactions. Beyond sales reporting, management needed to understand where products were missing, where menu listings could be improved, and which outlets had reported out-of-stock situations.

The main challenges
Disconnected data sourcesSales and field information lived in separate platforms, making consolidated analysis difficult.
Inconsistent product namesVariations in product nomenclature complicated matching and reporting across systems.
Inconsistent customer namesDifferences in customer and outlet naming made it harder to connect sales records with field observations.
Limited distribution visibilityThe business needed a structured way to identify outlets where relevant Ledrop products were absent.
Limited menu listing visibilityField observations needed to become clear reporting on missing product listings.
Fragmented out-of-stock reportingReported stock gaps needed organising so teams could see which outlets and products required follow-up.
02

The system

Two source platforms, one pipeline, one reporting environment. Names are standardised on the way in, so every figure in Power BI traces back to the system it came from.

03

What was built

Pattern Grid developed a Business Intelligence solution that integrated data from Uwanjani and QuickBooks, standardised key business records, and translated the combined information into Power BI reporting.

Integrate the data through AzureDelivered

Azure handled the extract, transform and load process, with Azure Data Factory pipelines bringing both platforms into a structured reporting environment: a repeatable way to prepare sales and field information for analysis.

Standardise product and customer namingDelivered

Product nomenclature was aligned so variations referring to the same product analyse consistently, and customer and outlet names were harmonised so sales transactions connect to field records without splitting one customer or product into several reporting categories.

Build consistent sales reportingDelivered

Reporting structures and measures were developed to analyse sales by customer, product and reporting period on the standardised data.

Develop distribution and menu-listing gap analysisDelivered

Field observations were turned into reporting on distribution gaps (outlets where relevant Ledrop products were not observed), menu-listing gaps (products missing from outlet menus) and competitor-based opportunities (observed competitor products compared with the expected Ledrop equivalents).

Organise out-of-stock reportingDelivered

Out-of-stock observations captured through field activity were organised so the products and outlets associated with availability issues are easy to identify.

Present the insights in Power BIDelivered

Sales and field analyses were brought into Power BI dashboards that let users explore performance and gaps by product, customer or outlet, and reporting period.

04

What changed

The capabilities Ledrop gained, as recorded in the project notes.

Connected sales and field informationAn integrated reporting foundation using data from both platforms, so business transactions can be analysed alongside field observations.
Standardised product and customer recordsNaming aligned across both platforms, reducing inconsistencies in how records are grouped and improving the reliability of cross-platform analysis.
More consistent sales reportingPerformance analysed with consistent product and customer definitions.
Clearer distribution and menu-listing gapsMissing product presence and menu listings visible at outlet level, giving commercial teams a practical basis for prioritising follow-up.
Better visibility into reported out-of-stock issuesOut-of-stock observations organised into accessible reporting.
Repeatable data preparationAzure Data Factory pipelines support ongoing reporting and reduce reliance on one-off data preparation.

Written from the project records. No performance figure is quoted unless the records support it.

Have a similar question in your business?

Tell us how your sales, stock or field data is held today. We reply to arrange a short conversation.

  1. We read your enquiry
  2. We reply to arrange a short conversation
  3. We suggest a sensible next step