Musselburgh, MidlothianSoftware & portals for communication across food supplyMon–Fri 09:00–18:00
FoodLocality

Field notes

Practical notes for people planning supply software

Answers we give often, useful whoever builds your system.

Ripe tomatoes on a steel work surface beside green crates of salad leaves
Illustration, AI-generated

Starting

Before you commission anything

What should we fix first?
The single conversation that causes most waste or awkwardness each week. Often availability or late changes.
Should we buy an existing ordering platform?
If your network fits its model and its fees work for your participants, possibly. Bespoke makes sense for distinctive networks or where you want no commission on trade.
How do we get suppliers to use it?
Make it easier than a phone call. Involve two or three suppliers in testing and let them shape the screens.

Running

Once it is live

Who should own product lists?
Each supplier owns theirs, with an administrator able to help. Stale lists are the commonest cause of distrust.
What about people who will not use it?
Allow an administrator to enter orders on their behalf, so the record stays complete.
How do we handle connectivity?
Choose tools that show clearly whether a message has been sent, and agree a fallback channel for outages.

Money

Budgeting

What drives cost?
Number of participant types, connections to other systems and complexity of pricing rules.
What does it cost to run?
Hosting, any text-message fees and support. We estimate these before you commit.
Can costs be shared across a network?
That is a decision for your network; we can structure releases so that early phases deliver value quickly.