Supply Chain & Mobile2024 — 2026•Production App (Google Play Store)•ERPNext / Frappe (Multi-Instance Python APIs) & Google Play Store

Branch Logistics & Hub Distribution App

Mobile Hub Operations, Truck Unloading & Last-Mile Receiver Delivery

Production mobile application hosted on the Google Play Store (com.dexciss.branchapp) engineered for logistics distribution hub operations and field delivery teams. Built to power high-throughput transport hubs, the app enables hub users to receive cartage manifests, audit and unload incoming transport trucks, pick and stage dockets, monitor delivery fleet transit, and execute verified hub-to-receiver doorstep deliveries. Architected with an agile multi-instance gateway where a single mobile application dynamically authenticates and connects across multiple independent ERP instances via Python REST APIs, generating isolated session tokens without hardcoded server boundaries.

Inbound Truck Unload & Cartage
Hub Docket Audit & Staging
Hub-to-Receiver Last-Mile Delivery
Multi-ERP Session Authentication
ERPNext / Frappe (Multi-Instance Python APIs) & Google Play Store
Product UI & Interactive Interfaces

Interface Evidence & Workflows

Click any thumbnail to inspect
Branch App Launch & Secure ERP Login
Authentication & Setup

Branch App Launch & Secure ERP Login

Official splash and gateway portal hosted on Google Play Store (com.dexciss.branchapp), prompting secure username and password authentication to generate authenticated ERP session cookies.

Screen 1 of 6
Workflow Mechanics

End-to-End Hub Logistics & Last-Mile Delivery Lifecycle

Step 01

Dynamic ERP Instance Authentication

Hub operators launch Branch App, specify the target ERP server URL, and input their username and password. The Python backend validates credentials and issues an authenticated session token ('sid'), enabling one mobile app to seamlessly interface with multiple enterprise ERP instances.

Step 02

Inbound Truck Arrival & Manifest Inspection

Arriving transport vehicles report to the hub dock. Operators open the 'Manifest Receive Cartage' screen, fetch scheduled inbound manifests, and inspect expected docket numbers and consignment parcels.

Step 03

Truck Unloading & Cartage Reconciliation

As cargo is unloaded, operators scan physical barcodes or verify parcel counts against the manifest. Discrepancies, shortages, or damaged parcels are flagged before accepting cartage into hub custody.

Step 04

Hub Docket Auditing & Staging

Received dockets are audited at the central hub distribution area. The 'Received Dockets At Hub' console updates inventory statuses in real-time and routes packages into designated staging bins for sorting.

Step 05

Docket Picking & Vehicle Run-Sheet Dispatch

Hub delivery executives pick assigned dockets according to local distribution zones, load delivery vehicles, and generate real-time transit run-sheets for last-mile routes.

Step 06

Final Hub-to-Receiver Delivery & POD

Drivers navigate delivery routes, perform doorstep handovers to the consignee/receiver, record digital Proof of Delivery (POD) signatures, and close the consignment lifecycle in the central ERP.

Architectural Breakdown

System Layers & Technical Design

Client & UI Layer

Android / Cross-platform mobile client (Google Play Store: com.dexciss.branchapp) featuring dynamic ERP server URL configuration, session credential manager, camera barcode/QR scanner, vehicle run-sheet tracking, and role-gated UI modules.

Services & Logic

Python REST API controllers within Frappe/ERPNext backend support app handling session authentication ('sid' cookie/token), Inbound Cartage Manifest receipt, Hub Docket auditing & picking, Delivery run-sheet dispatch, and role-restricted audit services.

Storage & Persistence

Relational MariaDB / PostgreSQL schemas maintaining Cartage Manifests, Hub Inbound Dockets, Inventory Staging Bins, Delivery Run Sheets, Consignee Digital POD records, and Role-Based Access Control (RBAC) permissions.

Problem & Solution

The Engineering Challenge & Solution

The Engineering Constraint

Logistics hubs frequently experienced severe docket mismatches, misplaced parcels, and slow turnaround times during chaotic truck unloading. Furthermore, field operators needed to interact with multiple independent ERP instances without requiring distinct app installations, and sensitive operational decisions (like collection overrides and docket cancellations) required strict role-based permission enforcement on mobile devices.

The Technical Solution

Engineered and published the Branch Logistics App on Google Play Store featuring a dynamic session-based multi-ERP gateway, enabling a single client to authenticate and interact with any Frappe/ERPNext instance hosting the Python backend support app. Built dedicated, high-speed interfaces for Inbound Cartage Receiving, Hub Docket Auditing & Picking, and Transportation Delivery Tracking with digital POD handovers, reinforced by server-side role restrictions on high-risk operations.

Deliverables

Production Impact & Delivered Capabilities

Hosted and published production Branch App on Google Play Store (com.dexciss.branchapp)

Architected multi-instance ERP session gateway enabling 1 mobile client to connect dynamically across multiple ERP servers

Streamlined inbound truck unloading and cartage manifest reconciliation, significantly reducing vehicle dwell times

Engineered hub docket barcode auditing and pick-and-stage workflows to eliminate sorting errors

Implemented end-to-end transportation delivery tracking with verified hub-to-receiver proof of delivery (POD)

Enforced role-restricted operational governance, protecting sensitive financial actions and docket cancellations

Technologies & Frameworks
Android (Google Play)Python REST APIsFrappe / ERPNextSession AuthenticationBarcode & QR ScanningMulti-Instance ERP GatewayMariaDB / PostgreSQLSupply Chain Logistics
System Architecture & Data-Flow Diagrams

Architecture & Process Flow Models

Interactive DFD
End-to-End Hub Logistics DFD
Rendering architectural data flow...
Rendered via Mermaid Engine • Dynamic Data Flow

End-to-End Hub Logistics DFD

Data flow diagram mapping Inbound Truck Unload, Cartage Manifest Receipt, Hub Docket Auditing & Staging, Last-Mile Delivery, and ERP Database Persistence.

Diagram 1 of 2