Avenxor turns raw public data into decision-ready intelligence for procurement, trade, and market research teams. We extract from Indonesian government and public sources — BPS for trade statistics, LKPP and INAPROC for procurement, Bea Cukai for customs records, SIRUP for planning data, PDN for procurement transactions — and run it through ETL pipelines that normalise inconsistent column names, reconcile mixed HS-code versions, and resolve vendor name variants that would otherwise break aggregation. The output is a clean, query-friendly schema you can build a dashboard or a model on top of, refreshed on a documented cadence, exposed via REST APIs or delivered as scheduled feeds. Current data products cover an indexed catalogue of 100,000+ INAPROC items, ten years of HS-code level import-export records across 40+ trading partners, and procurement planning signals from SIRUP that arrive months before the catalogue order is placed. Every dataset ships with provenance metadata, refresh logs, and a published quality SLA — so your analysts and machine-learning models work on data you can defend in a meeting.
What public data sources does Avenxor ingest?
BPS (Badan Pusat Statistik) for trade and macroeconomic statistics, LKPP and INAPROC for the national procurement catalogue, Bea Cukai for customs and import-export records, SIRUP for procurement planning signals, and PDN for procurement transaction history.
How fresh is the data, and how often is it refreshed?
INAPROC and SIRUP datasets refresh every three days via scheduled cron. Trade and customs data follow the publication cadence of BPS and Bea Cukai (typically monthly). Every dataset has a published SLA so downstream consumers know the freshness floor.
Do you provide raw datasets, APIs, or both?
Both. Curated datasets can be delivered as scheduled CSV / Parquet feeds for analyst teams, or exposed as REST APIs for application integration. Custom delivery (S3 drop, BigQuery export, webhook) is available on request.
How do you handle data quality and provenance?
Every record carries source identifiers and ingestion timestamps. ETL pipelines log row counts, schema diffs, and rejection reasons per run. A quality SLA is published per dataset so users know what is guaranteed and what is best-effort.
Can Avenxor build custom market intelligence for a specific sector?
Yes. Past engagements include HS-code level competitive analysis for trading companies, procurement gap analysis for medical device vendors, and trend reports built from multi-year LKPP catalogue history. Output formats range from scheduled briefings to embedded dashboards.
Is the data legally usable for commercial decisions?
The underlying sources (BPS, LKPP, Bea Cukai) are public datasets published under open data terms by the Indonesian government. Avenxor adds the cleaning, normalisation, and delivery layer — clients are responsible for confirming downstream use cases match their internal compliance.
Have a data & analytics challenge?
Let's talk.
Most engagements start with a 30-minute call. Describe the problem — we'll tell you honestly if we're the right team.