Warehouse execution on a phone you already own.
Twenty-one operational modules covering inbound through pick, pack and ship. Camera-first capture from any iOS or Android phone — no barcode scanners required. AR-guided picking, voice-directed retrieval, Claude-narrated route optimization. Thirteen carriers, seven country packs and fourteen languages including Arabic RTL.
- 21 modules · inbound through ePOD ship
- Camera-first on iOS + Android · scanners optional
- AR-guided picking + voice with Claude dialog
- OR-Tools CVRP route solver + greedy fallback
- 13 carriers · 7 country packs · 14 languages
- MASVS-L2 mobile hardening · Entra ID OAuth2
Built on infrastructure your warehouse team already trusts
Most WMS add-ons assume your warehouse has scanners. Most warehouses just have phones.
Hand-held barcode scanners cost ₹15,000-₹50,000 a unit, take six months to deploy, and turn into shelf-ware when staff turn over. We took a different bet: every operator already has a phone, and modern phone cameras with a Claude-grade vision model resolve barcodes faster than dedicated scanners. Hand-helds are an optional accessory, not a prerequisite. Result: a warehouse that's live in weeks, not months, with a per-operator capex of zero.
Camera-first capture from any iOS or Android phone. Bluetooth scanners supported as an optional accessory for high-volume operators.
Inbound, putaway, pick, pack, ship, cycle count, returns, replenishment, QC, ePOD — the full warehouse execution surface in one app.
IN, AU, EU, UK, US, CA, AE country compliance packs. FedEx, UPS, DHL, Aramex, DTDC, Ekart, Ecom Express and 6 more carriers.
Every warehouse flow, one app.
Each module has its own role-based UI in the mobile app and its own AL codeunit in BC. Activate the modules your operation runs; the rest stay invisible to operators.
Six concrete Claude features routed through one orchestrator.
The Node 20 + TypeScript orchestrator handles every Claude call — JWKS auth, token budgets per company per month, audit logging to SF_AIAuditLog, BC writeback. Vendor-neutral deployment to Azure Functions, AWS Lambda, GCP Cloud Run or self-hosted Docker.
Camera-first capture
Point a phone at any barcode, QR or hand-written label. Claude resolves the SKU. Bluetooth scanners optional, never required.
Voice-directed retrieval
Multi-turn voice dialog with the operator while their hands are full. Speech-to-text + flutter_tts with Claude reasoning, handling clarifications and confirmations.
AR-guided picking
Camera overlay frame highlights the target bin as the operator walks the aisle. Reduces wrong-bin picks; particularly effective for new staff.
Pick-route optimization
Google OR-Tools CVRP solver in a standalone Python service computes the optimal pick sequence. Claude narrates the choice. Greedy fallback if the solver is unreachable.
AI exception triage
Classifies pick discrepancies, short-shipments and damages. Proposes the next action (re-pick, write-off, escalate). Operator confirms; audit trail captures who approved what.
Operator coaching
Pattern analysis over individual operator KPIs. Generates private coaching suggestions for the operator and aggregate insights for the supervisor. Gamification with leaderboard and badges.
Four tiers. One trust boundary per hop.
Mobile, BC, orchestrator and route-solver each do one job. Every hop is JWKS-signed and OpenTelemetry-traced.
Mobile
iOS 14+ / Android 9+. Camera-first capture. Offline-capable SQLite store. MASVS-L2 hardening.
BC AL extension
Cloud target. AppSource-ready. SF_ prefix. JWKS verification on every inbound call. Sync log per device.
AI orchestrator
Claude broker. Token budget per company. Audit log to SF_AIAuditLog. Vendor-neutral deploy.
Route solver
CVRP optimization. JWKS-signed REST. Greedy fallback when unreachable. Stateless, horizontally scalable.
Every Azure-hosted recipe (Functions for orchestrator, App Service for solver) has documented AWS, GCP and self-hosted Docker equivalents. We do not lock you into a cloud you did not choose.
Ship through every carrier you use today.
Every adapter shares one SF_CarrierHTTPBase codeunit handling OAuth / API-key / Basic auth, IsolatedStorage secrets, retry-with-backoff, and sandbox fallback. Adding the 14th carrier is one interface implementation.
Real-API compliance, not stubs.
Each pack ships a real-API client to the relevant tax / e-invoicing authority — token caching, retry, IsolatedStorage secrets, sandbox endpoints for testing.
14 languages shipping at launch, with ARB-based localization and full right-to-left support for Arabic: English (US / GB / AU / IN) · Hindi · Arabic (RTL) · Punjabi · Kannada · Italian · Dutch · Polish · Danish · Swedish · Norwegian · Finnish.
Built for warehouses where the audit matters.
ePOD, batch / lot capture, e-invoicing — every operator action lands in BC with a full audit trail and is exportable for DSR requests.
MASVS-L2 mobile hardening
Certificate pinning with pure-Dart SHA-256 via Dio; biometric step-up (Face ID / Touch ID / fingerprint) for high-risk actions; strict-mode jailbreak / root detection block.
Secrets in Isolated Storage
Anthropic API key, carrier credentials and country-pack OAuth tokens all in BC Isolated Storage. Orchestrator-side secrets in environment-variable secret stores per cloud provider.
JWKS signature verification
Every call between the mobile app, BC AL extension, orchestrator and route-solver is JWKS-signed and verified. No anonymous endpoint touches any business data.
Microsoft Entra ID OAuth2
Mobile sign-in via flutter_appauth against Entra ID; standard BC Web Service users for orchestrator-to-BC writes; full audit trail of who did what.
GDPR / DPDP DSR endpoints
Data-subject request endpoints on the orchestrator handle access, rectification, erasure and portability for delivery records, operator captures and ePOD signatures.
OpenTelemetry tracing
Orchestrator + route-solver emit OpenTelemetry traces. Sentry crash reporting + FCM push + deep-links + sync-conflict review UI on mobile. Full observability for ops teams.
Connectivity-dead aisles do not stop work.
The mobile app maintains a local SQLite store of work assignments and reference data. Captures land locally first, then sync to BC when connectivity returns — with an in-app conflict-review UI for operators.
- Run an entire shift in a connectivity-dead zone — reconcile at the end.
- Mobile Sync Log per device with success / failure and underlying response.
- Sync-conflict review UI on the device; nothing silent.
- Sentry crash reporting + FCM push + deep-links for ops visibility.
Operators see their own KPIs, leaderboard and badges.
Today · Rajesh Kumar ───────────────────── Picks completed 142 ✓ Avg pick time 28 s Accuracy 99.2 % Streak (no error) 58 Position #3 of 21 Badge unlocked Speed II Coach tip: "Bin A-12 to B-04 is the slowest hop on your sequence. Try the route the solver proposed."
Production in 6-10 weeks.
Single-warehouse SMB rollouts: 6-10 weeks. Multi-site multi-country: 10-20 weeks. A senior SourceForge consultant runs each project end to end.
AppSource-ready AL extension. Orchestrator deploys to your stack.
1
Warehouse layout walk-through. Bin and rack structure audit. Existing process pain points. Carrier and country-pack shortlist. Mobile-device standardization (BYOD vs issued).
2
Publish AL to sandbox. Master data + bin structure import. Mobile app pilot to a 3-5 operator group. Orchestrator deployed to Azure Functions / AWS Lambda / GCP / Docker per your stack.
3
First inbound + outbound shifts in parallel with the legacy flow. Sync log monitored end-to-end. Country pack + first carrier adapter configured and tested with sandbox endpoints.
4
Full operator training. Mobile app rolled to every device. AR + voice features activated. Comms plan for the first week of solo running. Daily check-in calls.
5
Daily review of Mobile Sync Log and AI Exception Triage backlog. Tune route-solver constraints. Add country packs and carrier adapters as roll-out expands.
Frequently asked questions
Business Central v27.4 and above, both SaaS (Cloud) and On-Premises. AL runtime 16.0, Cloud target — AppSource-ready. Object range 52000-52299, with all identifiers prefixed `SF_` and a separate test app in 51490-51499. Depends only on Microsoft System Application and Base Application 27.0.
Hand us your phone. We will scan your shelf live.
A 60-minute working session, not a sales pitch. Bring an actual phone and a sample box from your warehouse. We sign you in to a sandbox, walk through inbound → putaway → pick → pack → ship on your device, and show you the audit trail in BC for every step.
- Real device demo — your phone, your barcode, your aisle
- Live AR + voice features in the picking flow
- Honest answer on whether you need scanners (most do not)
- Written proposal within 48 hours