Warehouse management and courier dispatch. One operational brief.
Pika Logistics OS connects order intake, warehouse management (Pika WMS), courier dispatch, the driver app, tracking, proof of delivery, returns, billing and customer portals into one unified logistics offering.
PCube confirms the following modules are live, with 946 live features across Pika Logistics OS. Product status confirmed on .
Order intakeLive
Warehouse management · Pika WMSLive
Courier dispatchLive
Driver appLive
TrackingLive
Proof of deliveryLive
ReturnsLive
BillingLive
Customer portalsLive
Review the relevant functions in a walkthrough and agree your deployment, configuration, users and third-party connections in the proposal.
REAL PRODUCT DEMONSTRATION
The 6-stage operational journey from order intake to billing.
Follow the authoritative order reference through each handover. Use this workflow sequence to evaluate your operational requirements during the product walkthrough.
Workflow illustration: Operational data and status transitions across the 6 core stages.Diagrammatic representation of live system transitions; no fabricated customer data.
Stage 01
Order Intake & Validation
Capture orders from multi-channel sources into a single validated queue with instant inventory reservation.
Operational trigger:Customer order arrives via API webhook, batch CSV import, or manual dispatcher entry.
System action:Order intake module validates line-item SKU availability, checks delivery address formatting, and generates a master operational consignment tracking ID.
Output & handover:Order moves to "Validated & Ready for Fulfilment"; pick lines are assigned to the warehouse queue.
Exception handling:Invalid address or out-of-stock SKU triggers an exception alert; order is quarantined before warehouse release.
Operational trigger:Order release to warehouse floor according to dispatch schedule.
System action:Pika WMS calculates optimal pick paths by aisle and bin, directs staff via handheld scanner, and enforces 1D/2D barcode scan verification.
Output & handover:Goods staged at packing dock; box labels printed; order updated to "Packed & Ready for Dispatch".
Exception handling:Mispick or broken item locks handheld with warning; supervisor approves stock adjustment or backorder split.
Stage 03
Courier Dispatch & Manifesting
Group consignments into delivery zones, allocate fleet vehicles, and issue verified electronic manifests.
Operational trigger:Packed consignments staged at dispatch bay for vehicle loading.
System action:Dispatch controller groups orders by geographic delivery zone, checks vehicle weight limits, and generates electronic manifests.
Output & handover:Parcels scanned onto vehicle; driver signs manifest transfer; order status updates to "Dispatched · In Transit".
Exception handling:Parcel omitted or damaged during loading is unlinked from manifest with timestamped reason before departure.
Stage 04
Driver App & Roadside Updates
Mobile run-sheet for drivers with turn-by-turn map redirection and live milestone updates.
Operational trigger:Driver departs depot with synchronized mobile app run-sheet.
System action:Driver follows sequenced stop list; one-tap status toggling logs real-time milestone timestamps (En Route, Arrived).
Output & handover:Milestone updates sync to customer tracking link; ETA recalculated; depot monitors route completion.
Exception handling:Gate locked or customer unreachable: driver logs structured exception code with photo and GPS location; dispatcher alerted.
Stage 05
Proof of Delivery (e-POD)
Electronic sign-on-glass, camera photo capture, and timestamped GPS coordinates for indisputable delivery proof.
Operational trigger:Driver reaches delivery destination with consignments.
System action:Driver captures recipient digital signature, prints recipient name, and snaps photos of parcel handover with GPS verification.
Output & handover:Delivery marked completed; cryptographic proof generated; status immediately moves to "Delivered · Verified POD".
Exception handling:Customer refuses parcel due to carton damage: driver selects "Damaged Refusal", photographs damage, and initiates return.
Stage 06
Billing, Portals & Reconciliation
Automated line-item billing, instant customer portal visibility, and accounting exports.
Operational trigger:Verified delivery status synced to central OS database.
System action:Pika billing engine applies agreed rate cards (weight, volume, delivery zone, handling fees) and prepares invoice items.
Output & handover:Customer portal displays signed e-POD certificate and photos; accounting export prepared for invoice dispatch.
Exception handling:Disputed charges or return freight fees routed to finance approval queue before invoice finalisation.
How to request a practical walkthrough
To maintain system integrity and operational security, recorded walkthroughs and demonstration environments are provisioned on request for verified logistics operations. No empty video players or fabricated demo credentials are published.
1. Share your operational profile
Tell us your daily order volume, number of warehouses, fleet vehicle count, and current software stack.
2. Bring representative test records
Provide one normal order, one receiving discrepancy, and one complex delivery exception to test against the live product.
3. Live 1-on-1 walkthrough
We demonstrate the live order intake, Pika WMS, dispatch, and driver app workflows handling your operational scenarios.
4. Scoped technical proposal
Receive a transparent, written quotation detailing required modules, user seats, onboarding milestones, and support terms.
Organised by confirmed live module. 946 live features.
PCube reports 946 live features across Pika Logistics OS. An itemised catalogue is reviewed during your scoped operational walkthrough. Below is the confirmed module architecture with customer problems, core functions, and operational dependencies.
Operations & PortalsConfirmed Live
Order Intake & Consignment Ingestion
Customer problem solved:
Orders arriving across emails, spreadsheets, WhatsApp messages, and e-commerce stores lead to duplicated data entry, transcription typos, lost consignments, and fulfilment delays.
Operational functions & capabilities:
Multichannel ingestion: manual single-order entry, batch CSV/Excel import, and direct REST API webhooks.
Automatic SKU validation, inventory availability check, and destination address parsing.
Consignment reference generation linking original order ID to internal tracking and barcode tags.
Duplicate consignment rejection and incomplete order quarantine.
Practical business benefit:
Eliminates double entry and ensures fulfilment starts within minutes of order arrival with verified references.
Dependencies:Integration webhooks or CSV format mapping; configured address validation rules.
WarehouseConfirmed Live
Warehouse Management System · Pika WMS
Customer problem solved:
Mispicks, misplaced pallets, lack of location visibility, and unrecorded inventory adjustments erode operating margins and disrupt delivery schedules.
Operational functions & capabilities:
Inbound receiving, supplier delivery discrepancy logging, and quality check sign-off.
Dynamic location management: zone, aisle, rack, shelf, and bin allocation.
Barcode-directed wave, batch, and discrete picking workflows with wrong-bin lockout.
Stock cycle counts, adjustment approval hierarchy, and cross-client stock isolation.
Practical business benefit:
Ensures inventory accuracy across all bin locations, prevents mispicks, and maintains an immutable audit trail.
Requirements:Pika WMS module activation; Android-compatible handheld scanners or camera-enabled mobile devices; barcode thermal printers.
Dependencies:Warehouse layout mapping (aisle/rack/shelf barcodes); barcode printer for SKU/pallet labels.
Dispatch & FieldConfirmed Live
Courier Dispatch & Route Allocation
Customer problem solved:
Dispatch controllers spend hours matching delivery notes to vehicles manually, resulting in unbalanced loads, delayed departures, and zero mid-route visibility.
Operational functions & capabilities:
Centralised dispatch board with delivery stage queues (Ready for Dispatch, Assigned, In Transit, Delivered, Exception).
Route grouping and delivery clustering by geographic delivery zone or postal code.
Vehicle load and capacity assignment with driver allocation.
Digital manifest generation and driver departure handover sign-off.
Practical business benefit:
Speeds up morning vehicle turnaround, optimises fleet loading, and ensures every parcel is accounted for before leaving the depot.
Dependencies:Defined delivery regions; driver user accounts; vehicle capacity configuration.
Dispatch & FieldConfirmed Live
Driver Mobile Application
Customer problem solved:
Drivers working from printed manifests cannot communicate live roadside progress, lose delivery paperwork, and struggle to manage re-deliveries or route changes.
Operational functions & capabilities:
Digital run-sheet synchronization: assigned stops, delivery notes, and recipient contact details.
Stop-by-stop navigation link to maps (Google Maps, Waze) with priority sequence.
Real-time stop status toggling: Arrived at Stop, Delivery Completed, Access Issue, Customer Unavailable.
Offline caching: drivers can capture statuses and evidence in cellular dead zones, auto-syncing upon reconnect.
Practical business benefit:
Eliminates paper loss, gives the central control room live delivery progress, and handles intermittent connectivity smoothly.
Requirements:Driver mobile seats; Android or iOS smartphones with active data and GPS location enabled.
Dependencies:Active mobile data connection; GPS location and camera permissions on mobile devices.
Operations & PortalsConfirmed Live
Real-Time Tracking & Event Audit
Customer problem solved:
Frequent customer "where is my parcel?" phone calls overwhelm customer support and distract operational staff from core fulfilment work.
Operational functions & capabilities:
Timestamped operational milestone log: Received → Staged → Dispatched → In Transit → Out for Delivery → Delivered.
Public or tokenised branded tracking URL for customer self-service lookup.
Automated status notification webhooks and triggers (SMS, WhatsApp, email).
Strict separation of internal driver telemetry from customer-facing milestone status to protect driver privacy.
Practical business benefit:
Reduces repetitive support calls while giving business clients and end customers transparent delivery progress.
Requirements:Tracking module; SMS/email provider gateway credentials (e.g. Resend, Twilio, or regional SMS provider) configured in proposal.
Dependencies:Configured tracking domain; provider credentials for transactional notifications.
Dispatch & FieldConfirmed Live
Electronic Proof of Delivery (e-POD)
Customer problem solved:
Lost paper delivery notes, illegible handwriting, and customer non-receipt disputes result in delayed invoice payment and lost freight claims.
Operational functions & capabilities:
Sign-on-glass electronic signature capture with printed recipient name and designation.
High-resolution camera capture of parcel handover, doorway placement, or gate drop.
Cryptographic timestamping with latitude/longitude GPS coordinate embedding.
Instant PDF delivery receipt generation and attachment to the central order record.
Practical business benefit:
Provides tamper-evident, indisputable delivery verification available to accounting and customers within seconds of handover.
Requirements:Proof-of-delivery capabilities enabled on driver mobile app; mobile camera and GPS permissions; secure cloud storage.
Dependencies:Driver mobile app access; touchscreen device; camera access permissions.
WarehouseConfirmed Live
Returns & Reverse Logistics
Customer problem solved:
Returned consignments accumulate in warehouse receiving bays without RMA references, customer context, or stock grading, causing inventory leaks.
Driver return collection manifest and warehouse intake scanning.
Quarantine inspection workflow: Grade A (Restock), Grade B (Repackage), Grade C (Damaged / Supplier Return).
Automated restock allocation or disposal approval with reverse billing trigger.
Practical business benefit:
Controls return processing time, protects sellable stock accuracy, and establishes clear financial accountability for return freight.
Requirements:Returns module; defined quarantine location in WMS; authorized return-inspection user permissions.
Dependencies:Return inspection policy definition; quarantine bin layout; staff role allocation.
Commercial & FinanceConfirmed Live
Automated Logistics Billing & Tariffs
Customer problem solved:
Manual consolidation of consignment notes, volumetric weight calculations, surcharge lookups, and storage rates leads to billing leakage and days of invoicing lag.
Operational functions & capabilities:
Multivariate rate engine: dead weight vs volumetric weight (CBM) calculations with configurable dimensional divisor.
Zone-to-zone courier freight tariffs, per-stop fees, waiting time surcharges, and fuel levy calculation.
Warehouse storage and activity charges: pallet-day storage, receiving handling fee, picking fee per item/line.
Automated VAT-compliant invoice and line-item statement generation with export to accounting platforms (Xero, Sage, QuickBooks).
Practical business benefit:
Recovers unbilled operational revenue, eliminates manual billing calculation errors, and shortens the order-to-cash cycle.
Requirements:Billing module; approved customer rate cards and tariff matrices; accounting export mapping (CSV or API).
Enterprise merchants and key accounts require independent visibility into stock balances, order progress, and delivery proofs without emailing the warehouse manager.
Operational functions & capabilities:
Role-based authenticated client portal with multi-tenant data segregation (Client A never sees Client B’s stock or orders).
Self-service consignment creation, CSV bulk order upload, and address book management.
Real-time stock balance lookup by SKU with inbound shipment expected delivery dates.
Proof-of-delivery certificate download and historical invoice statement archive.
Practical business benefit:
Transforms logistics client retention into an enterprise-grade software experience while drastically cutting customer support overhead.
Requirements:Customer portal module; custom domain or subdomain configuration (e.g. portal.yourdomain.com); authenticated customer user accounts.
Dependencies:Domain/subdomain DNS configuration; customer account creation and permissions.
COMMERCIAL CLARITY & PRICING APPROACH
Transparent terms: licences, onboarding, hosting and support.
Pricing depends on confirmed module scope, operational requirements, deployment model, integrations, migration, training and ongoing support. All quotations are issued in South African Rand (ZAR) with clear milestone deliverables.
Licence & Setup Charges
Pika Logistics OS is quoted in South African Rand (ZAR) based on confirmed operational scope: active modules required, depot count, and user tiers.
Setup and deployment fees cover operational scoping, warehouse layout/bin mapping, label configuration, and system onboarding.
No unverified blanket licence fees or arbitrary price lists are published; your written quotation confirms exact monthly or annual terms.
Proposal scope:
We assess your daily consignment volume, required live modules, and integration points before issuing a fixed proposal.
Included Modules & User Seats
Modules can be activated together or deployed modularly (e.g., Pika WMS for warehousing, Courier Dispatch for fleet, or the full unified OS).
User roles are partitioned by responsibility: warehouse floor operatives, dispatch controllers, driver app seats, administrative/finance managers, and client portal users.
Client and customer portal accounts are typically provisioned with unlimited view-only access for verified client accounts.
Proposal scope:
The proposal specifies the included seat count for each role, with transparent pricing for adding additional drivers or depot users as you grow.
PCube conducts pre-launch validation and dry runs in a staging environment to verify data consistency before cutover.
No operations are cut over without signed verification of receiving, picking, dispatch, and delivery proof test runs.
Proposal scope:
Migration timelines depend on data cleanliness and current system export formats, agreed in your onboarding schedule.
Training & Support Boundaries
Role-based onboarding sessions for warehouse teams, drivers, and dispatch controllers.
Direct support via email, WhatsApp, and scheduled video sessions during South African business hours (08:00–17:00 SAST).
Emergency escalation procedures for critical dispatch or receiving blockers.
Proposal scope:
Support scope, response time expectations, and included ongoing maintenance hours are clearly defined in the service level agreement.
Hosting & Deployment Options
Fully managed cloud deployment: secure, managed infrastructure with automated daily backups, SSL encryption, and isolated tenant databases.
Private cloud / dedicated VPC options available for enterprise operations with dedicated compliance or IT sovereignty requirements.
High availability and disaster recovery procedures configured per operational brief.
Proposal scope:
Hosting infrastructure, backup retention, and data sovereignty locations are confirmed during initial scoping.
Third-Party Charges & Integrations
Third-party operational services (SMS/WhatsApp notification credits, mapping APIs, and external carrier broker APIs) are direct pass-through costs without markup.
Supported API integrations: accounting software (Xero, Sage, QuickBooks), e-commerce platforms (WooCommerce, Shopify), and custom ERP endpoints.
Webhook and API documentation provided for in-house technical teams.
Proposal scope:
Integration development, provider API account setup, and failure-handling procedures are agreed before contract signing.
Data Ownership, Exports & Offboarding
100% Client Data Ownership: You retain complete legal and operational ownership of all customer records, order histories, inventory movements, and delivery receipts.
Full Data Portability: Standard CSV and JSON export tools are built into every module for continuous data backups.
Zero-Lock-in Offboarding: If you choose to transition to another platform, PCube assists with comprehensive data extraction and handover without punitive exit penalties.
Proposal scope:
Data retention schedules and offboarding procedures are documented in the master software agreement.
THE OPERATIONAL PROBLEM
One order journey. Fewer disconnected handovers.
Pika Logistics OS is PCube’s live logistics software, bringing order intake, warehouse management, courier dispatch, the driver app, tracking, proof of delivery, returns, billing and customer portals into one product offering. Explore the live modules in a walkthrough using your own operational examples.
Stock and delivery teams lose the same order reference
A warehouse record, dispatch instruction and customer update can become separate versions of the same job. Define the authoritative reference and the owner of each handover.
Exceptions disappear into calls and spreadsheets
Short picks, missed collections and returned goods need a visible owner and a next action. Bring these cases into the requirements discussion instead of reviewing only a perfect order.
Staff repeat information between systems
Review supported import, export and API routes before committing to another manual capture step. An integration must account for duplicate messages and failed updates.
Managers cannot reconcile what happened
Agree the event history, stock movements, status evidence and access roles needed to check an operational record. The right information depends on your responsibilities and workflow.
WAREHOUSING AND DISPATCH BELONG TO THE SAME OPERATION
Review the scope around the work your team does.
Warehouse management · Pika WMS
Live module
Review receiving, stock references, locations, scanning requirements, counts and dispatch preparation against the current product.
Explore live order intake, dispatch, driver handovers, tracking and proof of delivery. Use a normal order and an exception to assess the workflow and supported devices.
Live capabilities · configuration matched to your operation
Bring item codes, units, locations, stock ownership rules and barcode examples. Match the live capabilities to your item references, access roles and configuration requirements.
Provider access and implementation scoped separately
Explore live customer portals and discuss notifications, accounting, order sources and courier connections. Supported APIs, permissions, provider charges and failure handling are confirmed before delivery.
Main capabilities to check against your operation.
The core modules are live. Use these demonstration checks to match their functions, configuration and supported devices to your operation.
Order intake and assignment
Follow an incoming order reference through validation and assignment, including a repeated or incomplete request.
Receiving, stock and locations
Use representative item codes, units, stock locations and a receiving discrepancy in the WMS walkthrough.
Barcode and picking workflow
Confirm supported scanning devices, labels, units and the process when an expected item cannot be picked.
Driver handover and delivery evidence
Review supported staff devices, status ownership and the evidence required to close a delivery or record an exception.
Tracking and customer updates
Separate vehicle-location data from order completion; check source permissions, provider charges and failed updates.
Returns, billing and reconciliation
Review the live returns and billing modules against your approval, charge, export and reconciliation requirements.
Client portals and access roles
Review who can see each owner’s records, which actions need approval and what the customer can access.
Follow the operational reference through each handover.
Order or receiving reference
Warehouse and stock handover
Dispatch assignment
Delivery or exception evidence
Reconciliation and customer follow-up
Use this sequence to review your requirements in the demonstration. The modules are live; your proposal confirms which configuration, users and third-party connections are included in your deployment.
How Pika’s approach differs from other options.
Pika Logistics OS combines live warehouse management, dispatch, driver, tracking, delivery-evidence, returns, billing and portal modules in one logistics product offering. Its fit should be tested using your records and exceptions. This is a comparison of approaches, not a tested claim that Pika has more features, lower costs or better performance than every competing product.
Compare the approach against your requirements, not an unverified vendor ranking.
Approach
What to establish
When to assess Pika
Spreadsheet-led operation
Flexible to start; ownership and version control need a manual process.
Assess Pika when repeated handovers need shared records, roles and a controlled workflow.
Standalone inventory tool
May cover stock balances and movements; verify its dispatch and delivery scope.
Review warehouse-to-dispatch requirements together rather than assuming stock control covers the whole journey.
Tracking-only platform
Can provide supported vehicle or location information; location is different from order completion.
Define operational order status and delivery evidence, including which existing tracking provider to keep.
Large enterprise suite
May offer broad modules; the fit, configuration effort, licensing and integration terms need review.
Compare your required first workflow, current product coverage, customisation and total support responsibilities.
When Pika is worth evaluating.
You need to assess stock and dispatch handovers together.
Your team can provide representative records and acceptance examples.
You want current product capabilities and custom work clearly separated in the proposal.
If your only need is an existing tracking feed or a simple stock list, a narrower supported tool may be enough. Choose against the work and total cost rather than the size of the feature list.
Make the walkthrough a practical acceptance check.
Bring one normal order, one discrepancy and one failed handover.
Choose the live modules, users, devices and access roles for your deployment.
Review imports, exports, migrations and provider permissions.
Record demonstrated functions separately from additional work.
Agree pilot boundaries, training, support and commercial terms.
Pika Logistics OS is PCube’s live logistics software covering order intake, Pika WMS, courier dispatch, driver app, tracking, proof of delivery, returns, billing and customer portals. PCube confirms these modules are live. A walkthrough establishes the configuration, deployment and integrations appropriate for your operation.
Is Pika WMS a different product?+
Pika WMS is the warehouse-management part of the Pika Logistics OS offering. Existing warehouse and courier service pages explain their specific requirements; the OS overview connects the broader operational journey.
Which modules can we use now?+
Order intake, warehouse management, courier dispatch, driver app, tracking, proof-of-delivery, returns, billing and customer portals are live, as confirmed by PCube on 28 October 2026. Deployment, configuration, supported devices and third-party access are reviewed for your requirements.
How many live features does Pika Logistics OS have?+
PCube reports 946 live features across Pika Logistics OS. This is the product owner’s stated feature count. Request a walkthrough to review the functions relevant to your operation; deployment scope and third-party integration access are agreed separately.
Why choose Pika over another logistics system?+
Consider it when your priority is connecting warehouse and dispatch responsibilities around a scoped workflow. Compare a representative normal order and an exception, required integrations, staff roles, migration, training and total costs. No universal best-software or measured savings claim is made.
How much does Pika Logistics OS cost?+
Pricing depends on confirmed module scope, operational requirements, deployment, integrations, migration, training and support. Request a written quotation; no unverified licence or subscription price is published here.
What devices are supported for warehouse scanning and driver delivery?+
Pika WMS supports Android handheld mobile scanners, Bluetooth barcode sleds, and camera-enabled mobile devices for barcode scanning (1D and 2D formats). The driver app runs on standard Android and iOS smartphones with active GPS and camera permissions.
How does the driver mobile app handle poor cellular connectivity?+
The driver app caches assigned manifests locally. Drivers can update stop statuses, capture signatures, and photograph delivery evidence in offline dead zones; data automatically synchronises back to Pika Logistics OS once mobile signal is restored.
Who owns our operational, inventory and customer data?+
You own 100% of your data at all times. All inventory balances, order histories, customer records, and proof-of-delivery files belong to your business and can be exported at any time in standard CSV or JSON formats without vendor lock-in.
Can Pika Logistics OS integrate with our existing accounting or online store?+
Yes. Pika Logistics OS provides REST APIs and webhook endpoints for connecting with e-commerce platforms (such as WooCommerce and Shopify), accounting packages (such as Xero, Sage, and QuickBooks), and custom corporate ERPs.
EXPLORE THE NEXT STEP
Review the connected operational scope.
Compare the warehouse, dispatch and integration requirements for your team.