Digitizing Proof of Delivery for GSC

This case study explores how Closeloop digitized Grocery Supply Company’s paper-based proof of delivery process by building a custom offline-first Android application that mirrored legacy workflows supported drivers and helpers captured exceptions in real time and integrated seamlessly with backend systems resulting in faster delivery reconciliation reduced accounting errors zero paper usage and improved operational visibility across logistics and finance.

Nov 20, 2025 5 Minutes Read Grocery Supply

Grocery Supply Company (GSC) is a Texas- based wholesale distributor with a legacy of over 70 years in serving convenience stores across the United States. As a full-line distributor, GSC offers a comprehensive range of products, including food, beverages, tobacco, and general merchandise.

Their operations span multiple states,supported by a fleet of internal drivers and a logistics network built on precision, reliability, and customer service. GSC’s mission is to empower retailers with timely, accurate, and comprehensive supply solutions. Their business thrives on operational excellence, and their delivery model is a critical pillar of that promise.

With a strong emphasis on service quality and accountability, GSC has built long- standing relationships with thousands of retailers.

Team Collaboration

Paper Systems Constraining Delivery

GSC’s delivery operations were anchored in a paper-based proof-of-delivery (PoD) system. While this legacy approach had served them for over seven decades, it was increasingly becoming a bottleneck in their otherwise streamlined supply chain.

Manual Documentation

Drivers recorded deliveries, exceptions, and pickups on paper forms. These were prone to errors, omissions, and illegibility.

Lack of Real-Time Visibility

If you explain your goal, it will be easier to achieve the vision. A variety of important challenges and concerns explain the mission.

Delayed Reconciliation

Accounting teams had to interpret scribbled notes to reconcile deliveries with invoices, often taking days.

Inconsistent Exception Handling

Overages, shortages, damages, and returns were inconsistently documented, leading to disputes and inefficiencies.

Operational Overhead

Paper forms had to be printed, distributed, collected, and stored — adding cost and complexity.

Unlock Full Case Study

Our research engaged frontline and back-office stakeholders to understand end-to-end delivery operations, revealing critical edge cases and workflow evolutions that shaped a practical, user-centered design.

Glove Use

Drivers needed large touch targets and minimal typing.

Helper Roles

Some deliveries were logged by helpers, requiring exible input.

Pickup Tasks

Drivers often picked up expired items and cardboard trash—tasks not reflected in the original documentation.

Paper Legacy

The forms usage had evolved organically, and replicating their logic was essential for adoption.

  • Drivers to understand daily routines, pain points, and edge cases
  • Helpers to map team-based delivery flows
  • Accounting staff to trace reconciliation challenges
  • Operations managers to align with understanding edge cases

Scalable Solutions

We explored several commercial PoD platforms and logistics apps. However, through early whiteboarding sessions and stakeholder interviews, it became clear that GSC’s delivery process was highly specialized, with nuances that generic platforms couldn’t accommodate.

1

Collaboration

Helper involvement, where multiple team members contribute to a single delivery log.

2

Cleanup

Pickup tasks like expired items and cardboard trash, which are rarely supported in standard PoD tools.

3

Offline

Offline operability, essential for routes with poor connectivity

4

Glove-Friendly

Support glove-friendly interaction, with large touch targets and minimal typing, tailored for blue-collar ergonomics.

5

Exceptions

Exception handling for overages, shortages, and damages, requiring structured capture and reconciliation.

6

Enterprise

No public-facing features, since the app was for internal use only on company-issued devices.

Key Features

This architecture reflects Closeloop’s commitment to building resilient, user-centric, and scalable solutions that honor the operational realities of GSC’s delivery business.

Key principles applied:

  • Offline-First Design
  • Geo-Fencing Validation
  • Modular Exception Handling
  • Helper Support
  • Security & Compliance
  • Scalability
Key features

Technical Architecture

Acg workflow Diagram

Tech Stack

Kotline Logo Kotlin
SQLite Logo SQLite
Node Logo Node / Express JS
Laravel Logo PostgreSQL
AWS Cloude AWS Cloud
JWT Logo JWT

Value Delivered & Business Impact

Closeloop delivered far more than a mobile app — we delivered a strategic transformation rooted in empathy, operational insight, and technical excellence.

  • Business Immersion, Not Just Requirements Gathering.
  • Empathy-Driven Design for Blue-Collar Usability.
  • Digitization of Tribal Knowledge.
  • Operational Streamlining Across Departments.
  • Iterative Collaboration and Co-Creation.
  • Scalable Foundation for Future Innovation.
Delivery Reconciliation Time
85% Faster
Accounting Errors
90% Reduction
Driver Satisfaction
High Positive feedback
Paper Usage
0% Fully eliminated

Portfolio

These screenshots highlight how the GSC proof-of-delivery mobile app brings the key workflows to life, showing an offline-first, driver-friendly experience that captures exceptions, supports helpers, and keeps deliveries secure and scalable.

Portfolio
Portfolio
Portfolio
Portfolio
Portfolio
Portfolio

Client Value & Feedback

"The scope of work was to develop a proof of delivery Android app for our delivery drivers. Our delivery process is unique. Therefore, we needed a custom software solution. Our deliverables are the app itself along with underlying code. What we found most impressive was how they immersed themselves in our business to learn its nuances. This turned out to be crucial in developing the software we needed."

— CIO, GSC Enterprises, Inc