Scannur
Scan, catalog and manage stock from the phone in your pocket.
Scannur puts inventory on the phone. Warehouse teams scan a barcode and the item shows up. Retail teams snap a photo and Scannur's reverse image search finds the match. Lists, categories and stock counts stay in one place. We shipped a native iOS app in Swift, a native Android app in Kotlin and a Laravel backend on AWS, with PostgreSQL holding the catalog and Lambda functions running the image search model.
Four capabilities in one native app.
Scannur replaces the clipboard, the barcode scanner and the photo-search tool with a single app that runs on the warehouse floor and a Laravel backend that scales with the business. It is the kind of custom software development that maps to one team's exact workflow.
Barcode scanning
On-device reads for EAN, UPC, Code 128, QR and Data Matrix. Camera reads, app responds, no extra taps.
Object detection
Point at a shelf. Scannur draws bounding boxes, lists what it saw and lets the operator accept or discard.
AI image search
A photo hits an AWS Lambda vision model and the matching catalog item comes back in under a second.
Lists & catalogs
Purchase orders, stock-takes and categories live on top of the item library. One source of truth, no retyping.
Edit and scan, in parallel.
A manager edits an item on the left phone while a floor worker scans a barcode on the right. Both views update against the same PostgreSQL catalog in real time.
Auto Mode reads first, asks second.
Flip Auto Mode on and the camera reads every code that crosses the viewfinder. Scannur ties the code to the active list, pulls the item from the catalog and shows purchase detail and quantity controls with one tap.
- Barcode · Object · Equipment AI modes
- Quantity increment with native haptics
- Auto-link to the active job or stock list
AWS Lambda finds items without a barcode.
When an item has no barcode, point the camera at it. Scannur uploads the frame to an AWS Lambda vision model, the product of focused AI development, and returns candidate matches in under a second. The operator accepts, rejects or edits. The catalog learns from every decision.
- Vision model runs on AWS Lambda
- Multiple-object detection per frame
- Accept / Remove inline review
Every list is a view into the catalog.
Purchase orders, stock-takes and receiving lists sit on top of the same item library. Add a photo thumbnail. Total the cost. Share or export when the count is done. No retyping between tools.
- Live subtotal and total calculation
- Photo thumbnails per list item
- Export to CSV for downstream systems
Native where speed matters. Cloud where scale matters.
The phones stay light because the heavy work sits on the server. The server stays simple because Lambda handles the ML on demand.
{
"mobile": ["Swift", "Kotlin", "React Native"],
"backend": "Laravel",
"database": "PostgreSQL",
"cloud": "AWS",
"ml": "AWS Lambda + vision model",
"native": true
}
// Native camera and haptics live on the phone.
// Catalog, auth, orders and image search live on the server.Four problems detected. Four fixes applied.
Read the left column to see what the brief threw at us. Read the right column to see what we shipped to answer it.
Reverse image search had to run fast from the warehouse floor. A photo goes up, the model runs, the item comes back. Mobile phones cannot hold a model that heavy, so the work had to live on the server.
Barcode scanning had to feel instant. The camera reads the code, the app responds, no extra taps. It runs on a kitchen label and a warehouse pallet with the same speed.
Item libraries had to scale from a corner shop with 50 items to a warehouse with 50,000. The data model stayed the same for both. Pagination, search and filtering had to stay quick at any size.
List management had to feel familiar to anyone who has used a spreadsheet. Add items. Reorder them. Share the list. Export the count. Simple, not simplistic.
We built it native where speed matters. Swift runs iOS. Kotlin runs Android. Camera access, haptics and scan feedback feel right on each platform.
A Laravel backend on AWS holds the core logic. PostgreSQL holds the catalog. AWS Lambda runs the ML reverse image search. The mobile apps stay light because the heavy work sits on the server.
The item library indexes and caches for speed at any scale. A business with 50 items uses the same screens as a business with 50,000. The data model grows underneath without changing what the user sees.
List management sits on top of the library. Any list is a view into the catalog. Sort, filter, share, export. No double data entry. The stock-take on Monday flows into the order on Friday without anyone retyping a number.
Questions buyers ask before the demo call.
> Building an inventory management app typically costs between $40,000 and $200,000 in 2026. A lean MVP with barcode scanning and a basic item library starts near $40,000. A production build with reverse image search, advanced list management, enterprise integrations and dashboards usually lands between $120,000 and $200,000. Scope moves the number.
> Reverse image search in an inventory app takes a photo from the phone, sends it to a machine learning model on the server and returns the closest matching item from the catalog. AWS Lambda functions with a vision model run the search. The app stays light because the heavy work happens on the server.
> A solid tech stack for an inventory management app pairs native Swift on iOS and Kotlin on Android with a Laravel or Node.js backend, a PostgreSQL database and AWS for hosting. Lambda functions handle image recognition well. Native gives the camera and scanner the responsiveness that warehouse users expect.
> A barcode scanning and inventory app typically takes 4 to 7 months from kickoff to launch. Expect 2 weeks of discovery, 12 to 20 weeks of parallel native development on iOS and Android, 2 weeks of closed beta in real warehouses and 2 weeks for App Store and Google Play review. Scope shifts the timeline.
> Yes, an inventory app can integrate with existing ERP systems like SAP, Oracle NetSuite, Microsoft Dynamics, Shopify and QuickBooks through REST APIs, webhooks and middleware connectors. Two-way sync keeps products, stock counts and orders aligned. The ERP stays the source of truth while the mobile app handles the floor.
> An inventory app should work offline because warehouse signal is not guaranteed. Local caching, queued writes and background sync let a user scan, list and edit without a connection. When the phone reconnects, the queue drains to the server and conflicts resolve cleanly. Offline is a requirement, not a nice-to-have.
> A modern inventory app should support EAN-13, EAN-8, UPC-A, UPC-E, Code 128, Code 39, ITF, QR and Data Matrix. Native camera libraries on iOS and Android handle most of these out of the box. Edge cases like damaged or low-contrast codes need tuning. Field tests in real warehouses matter more than lab tests.
> An inventory management app keeps business data secure through TLS in transit, encryption at rest, role-based access control, audit logs and session expiry. Enterprise tenants should get single sign-on through SAML or OAuth. Regular backups, least-privilege server roles and a tested recovery plan round out the essentials.
Planning an inventory or productivity app?
We build native apps that run on the floor and in the office, backed by servers that scale from 50 items to 50,000.