Flagship Case Study

Odoo ERP Analytics

Turning scattered ERP transactions into structured business flow, data logic, and practical review views.

I mapped how sales, purchasing, production, delivery, invoicing, and payment data connect in Odoo, checked the logic behind the records, and turned the flow into practical review views that help teams review order progress, issues, insights, and follow-up points more clearly.

ERP Analytics / Operations Reporting Odoo 16 and Odoo 18 Business Flow Data Logic Review Dashboard Views
Read the case study

Public-safe case study built from real ERP analytics work.

Business Context

The problem was not missing data. It was a scattered business story.

The records were already inside Odoo. The challenge was reading them as one business case.

  1. Case opened
  2. Clues traced
  3. Summary reviewed
ERP Case File

One order, many clues

A single order could leave traces across sales, purchasing, production, delivery, invoicing, and payment. The dashboard helped turn those traces into a clearer review summary.

Sales Order Where the business request begins.
Purchase Order Where material readiness starts to become visible.
Manufacturing Where stock and production movement need checking.
Delivery Where operational progress becomes customer-facing.
Invoice Where delivery begins to become financial progress.
Payment Where outstanding follow-up becomes visible.
  1. ERP records existed in different places
  2. The relationship between records had to be interpreted
  3. The dashboard became the shared review summary.
MY ROLE

Turning ERP complexity into business-readable review logic

My role was to bridge the gap between operational reality and dashboard review, so scattered ERP records could become a clearer business story.

THE CHALLENGE

Understanding the business flow

The work started from real operational questions across sales, purchasing, production, delivery, invoicing, and payment.

  1. 01 Business processHow the work actually moved across teams.
  2. 02 ERP recordsWhere the data appeared in Odoo.
  3. 03 Review questionsWhat people needed to check or follow up.
THE OUTCOME

Delivering review visibility

The output needed to make interpretation easier: progress visibility, issue signals, and follow-up points that could support review.

  1. 01 Dashboard rulesHow ERP records should be classified.
  2. 02 Review signalsProgress, issue, and watchlist context.
  3. 03 Follow-up visibilityWhat needed action or discussion.
BUSINESS PROCESS

The business flow behind the dashboard

Before the dashboard could become useful, the process itself had to be understood. A case could begin from Sales Order or Internal Order, then move through BOQ, stock checking, purchasing, production, delivery, and invoice.

Mixed cases combine order, stock, purchase, and production logic. Why it mattered: each branch changes timing, control, and interpretation.

DASHBOARD CONCEPT PREVIEW

A recreated review view for Odoo ERP Analytics

This preview uses dummy data to show how order status, source path, delivery progress, invoicing, payment, review signals, and follow-up priorities can be brought into one business-readable dashboard view.

Dashboard Concept Preview for Odoo ERP Analytics using recreated sample data

Recreated dashboard concept preview using dummy data. The layout demonstrates the review logic without exposing internal company records.

Order status Source path Review signals Follow-up priority Invoice and payment progress Data-quality questions

What the dashboard helped reviewers see

Order status

See where each order stood: delivered, billed, delayed, waiting, or needing follow-up.

Follow-up signals

Highlight issues, unusual cases, and next actions without checking raw ERP menus one by one.

APPROACH / PROGRESS STORY

From weekly Excel reporting to dashboard signals

This section shows how my usual problem-solving pattern was applied in the Odoo dashboard project.

01
BEFORE

Weekly Excel reporting

Progress review was mostly handled through weekly Excel reporting connected to the previous Scala ERP process.

Scala ERP Weekly review Excel reporting
02
WORKING THROUGH

ERP access and flow logic

As ERP PIC, I had access to the available data and could trace how records moved across sales, purchasing, production, delivery, invoicing, and payment. From there, the required columns, calculations, classifications, and review signals became clearer.

ERP data Process tracing Review logic
03
CURRENT STATE

Web app and dashboard signals

The reporting direction is moving toward a Python and PostgreSQL-backed web application that can pull ERP data and turn it into dashboard signals for progress, unusual cases, and data quality.

Python PostgreSQL Near real-time signals
HOW THE PROJECT WAS BUILT

How ERP records became review logic

The build focused on interpreting ERP records, validating business rules, and turning them into reusable review logic.

Build Journey

From messy flow to review-ready visibility

A guided path showing how the project moved from ERP complexity into practical review outputs.

01

Messy ERP flow

Sales, procurement, production, delivery, invoice, and payment records were connected in practice but difficult to review together.

02

Source mapping

The project mapped how SO, IO, PO, MO, DO, invoice, and payment records relate to each other.

03

Business rule validation

Statuses, references, custom fields, and exceptions needed interpretation before becoming reporting logic.

04

Review logic

Validated rules were translated into SQL views, dashboard outputs, and review signals.

05

Review-ready output

The validated logic became dashboard views, review signals, and portfolio-ready examples.

Technical judgment

The harder part was validating what each transaction meant in the business process before turning it into review logic.

OUTPUT EVIDENCE

Example of dashboard output built for practical review

The output turns ERP transaction logic into a readable table that supports order tracking, fulfillment review, invoicing context, payment follow-up, and profitability signals without requiring users to inspect raw ERP records one by one.

Order RefSource TypeDeliveryInvoicingPaymentProfitability SignalReview Note
SO-24-0142From StockDeliveredFully InvoicedPaidHealthyRoutine order, no exception follow-up.
SO-24-0179ManufacturingIn ProgressPendingNot DueWatchlistProduction and delivery progress under monitoring.
SO-24-0208Internal OrderPartially ReadyPartialOutstandingNeeds ReviewLinked procurement and invoice follow-up required.
SO-24-0241PurchaseWaiting MaterialNot InvoicedNot DueSupplier Follow-upMaterial availability affects delivery readiness.

Supporting material tracking preview

Material and Amount Order Tracking dashboard preview with sanitized labels and recreated values

Material and Amount Order Tracking preview. Displayed labels and values are sanitized or recreated for explanation.

Material requirementPurchase progressReceipt statusFollow-up readiness
REVIEW SIGNALS / EXCEPTION INSIGHTS

From records to review signals

The dashboard groups filtered ERP rows into simple review indicators so users can distinguish normal records from items that may need delivery, invoice, procurement, source relationship, or material follow-up.

Sales Order Review Signals

Groups sales order rows into review categories for delayed delivery, invoice follow-up, source relationship checks, and operational follow-up.

Sales Order Review Signals dashboard preview with sanitized review signal counts and detection cards
Delayed deliveryWaiting invoiceSource relationship checkOperational follow-up

Material & Procurement Review Signals

Groups material and procurement rows into review categories for monitoring PO progress, receipt status, and procurement follow-up.

Material and Procurement Review Signals dashboard preview with sanitized review signal counts and detection cards
ROP without POPO not receivedPartially receivedSupplier follow-up

Healthy

Rows with no immediate follow-up detected from the exposed dashboard fields.

Watchlist

Normal in-progress or context rows that should be monitored until complete.

Needs Review

Rows with delayed, unclear, mismatched, or variance-related signals.

Supplier Follow-up

Procurement or receipt progress that may need supplier-side follow-up.

Operational Follow-up

Fulfillment, manufacturing, source path, or internal process follow-up.

BUSINESS VALUE

From manual checking to reusable dashboard review

The project reduces repeated manual checking by turning scattered ERP records into reusable review views, helping teams understand what needs attention, what is progressing normally, and what requires follow-up more quickly.

Manual checking
Scattered ERP records
Structured dashboard views
Faster follow-up

Before

  • Manual checking across multiple ERP menus
  • Order, procurement, delivery, invoice, and payment information felt scattered
  • Traceability depended heavily on individual knowledge
  • Reporting required repeated spreadsheet reconstruction
  • Business rules and exceptions were difficult to review consistently

After

  • Centralized dashboard views for practical review
  • Clearer connection across order flow and supporting transactions
  • Reusable SQL logic and dashboard-ready analytical structure
  • Faster review path for management reporting and follow-up
  • Better documentation of business logic and data exceptions
PUBLIC-SAFE CASE STUDY

A portfolio version designed to protect confidential operational data

This case study explains the project structure, business logic, and analytics approach without exposing customer names, supplier names, real order numbers, invoice values, profitability figures, database access details, server details, or confidential operational records.

View repositoryBack to projects