Muhammad Syauqi Al Bashir
All projects

Case study

Work at Monotaro

Data and integration work for a Japanese-owned B2B e-commerce company, on Google Cloud.

  • Oracle APEX
  • PL/SQL
  • SAP
  • Magento
  • Google Cloud
  • BigQuery
  • Dataform
  • Cloud Run
  • GitHub Actions
  • Odoo
Customer SAPtheir ERP Oracle APEXmiddle system Magento storecatalog · prices Google Cloud data platform Scheduler Workflows Cloud Run Dataform ·BigQuery ~7–9 million records synced per day

The problem

Enterprise customers buy from their own ERP, product data changes every day, and releases must be safe. (Described at a high level; no internal details are shown.)

What I built

  • SAP ↔ Magento e-catalog: an Oracle APEX middle system that keeps enterprise customers' SAP catalogs in sync with the store, so they can order from inside their ERP. Live since January 2026; billions of rupiah in sales have gone through it. It needed close work with customers and stakeholders.
  • Daily data syncs at scale: batch jobs moving ~7–9 million records per day with selective sync and concurrent workers.
  • Pipelines on Google Cloud: Cloud Workflows, Dataform, Cloud Run jobs/functions/services, Cloud Scheduler, BigQuery, IAM and Workload Identity Federation.
  • CI/CD for Oracle APEX: schema and application releases automated with GitHub Actions + Playwright + Workload Identity Federation, replacing a manual process and improving security.
  • Odoo ERP development and support across sales, purchase, manufacturing and accounting.

How it works

  1. 1Customer SAP
  2. 2Oracle APEX middle system
  3. 3Magento store
  4. 4Orders back to the ERP

Engineering notes

  • Working language: English, with a Japanese manager and Japanese engineering standards.

How I build

Designed, built, tested and deployed by me with an AI coding assistant (Claude Code): I set the requirements, review every change, test on scratch copies with fake data, and run it in production.