Shipping and receiving, run from a phone on the warehouse floor

When a build was done, the job went dark

For everything we had wired up on the production side, there was a blind spot right at the end: the moment a build was finished, the job went dark. Was its shipment set up? Had it left the building? Was it paid for? Where were the photos? There was no one place to answer any of it - you asked around, or you went and looked.

A finished build used to just go dark - nobody had one place to see what shipped, what was still sitting, or what came in short.

Shipping and receiving ran on paper and phone calls

A finished job takes one of two paths - it ships out to a customer, or it's a local pickup - and both ran on paper and phone calls. Receiving was the same story: a delivery showed up, and a partial or damaged one only got caught if someone happened to notice and remember to say something. None of it was written down anywhere you could pull up later.

One board for what's built, staged, and shipped

So we built one board for the whole outbound side. Every job moves across it in plain stages - built, staged, shipped or picked up - and each card carries what you actually need to know: whether it's paid, how many photos are attached, and its tracking. The shipping clerk opens one screen and sees the whole floor's outbound status at a glance, instead of chasing it down job by job.

Receiving, run from a phone on the floor

Receiving moved onto the phone in your hand on the warehouse floor. You pull up the purchase order, receive it line by line, and mark anything that came in short or damaged right there - with photos - instead of carrying a clipboard back to a desk to type it in later. When you're done, it updates the inventory in our system of record on its own. The work happens where the boxes are.

No shipment goes out without a photo

A couple of guardrails make it trustworthy. A shipment can't be marked shipped without at least one photo, so there is always proof of what left and in what condition. Those photos get taken with no corporate login - the floor crew scans a code and uses their own phone - and a photo taken on flaky shop wifi is saved safely before it uploads, so nothing is lost in a dead spot. Two separate security reviews went over all of this and caught real issues before any of it shipped.

The floor crew shouldn't need a corporate login to photograph a box. They scan a code and use their own phone - without creating a security risk.

We almost built a parser for data we already had

The best lesson was a piece of work we almost did and didn't need to. We set out to read the carriers' tracking emails to pull in shipment status - and those emails strip out the reference number, so it looked genuinely hard. Then we realized the clerk was already typing the contract number into the shipping portal when they set up the shipment, which meant the portal's own data linked itself back to the job. We were about to build a fragile parser for information we already had. Always check whether the data exists somewhere clean before you go scrape a messy copy of it.

The tracking emails stripped the reference number. But the clerk was already typing the contract number into the portal - so the portal's own data linked itself. We were about to process a copy of data we already had.

Build for where the work happens, and go to the source

Two lessons worth keeping. First, build for where the work actually happens - if the job is on the warehouse floor, the tool belongs on a phone, not on a desktop back in the office. Second, go to the source, not the lossy copy - the cleanest version of your data is usually already sitting in a system you own. Get both right and the job stops going dark, and nobody has to walk to a desk to write down what they just did.