Learning a new business system — Patter

The case

You built those spreadsheets. You know which tab has the live stock figures and which one hasn’t been touched since 2019. You know the formula that breaks if anyone adds a row in the wrong place, and you’ve quietly fixed it every time. For years, knowing the numbers meant coming to you.

Then the company moves to a new system. Suddenly the data lives somewhere else, enters through forms you didn’t design, and updates in ways you can’t immediately follow. Everyone gets a login. The thing that made you the person to ask is now, in theory, self-service.

That’s a hard transition. Not because the new system is worse — it probably isn’t — but because expertise that took years to build feels like it’s been quietly redistributed overnight.

It hasn’t. What you know about the business, the data, the flow of an order from inquiry to invoice — none of that disappears. The routine here is about getting that knowledge back on solid ground in a new environment. One step at a time, until the new screens feel as familiar as the old tabs.

Processing a Shipment End to End

Log in and check the dashboard What's open, what's overdue, what needs action today. Get the shape of the day before touching anything.
Open the incoming order or inquiry Find it in the system. Note where it sits in the workflow — status, assigned to, last updated.
Check the supplier record Is the supplier already in the system? Correct contact, payment terms, currency. Flag anything missing.
Check stock or availability Against what's in the system, not what you remember. Trust the data — or flag it if something looks wrong.
Create or update the purchase order Fill in every field. The system can't work with gaps. Notes fields exist for a reason — use them.
Confirm pricing and currency Check against the supplier's last invoice or agreed rate. Exchange rates change. Don't assume.
Log the expected delivery date Realistic, not optimistic. Everything downstream depends on this number being right.
Attach the relevant documents Proforma, packing list, bill of lading — whatever you have at this stage. One place, not three email threads.
Update the shipment status Wherever it is in the workflow — ordered, in transit, at customs, cleared. Keep it current.
Check customs and compliance fields HS codes, country of origin, any certificates required. This is where gaps cause delays.
Notify the relevant team members The system may do this automatically. Check that it did. Don't assume a notification went out.
Create or match the sales order Link it to the purchase order where the system allows. The connection matters for reporting.
Check the invoice when goods are received Against the PO. Quantity, price, currency. Approve or flag a discrepancy before it goes to accounts.
Close the shipment record Mark it complete. Add a note if anything was unusual — delays, substitutions, pricing changes. Future you will want to know.
Review what the system did automatically What reports updated, what alerts fired, what the dashboard now shows. This is how you learn what the system knows.

Make it yours

The first time through, go slowly. The goal isn't speed — it's building a mental map of where things live and how they connect. The system is doing more in the background than is immediately visible, and step 15 is the one that starts to make that visible.

As the process becomes familiar, some steps will collapse into habits — you'll check the supplier record without thinking about it, the way you used to know which tab to open first. When that starts happening, remove those steps or fold their notes into adjacent ones. The routine should get shorter the more you use it.

If your business handles multiple shipment types — sea freight, air, courier, domestic — consider building a separate routine for each. The core steps stay the same; the compliance and documentation steps change. One template per type is cleaner than a single routine with conditional notes throughout.

The knowledge you had in the spreadsheets isn't gone. It's the reason you'll spot when something in the system looks wrong before anyone else does.