Checkout
Creates in-store, pickup, and delivery orders from one transaction flow.
Technical system overview
CommuterCart platform architecture
A technical description of the point-of-sale system, delivery layer, matching engine, integrations, and operating workflow.
POS
Orders and inventory
Delivery
Dispatch and tracking
TransportAI
Route-fit matching
Data
Operational records
Point of sale
Commerce and fulfillment in one order model
Catalog and inventory
Maintains products, modifiers, availability, pricing, taxes, and stock.
Customer records
Stores merchant-controlled customer and order history.
Operations
Supports staff permissions, reporting, refunds, locations, and reconciliation.
Delivery trigger
Creates an eligible delivery request automatically when checkout completes.
Integration
Connects through the dashboard, widgets, APIs, and webhooks.
Delivery layer
Order-to-delivery workflow
Request
Capture pickup, dropoff, package, timing, handling, and price inputs.
Qualify
Check service area, package constraints, merchant rules, and carrier requirements.
Match
Rank available drivers by route fit, vehicle capacity, reliability, and timing.
Dispatch
Send the opportunity, record the response, and assign the accepted driver.
Track
Record pickup, status, location, ETA, messages, and exceptions.
Complete
Store delivery evidence, payment status, ratings, and the final audit record.
System architecture
Modular, event-driven, and carrier-neutral
1
Experience layer
Merchant POS, business dashboard, sender workflow, driver workflow, and customer tracking.
2
Commerce layer
Catalog, checkout, orders, taxes, refunds, customer records, and inventory.
3
Delivery orchestration
Eligibility, quotes, matching, assignment, status, exceptions, and proof of delivery.
4
Carrier adapters
CommuterCart drivers, merchant delivery, and approved third-party carriers.
5
Payment boundary
Sender charges, merchant billing, platform fees, driver payouts, and reconciliation remain separately recorded.
6
Data layer
Immutable order and delivery events support reporting, audit, scoring, and model improvement.
Operating controls
Controls required for production delivery
Identity and access
Role-based permissions for administrators, merchants, senders, and drivers.
Driver verification
License, insurance, vehicle, identity, and availability records.
Delivery evidence
Timestamps, status history, location events, recipient confirmation, and proof.
Exception handling
Reassignment, cancellation, failed delivery, damage, refunds, and support ownership.
Payment reconciliation
Separate gross charge, platform fee, driver payout, refund, and transfer records.
Integration reliability
Idempotent order creation, webhook retries, versioning, logs, and status monitoring.