About Safock
Safock designs Bollard and configures it for each customer. We work with organisations that buy and hold stock across many sites and need firm financial controls without slowing down the people who do the buying.
A bollard is the short iron post on a quay that a ship's mooring line is made fast to. The tide rises, wind leans on the hull, the current pulls. The ship moves a little with all of it. The post does not.
Spend drifts the same way. A price agreed in March is a few cents higher by June. A short delivery is invoiced in full. An approval happens in a chat thread nobody can find later. None of it is dramatic, and all of it adds up.
Bollard is the fixed point in that drift. The price on the purchase order, the quantity accepted at the door and the limit an approver signs to are made fast, and every later document is held to them. The round post in the b of our wordmark is that bollard.
How we build
Each one costs us something in speed or convenience. We keep them because they are what makes the numbers trustworthy.
If a control matters, the database enforces it: approval limits, the three-way match, site access and the audit trail. Nobody can click, script or export around it.
In practice
Not even an administrator can delete an audit entry.
Your team should recognise their own work the first time they sign in. We set names, roles, approval chains and site labels to match how they already talk.
In practice
A chef sees Unit and Commissary. A lab technician sees Campus.
No big-bang rollouts. We go live on one real site, check that requests, receipts and matching hold up, and only then add the rest.
In practice
The pilot runs real orders, not a sandbox.
Suppliers are held to the price they agreed. If an invoice drifts by a few cents, or bills for goods your team rejected, payment stops until it is put right.
In practice
Matching is per line, so a small overcharge can't hide in a large total.
You talk to the engineers who build and configure Bollard. If something isn't built yet, we say so and tell you what it would take.
In practice
Your discovery call is with an engineer, not a script.
The test we apply
Would a finance controller trust this number without checking it by hand?
Implementation
A short, fixed plan. Choose a phase to see what we do, what we need from you, and what you have at the end of it.
Days 1–3
By the end
A written configuration you can read and sign off.
Days 4–7
By the end
Requesters see only approved items, at the prices you agreed.
Days 8–14
By the end
One site running request to payment, with invoices matched.
Day 15 onward
By the end
Every site on one record, with the match enforced everywhere.
Tell us how you buy and store today. We'll walk you through Bollard configured with your sites, roles and approval rules.