ShapeField sales
Order taking on the route
Live prices and balances in the shop, orders queued offline, and the day reconciled against what the office expected to receive.
Services / Work / Mobile applications / Eight modules
Apps for people working away from a desk
A field app is judged in a basement with one bar of signal, not in a demo. Ours record locally and sync when the line returns, so an order taken in a shop is never lost because the network was not there when it was written.
| Captured | Items | Where | State |
|---|---|---|---|
| Order, shop 118Taken 11:04 | 14 | On device | Queued |
| Cash collectedAgainst invoice 2291 | 1 | On device | Queued |
| Delivery proofSignature and photo | 2 | On device | Queued |
| Order, shop 117Taken 10:22 | 9 | Server | Synced |
Standard specification
The eight modules in a standard mobile deployment
Built against the same database your office platform uses, so the app is a second window onto one set of records rather than a separate system to reconcile later.
01 / Offline capture
Work is written to the device first and posted when connectivity returns, in the order it was captured. Nothing is re-keyed and nothing is renumbered, because the sequence was recorded at the point of entry.
02 / Sign-in and device binding
Each user signs in against the same accounts as the web platform, with the option to bind a login to one handset so a shared password cannot become a shared identity.
03 / Orders and collections
Order taking against live price lists and customer balances, cash and cheque collection recorded against the invoice, and receipts issued on the spot.
04 / Routes and visits
The day's list per user, visits marked done with a time and location, and the ones that were skipped visible to a supervisor rather than quietly missing.
05 / Photos and signatures
Delivery proof, damage evidence and site photos captured at full quality, compressed for transfer, and attached to the record they belong to.
06 / Push notifications
Assignments, approvals and alerts pushed to the handset, so a person in the field learns about a change without having to open the app and look for it.
07 / Scanning
Barcode and QR scanning through the camera for stock counts, delivery confirmation and asset checks, with manual entry kept as a fallback for a damaged label.
08 / Release and updates
Builds published to Play and the App Store under your own developer accounts, with the store listing, screenshots and privacy declarations prepared as part of the engagement.
Commonly commissioned
Three shapes of app, and the one thing they share
Each of these lives or dies on what happens when the signal drops, which is why the offline queue is in the baseline rather than sold as an extra.
ShapeDelivery
Proof of delivery
Route lists, signature and photo capture, part-deliveries recorded honestly, and cash on delivery reconciled per driver at day end.
ShapeCustomer
A customer-facing app
Ordering, order history, statements and support in the customer's hands, reading the same catalogue and pricing your staff see.
Pricing
Entry pricing for mobile applications
These are the figures a build of that shape starts at. Beyond them an engagement is quoted as one fixed figure against an approved scope, so the price does not move unless the scope does.
BasicFrom
$3,500
Entry scope. Core build, one role set, standard reports and exports.
View this packagePremiumFrom
$7,500
Extended scope. Several modules and roles, an integration, and full reporting.
View this packageEnterpriseQuoted
Custom
Quoted against your approved scope. Multi-site, multi-role or integration-heavy programmes.
Request a quotationFigures are entry prices in USD, exclusive of taxes. Hosting, gateway charges and third-party services are recharged at cost. Basic and Premium figures are clickable: they open the product page, where the full module list and the buy buttons are. See all products.
Frequently asked
On mobile engagements
01Android only, or both platforms?
Both are quoted, and for most field deployments in this market Android alone is the honest recommendation, because that is what the team already carries. A customer-facing app usually needs both. We will tell you which of the two your audience actually uses rather than charging for a platform nobody will install.
02Whose Play Store and App Store accounts?
Yours, in your company's name, and we recommend that firmly. An app published under a developer's account is an app you cannot update if the relationship ends. We help you create the accounts, prepare the listing and submit the first release, but ownership stays with you throughout.
03What happens when two people edit the same record offline?
The rule is decided in the scope rather than left to chance, because the right answer differs by data. Orders are additive, so both survive. A stock count is a statement about a moment, so the later count wins and the earlier one is kept in the audit trail. Whatever the rule, the losing version is recorded, never silently discarded.
04Do we need a web system first?
The app needs something to sync with, so either you already have a system we can connect to, or the engagement delivers one alongside it. Where there is nothing yet, building the platform and the app together is usually cheaper than building them a year apart, because the data model is designed once.
Next step
Describe one day on the route. That is normally enough to scope the app around it.
State who carries it, what they capture, and what the office needs back from them. You receive a written module specification and a fixed price in return.