Field service

Requisitions from the job site, posted against the contract the ERP already owns

A specialty electrical contractor runs multi-year work from trucks. Each truck carries conduit, wire, breakers, and devices. Everything consumed has to hit the right contract and cost center. The ERP was fine at purchasing and job costing. It had no idea what was on a truck. So the field ran on text messages, and the warehouse spreadsheet was updated when someone had time.

Discuss a similar workflow

What was breaking

Material sitting on another truck got re-ordered because nobody could see it.
A text is not a requisition — it has no state, owner, or budget check.
Contract managers learned they were near budget after the material was already on site.
Replacing the ERP was not an option, and it was not going to grow a truck-stock module.

What changed

Field and warehouse look at the same on-hand number.
Approvals happen against a budget position, not a text thread.
The legacy ERP did not get replaced. It got the field data it never had.

Legacy ERP + mobile field app

What we built

A mobile app the crew will actually use

Today's scope, a material pull against the job, a restock request with quantity and urgency, hours, and a daily report. It queues offline and syncs when there is signal.

Requisitions with real states

Requested, awaiting approval, approved, picked, delivered, closed. Every request carries the contract and cost center, so approval shows the budget impact before anyone says yes.

One pool, two locations — ERP stays the ledger

Truck and warehouse stock share one inventory model with a location. Transfers are a movement, not an untracked event. The ERP remains the system of record; our layer proposes the consumption posting back to it.

Questions about this build

How do you track truck stock for an electrical contractor?

Truck and warehouse stock share one inventory model with a location, so a transfer is a recorded movement rather than an untracked event. That is what stops material being re-ordered because nobody could see it sitting on another truck.

Can this work with our existing ERP instead of replacing it?

Yes, and that was the requirement here. The ERP was already good at purchasing and job costing and was never going to grow a truck-stock module. It stays the ledger; our layer captures the field data it never had and proposes the consumption posting back to it.

Does the field app work without a signal?

Yes. Crews record material pulls, restock requests, hours, and a daily report offline, and the app queues them and syncs when there is signal. A field app that needs coverage to work does not get used on a job site.

Can material be posted against the right contract and cost center?

Every requisition carries the contract and cost center from the moment it is raised, and approval shows the budget impact before anyone says yes. That is the difference between a requisition and a text message: state, an owner, and a budget check.

More case studies

Construction

From blueprint PDFs to a tracked purchase order

Estimators were reading plans into spreadsheets, then emailing suppliers one by one. We built a desk where uploaded drawings become a reviewable material list, a quote, and a side-by-side RFQ — without another SaaS seat for each step.

Read the case study

Logistics

A freight desk that can answer what needs action

A freight team was running the day from Outlook, a TMS, and a status spreadsheet. We put an operations layer on top: inbound mail becomes a shipment, documents are readable, and the agent can explain what changed — with a human still on the send button.

Read the case study

Have a workflow that looks like this?

Tell us the tools, spreadsheets, or legacy systems in the way. We will say whether it should become one custom app.

Start a conversation