CASE STUDY · RBC EGGS
An egg farm’s order desk, rebuilt in a few weeks.
Rochfort Bridge Colony sells wholesale eggs to grocery stores across Alberta under the RBC Eggs name. I built rbceggs.ca and the system behind it. Orders, pallets, trucks, invoices and payments that used to be handled by hand now run as one flow.
Done by lunch
The day’s orders, trucks, invoices and payments can all be wrapped up by lunch.
Tens of hours
back every week, as reported by RBC Eggs.
Thousands recovered
in discounts stores had taken without agreement, caught by the payment matching.
BEFORE
Every step by hand
One person did all of it, and a lot of it got typed twice. In the seven months before the switch, more than 1,100 orders went through this way.
- Orders came in by phone and text, then got typed into a spreadsheet.
- Orders were split into pallets on paper, and every label was typed by hand.
- Trucks were planned by hand.
- Invoices were typed up, then typed again into customer portals.
- Each store’s prices were tracked separately.
- Payment advices were matched line by line. Stores took adjustments for old invoices off new payments, and sometimes paid the wrong amount.
- Putting together a mock recall meant digging through paper and spreadsheets.
FOR THE STORES
Ordering takes a minute
- Stores order online, with cut-off times and delivery days built in.
- Each store’s own prices apply automatically.
- Phone orders go into the same place, and duplicates get caught.
FOR THE FARM
From order to truck
- Orders are split into pallets, with lot and best-before labels for traceability.
- Trucks are loaded by drag and drop, and the labels update to match.
- Drivers get the delivery route on their phone and mark each stop.
FOR THE OFFICE
From invoice to paid
- Invoices come straight from the order, ready for customer portals.
- Payment advices are imported and matched to invoices. Adjustments to old invoices and wrong amounts are tracked and shown.
- Every store’s balance and payment history is in one place, and statements are ready to print.
- A mock recall comes from records that are already there.
IT KEEPS WATCH
It notices what a busy person misses
- A store that usually orders but hasn’t.
- An order much bigger or smaller than that store’s usual.
- A payment that doesn’t match what was agreed.
That last one found real money. Some stores had been taking bigger discounts than they had agreed to, and it added up to thousands of dollars.
Adding a new store, price, product or truck is something they do themselves, without calling me.
IN THE OWNER’S WORDS
“I didn’t realize how much of my day went into it.”
“Orders came in by phone and text. I’d put them in a spreadsheet, split them into pallets on paper, type up labels, plan the trucks, type up invoices, then type them all again into the store portals. Then I’d sit with the payment advices trying to figure out who paid what and what they’d taken off. I didn’t realize how much of my day went into it until Jamie built the system. Now I can be done by lunch, and I’ve got more time for my family. It caught stores taking discounts we never agreed to, and that was thousands. Mock recalls used to take hours of digging. Now it’s all right there. When we need something changed, we call Jamie and it gets done.”
— Sammy Wurz, Owner, Rochfort Bridge Colony
WHAT IT LOOKS LIKE
The screens they use every day
The website stores order from, and the system behind it, shown here with sample stores.
Have a process like this?
Most businesses do. Tell me about yours.