Skip to content
Rempel Automation

Case studies

Two operations. Two records they can trust.

The customers are not named. Details that would identify them are left out. What remains is the operational problem, the software, and the result.

FarmWork and FarmBridge are evidence of the practice. They are not a catalog you have to buy as-is.

Forklifts parked in a warehouse.
Industry photography, not a Rempel Automation client. Photo: TLSuda , CC BY-SA 4.0 .

FarmWork

Workforce time, piecework, and payroll for a seasonal agricultural employer.

Problem
Hours, piece counts, and shared production lived in separate lists. Payroll reconstructed the week by hand.
What we built
Office web app plus a native field app with offline sync. One record from clock-in through a Sage-shaped pay file.
What changed
Payroll reviews exceptions and exports. The floor still owns the clock and the count.
Read the case study

FarmBridge

Receiving, inventory, processing, shipping, and floor automation for a packing operation.

Problem
Clipboards from intake to load-out. “Where is that bin?” was a walk-around. Hardware was not part of the record.
What we built
One lot trail from receiving through shipping, handheld scan, dock hardware, and flows the shed can author.
What changed
Location, age, and quantity on screen. Load-out is a move plus an allocation on the same trail.
Read the case study

If harvest, labour, inventory, or shipping still live in three places, talk with us.

Contact us