Mobile

A native shop-floor CRM app, not a website squeezed onto a phone

Built for a phone that lives in a shirt pocket under a shop coat: real camera capture, an offline write queue, push approvals and GPS-stamped visits.

Start Free Trial (No Credit Card)See a Live Quote Draft

Diagram titled "The shop floor, on a phone", showing the seven RFQ-to-order stages from enquiry intake through to accepted order.

In short

KanchanFlow is an RFQ-to-Order CRM with native iOS and Android apps rather than a responsive website. The app captures RFQs from a drawing photo, works offline with a local write queue that preserves the original capture timestamp, and delivers quote approvals as push notifications on every tier.

Two places in a manufacturing business are hostile to software: the shop floor and the truck. The floor has bad light, worse signal, dirty hands and a person who has ninety seconds between setups. The truck has a rep who needs the last accepted price on a part before walking into a purchasing office, and who will be in a steel building with no bars ten minutes later.

Most manufacturing CRMs answer this with a responsive layout. That works for reading and fails at capture, which is the part that matters. The difference between a shop that logs its customer visits and one that does not is almost always whether logging takes fifteen seconds or five minutes.

Why native

Four things a browser cannot do well on a shop floor

Each one is a capability the platform grants an installed app and rations to a web page.

Camera: Direct capture; A print photographed against a granite plate under shop lighting needs real camera control, not a browser file picker. The app captures, crops and attaches to the RFQ in one motion.
Offline: Local queue; Steel buildings kill cellular. Records created in a dead zone queue locally and sync when signal returns, with conflicts surfaced rather than silently overwritten.
Push: Real notifications; A margin approval that needs the owner reaches a lock screen. A web notification in a browser tab nobody has open reaches nothing.
GPS: Visit stamping; A customer visit logged with a location and timestamp is a fact. A visit typed in from memory on Friday is an estimate.

Offline

What happens when the signal dies

A steel-clad building with a 40-ton crane overhead is a Faraday cage with a payroll. Offline is the normal case, not the exception.

Create offline — New RFQs, visit logs, notes and photos are written to a local queue with their capture timestamp preserved.
Read offline — Recently viewed accounts, open quotes and the parts you looked at this week are cached, so a rep in a plant basement can still see the last accepted price.

Sync on return — The queue drains in order when signal returns. The RFQ carries the time it was captured, not the time it uploaded, so response-time metrics stay honest.
Conflicts surfaced — If a record changed on the server while you were offline, you see both versions and choose. Nothing is silently overwritten in either direction.

Preserving the capture timestamp is the detail that keeps the reporting honest. An RFQ photographed at 9:12am in a dead zone and synced at 11:40am is recorded as arriving at 9:12am. Otherwise every offline capture would inflate your median response time and the number would stop being useful.

By role

Who uses it, for what, and where

The mobile app is not a smaller version of the desktop workspace. It carries the handful of actions that happen away from a desk.

Role	What they do on the phone	Where
Owner	Approve a margin exception, see today's order book, check the week's win rate	Between machines, 90 seconds at a time
Estimator	Photograph a print a customer brought in, add it to the RFQ queue with a note	At the front counter
Outside sales	Log a visit, capture an RFQ in the customer's lobby, check the last accepted price before quoting	In the truck and on site
Inside sales	Answer where is my order from the order record, send a quote follow-up on WhatsApp	Anywhere
Production coordinator	Update a milestone, flag a ship date at risk	On the floor

Field visits

A visit that is a record rather than a recollection

A field visit logged in the app carries the account, the contact seen, a GPS location, a timestamp, the notes taken and any photo captured. That turns a sales call into something the shop can act on: an RFQ raised from the visit, a follow-up task with a date, and a record on the customer 360 that the next person to visit can read.

The alternative most shops live with is a rep filling in a week of visits on Friday afternoon from memory. Those notes are thin, the dates drift, and nobody ever raises an RFQ from them. The visit intelligence reporting — coverage by territory, time since last visit by account, RFQs raised per visit — is only worth having if the underlying capture is quick enough that reps actually do it.

Boundaries

What the mobile app is not for

Shop-floor data collection — we are not a machine monitoring or time-clock app
Job routing and dispatch to work centres — that is your ERP
CAD viewing with measurement and markup on a phone screen
Barcode-driven inventory transactions
Anything that requires a person to look at a phone while running a machine

What this is not

This is not an ERP, MRP, CAD, BOM, or advanced CPQ system — it manages customer RFQs, quotes, follow-ups, and order handoff.

Questions about the mobile app

Four capabilities a mobile browser handles badly or not at all: sustained camera control for photographing prints, a reliable offline write queue, push notifications that arrive on a locked phone, and background GPS for visit stamping. A responsive site is fine for reading a dashboard in an office. It is not fine for a rep capturing an RFQ in a plant with no signal.

See a live quote draft built from a real RFQ

Fourteen days, no credit card, sample data pre-loaded. If it does not fit your shop, we will tell you in the first call.