Overview
An automated B2B procurement integration and monitoring platform that connects the company's internal procurement process to the systems of major vehicle providers (Toyota and Daihatsu). It automates end-to-end Purchase Order (PO) workflows — submitting orders, receiving confirmations, and synchronizing payment and status updates — orchestrated as scheduled data pipelines, with a dedicated web dashboard for real-time visibility into every job run.
The Problem
Procuring vehicles from external providers meant interacting with third-party systems that expose SOAP web services and exchange data as XML. Done manually, this was slow, error-prone, and hard to audit: orders and payment statuses had to be entered and checked by hand, failures were hard to spot, and there was no single place to see whether integration jobs had actually succeeded. The business needed a reliable, automated, and observable pipeline.
Architecture
The solution has two main parts — an integration pipeline and a monitoring application:
- Integration pipeline — Python scripts orchestrated by Apache Airflow DAGs run the PO workflow on a schedule, with built-in retries and logging so each step is repeatable and traceable.
- Third-party SOAP integration — dedicated integration scripts consume the providers' SOAP APIs (Toyota and Daihatsu), building and parsing XML payloads and handling secure SOAP headers for authentication, to automate vehicle purchasing and payment-status updates.
- Monitoring web application — a Laravel + Vue.js dashboard gives the procurement and operations teams real-time visibility into job runs, statuses, and failures, so problems can be caught and acted on quickly.
- Resilience — a disaster recovery plan was defined for the integration so the procurement flow can be restored if an upstream system or environment goes down.
Key Features
Automated Purchase Order Workflow
The full PO cycle is automated end to end: submitting purchase orders to the provider, receiving and processing confirmations, and updating payment and order status back in the internal system — removing manual data entry and reconciliation.
SOAP / XML Integration
Integration scripts interface with third-party SOAP APIs, parsing and constructing XML messages and attaching secure SOAP headers for authenticated requests. This bridges the internal procurement system with external providers that only expose SOAP-based services.
Orchestration & Scheduling
Apache Airflow DAGs schedule and orchestrate the pipeline, coordinating each stage of the workflow with retry logic and run logging so transient failures are retried automatically and every execution is traceable.
Monitoring Dashboard
A dedicated web app ("Monitoring B2B") surfaces the health of the integration: which jobs ran, their outcomes, and where failures occurred. This turns an opaque background process into something the team can actively monitor and troubleshoot.
Disaster Recovery
A DR plan was established for the B2B integration to keep the procurement flow recoverable in the event of an outage in an external or internal system.
Tech Stack
- Integration & Orchestration: Python, Apache Airflow (DAG)
- External Interfaces: SOAP, XML (secure SOAP headers)
- Monitoring App: Laravel, Vue.js
My Role
Integration / Backend Developer — architected and engineered the automated procurement pipeline, built the SOAP/XML integration scripts and Airflow orchestration for the end-to-end PO workflow, and developed the monitoring web application for job visibility and failure handling.
