MongoDB Logistics Indonesia

SiCepat Ekspres

Supply Chain Optimization

SiCepat Ekspres needed to replace a monolithic SQL Server logistics platform that struggled with real-time order and delivery data as Indonesia’s e-commerce growth drove a rapid increase in package volume.

Processing time was reduced by more than 98% from three hours to around two minutes.
SiCepat has 1,300 branches and 31,000 delivery drivers.
The business has been able to quadruple the number of packages it is capable of delivering to as many as two million per day.

Reported impact

Business outcome

SiCepat scaled deliveries to two million packages per day, cut processing time from hours to minutes, supported 40 million monthly deliveries, and freed engineers to keep modernizing logistics systems across the wider group.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

SiCepat Ekspres moved key logistics workloads from a monolithic SQL Server architecture on AWS to MongoDB Atlas so it could support microservices, real-time tracking, and rapid feature delivery across its nationwide logistics network. Atlas now manages nearly a third of the company’s data, including the core application that coordinates orders from e-commerce partners, pickups, branches, and drivers in real time. The team uses MongoDB indexing to keep operational queries fast, Atlas Online Archive to move older delivery records into lower-cost object storage while keeping them queryable, and continuous cloud backups for localized recovery. MongoDB Realm supports the mobile side of the application, and the company is exploring Atlas Device Sync to keep device and server data aligned. Atlas has also become the default for new innovations such as an executive chatbot that answers daily operational questions from live company data.

Data flow

Order and billing data from e-commerce partners, branches, and drivers are written to MongoDB Atlas, operational queries are accelerated through indexes, older delivery records are moved to Atlas Online Archive, and mobile workflows are served through MongoDB Realm.

Solution architecture

3 components · 2 layers
  1. Storage
    • MongoDB Atlas Runs the core logistics application and stores the operational order, driver, and delivery data used across SiCepat’s business.
    • MongoDB Atlas Online Archive Archives colder delivery data to lower-cost storage while keeping it available for analytics and queries.
  2. Serving
    • MongoDB Realm Supports the mobile-side application logic for delivery workflows running on end-user devices.

Architecture clues

  • Atlas Online Archive is used to keep only delivery-hot data on primary storage.
  • MongoDB Realm powers the device-side portion of the logistics application.
  • Nearly a third of SiCepat’s data is managed on MongoDB Atlas hosted on AWS.
  • The team is exploring Atlas Device Sync for automatic conflict resolution and synchronization.

Evidence from the source

The business has been able to quadruple the number of packages it is capable of delivering to as many as two million per day.
“Data is everything for us – from day-to-day business decision making, through to customer experience and on the ground operations.”
“MongoDB has been fantastic and really delivered for us operationally.”
“We’d heard good things about MongoDB’s fully managed Atlas service, so we decided to test this for our partners' order data and some billing applications. It was an immediate success.”
Transparency Evidence & methodology 90/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. MongoDB

    SiCepat Ekspres customer story

    First-party
    https://www.mongodb.com/solutions/customer-case-studies/sicepat-ekspres
    Source type
    Vendor-published customer story
    Published
    Apr 25, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Apr 25, 2025 · MongoDB · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.