Blogs · Operations
Why field order forms need industry math, not spreadsheets
At the counter, the dealer says sheets and sizes — the order should capture industry math there, not on a calculator while traffic waits.
Mobile order management for building materials must handle nett area, weight, and SKU math in the order flow — not in a rep’s head or a side calculator. Field order apps should encode industry rules.
A plywood salesperson standing in a dealer yard is not selling "units" in the abstract. They are selling sheets with thickness, grade, and face; the dealer thinks in nett area (NA), dispatch thinks in weight, and finance thinks in rupees tied to both. When your mobile order form only accepts quantity and SKU, the real conversation still happens on a calculator app, a scribbled note, or a WhatsApp message — and HQ spends the next day fixing what should have been right at the counter.
That is not a training problem. It is a product design problem. Building-materials distribution has industry math baked into how people buy and fulfil. Field software that ignores NA, sheet counts, and weight is asking salespeople to carry the industry's rules in their heads while the system records something simpler and wrong.
What breaks when math lives outside the order
Most generic SFA apps were built for FMCG: cases, pieces, standard pack sizes. Drop the same form into plywood, laminates, or boards and predictable failures appear:
- Salesperson enters "quantity" that nobody else understands. Is it sheets? Bundles? A number the dealer said that maps differently in your ERP?
- Nett area is calculated twice. Once on the phone calculator at the visit, again at dispatch when someone notices the tonnage does not match the truck plan.
- Weight is guessed or omitted. Logistics and credit teams discover the mismatch only when loading or invoicing — when changing the order is expensive politically and operationally.
- Corrections become the norm. "Please change line 3 to 18mm" messages pile up because the first submission was structurally incomplete, not because the salesperson was careless.
Each correction is a hidden tax: dealer trust ("your system is always wrong"), salesperson time, and back-office rework. The business learns to treat the mobile order as a signal rather than truth — which defeats the point of capturing orders in the field at all.
A dealer asks for "12 NA of 19mm commercial." The salesperson knows what that means. If the app only has a quantity box, they will either enter something approximate or pause the visit to open a calculator — while the dealer watches and the queue behind them grows.
Nett area, sheets, and weight are one calculation chain
In plywood and adjacent categories, nett area is not decorative metadata. It is how dealers compare brands, how schemes are explained, and how many sales conversations are conducted. Sheet count and dimensions drive NA; NA and product attributes drive weight; weight drives freight, loading, and often credit scrutiny.
When these values are computed during order placement, several things become possible that spreadsheets and side apps cannot reliably deliver:
- The salesperson and dealer see the same summary before submit — NA, sheets, estimated weight, line totals.
- Dispatch and warehouse see the same numbers the salesperson committed to, without a second interpretation pass.
- Product-specific rules (thickness, size, conversion factors) apply consistently branch to branch, not "how that salesperson was taught."
- Reorder from history replays the same math, not a remembered shortcut from last month.
The goal is not to turn salespeople into mathematicians. It is to remove mental arithmetic from a moment that should be about relationship, availability, and closing the basket.
Why spreadsheets and WhatsApp are the wrong layer
Many distributors already have a spreadsheet that "works." NA per SKU, weight factors, maybe a macro someone built years ago. It lives on a manager's laptop or gets forwarded in a group when a new product launches. That can survive a small team. It does not survive forty salespeople, product churn, and price changes every quarter.
Spreadsheets fail in the field for structural reasons: they are not on the visit record, they do not enforce current product rules, they do not sync when connectivity drops, and they create no audit trail when a dispute asks "who entered what, when?" WhatsApp captures intent but not structured product logic — and searching chat history is not operations.
Moving industry math into the order flow is how you stop treating corrections as normal operations.
Intelligent mobile order management in FieldAXIS ONE is built for salespeople at the dealer, not clerks at a desk. Orders are created during visits with live product visibility. For categories like plywood, the app computes Nett Area (NA), sheet counts, weight, and product-specific conversions as lines are added — no manual calculator, no post-submit HQ fixes for basic industry math. Drafts save server-side in real time, so a dropped connection does not erase twenty minutes of careful line entry in front of the customer.
From visit to dispatch without a translation gap
Industry math in the order form only pays off when the rest of the stack expects the same shape of data. A visit should start the workflow: check-in, outstanding context, then order lines that already speak the industry's language. When the order moves through lifecycle stages — pending, confirmed, clarification if needed, invoiced, delivered — each stage inherits the same NA and weight the salesperson captured, not a reinterpretation.
That alignment matters for building materials more than for uniform-pack FMCG because variance is the product. Two dealers ordering "the same SKU" may mean different effective NA depending on cut, mix, or bundle. Your system should encode what your business already knows about those conversions, not delegate it to tribal knowledge on the route.
On a Thursday beat, a salesperson adds three plywood lines at a dealer counter. The app shows NA and estimated weight per line and in the order summary. The dealer agrees to the total NA; the salesperson submits before leaving. Dispatch plans a truck using the captured weight; finance does not receive a "please recalculate" note at 6 PM. When the dealer reorders next month, one-tap history replays the same product logic — not a hunt through chat for last time's numbers.
What to ask before you buy another generic order module
If you distribute boards, plywood, laminates, or similar, feature checklists are not enough. Ask:
- Does NA compute inside the line item as dimensions and grade are chosen?
- Is weight derived from product rules, not typed freehand?
- Can the salesperson show the dealer an order summary they both understand before submit?
- Do drafts survive app restarts and weak networks without data loss?
- When products change, can ops update rules without a development project?
If the vendor's answer is "export to Excel for that," your field team will keep doing the math outside the system — and you will keep paying for both the licence and the rework.
The operational point
Building materials is not a niche exception to "normal" ordering. It is the core job for thousands of distributors. Field order forms should speak nett area and weight fluently because your salespeople and dealers already do. Putting that math in the flow is how orders become operational truth at the moment they are taken — not a rough draft someone fixes after the visit.
Teams that defer industry math to HQ often believe they are protecting data quality. In practice they are centralising rework — and teaching the field that the app is only a message to the back office. The distributors that scale cleanly are the ones whose first capture is already in the language of plywood, laminates, and boards: NA, sheets, weight, and a summary the dealer can confirm before the salesperson drives away.