The portal was supposed to end the ‘did you get my order?’ phone calls. Six months in, the calls are still happening, and now there’s also a portal to keep up to date. Before building another one, it’s worth listing what else does the same job, because most of the alternatives are already running in your business whether you chose them or not.
Five of them are below. Email and a PDF, EDI, a shared spreadsheet, WhatsApp with a written order format, and a shared order book that both sides can see. Each gets the same treatment: how it works, who it suits, and the catch, because every one of these has a catch and the catch is usually what decides it.
One thing to hold onto while you read. The job isn’t “have a system”. The job is to know, at any moment, whether an order is confirmed, shipped or invoiced, and to have the supplier agree with you about it. Portals fail at that job for a reason that has nothing to do with their features: the work lands on the supplier, and it recurs forever. Any alternative you pick has to be judged on the same axis.
Email and a PDF
The default. You raise a purchase order, export it as a PDF, attach it to an email and hope somebody on the other end opens it. The supplier replies “received, will dispatch Friday”, or doesn’t. Roughly nine out of ten small businesses that have never bought procurement software are running this, and it has been running like this since fax machines.
It suits anybody with a handful of orders a week and suppliers who live in their inbox: larger manufacturers, importers, printers with an office. It costs nothing, it produces a document both sides can file, and the PDF is a genuinely useful artifact when a dispute starts. Nobody has to be trained. Nobody has to register.
The catch is that nothing in it is structured. An email thread knows it contains messages; it doesn’t know it contains an order with a status. So finding out whether PO-1042 was ever acknowledged means opening a search box, guessing at a phrase, and reading. Multiply that by thirty live orders and your answer to “where are we with this?” becomes a person going through a mailbox. Email also gets slower the more it matters: it sits behind spam filters, gets buried under newsletters, and lands on a laptop the supplier opens twice a day. Plenty of small suppliers barely use it at all. They run the business off a phone.
EDI
Electronic data interchange is the grown-up option: your system sends a structured 850 purchase order, their system sends back an 855 acknowledgement, and a 856 when it ships. No human retypes anything. When the volume is real, EDI is genuinely the right answer, and it’s why every supermarket chain runs on it.
It suits buyers with hundreds of order lines a week and a stable base of suppliers big enough to already have the capability. If you’re trading with someone who supplies Walmart or Tesco, they have EDI, and asking for it costs them almost nothing.
The catch is everybody else. EDI needs a translator or a VAN, a mapping project per trading partner, and someone to call when a document fails validation at 6pm on a Friday. Pricing is quote-based and setup fees may apply; nobody publishes a sticker price, which tells you something. For a supplier doing eleven orders a month for you, the economics are absurd, and they’ll say so politely and then keep emailing. If you’re on the receiving end of that request and can’t justify it, there’s a simpler acknowledgement flow that does the same job.
A shared spreadsheet
A Google Sheet, one row per order, the vendor added as an editor. Columns for item, quantity, agreed price, expected date, status. They update the status column, you watch it change. It’s free, it’s structured, and it takes about twenty minutes to set up.
For one vendor you order from constantly, this is better than most software. A single fabricator, a single packaging supplier, a single freight agent. Both sides see the same rows, and you can sort by expected date and see today’s problem in one screen.
The catch arrives at vendor number two. Now you either invite them into the same sheet, which means vendor A can read vendor B’s prices, or you run a sheet per vendor, and you’re back to having no single view of your open orders. Neither is workable past a handful of suppliers. The other catch is that a spreadsheet has no memory of who changed what: someone overwrites a quantity, the old one is gone, and the version history is technically there but nobody has ever once opened it. A tracker you run yourself, without vendor access, avoids all of that and gives up the live updates. The spreadsheet-versus-software comparison has a column layout you can copy, and an honest account of where it stops working.
WhatsApp with a written order format
This is what most small businesses actually do, whether or not they admit it in a meeting. The order goes out as a message. The supplier replies. The difference between this working and this being chaos is entirely down to whether the message has a format.
Use something like this, every time, with no variation:
Five things are in there: what, how much, at what price, by when, and where. A reply that repeats them back is a confirmation. A thumbs-up is a receipt that someone’s eyes passed over it, which is a different thing entirely and the source of more short deliveries than any other habit in small business buying.
WhatsApp suits almost everyone, and that’s the whole argument for it. Your suppliers already have it open. Reply rates are the reason suppliers answer there and not in your portal, even when your portal has a perfectly good message box. Nothing to install, nothing to remember, no password reset in March.
The catch is the record, or rather the absence of one. A thread is a conversation, and a conversation with five live orders in it can’t be filtered, sorted or handed to a colleague. The history also belongs to a phone number rather than to your business, so when the person who does the ordering leaves, so does everything they agreed. You can fix this by hand: send on WhatsApp, log in a tracker. It works, and it costs you a minute of double entry per order, forever.
A shared order book
The newest of the five and the one that tries to keep WhatsApp’s reach while fixing its record problem. One order exists once, in a system. Both parties see it, each from their own side: you see an order you placed, the supplier sees an order they received. The message still goes out over WhatsApp, because that’s where they are, and it carries a link that takes one tap to acknowledge. No account required to answer. If the supplier does have an account, the order simply appears on their board and the acknowledgement is a button.
It suits businesses with more than a couple of suppliers who want a filterable list of open orders without asking anyone to log into anything. It suits the two-sided case especially: if you buy from some businesses and sell to others, a portal built by you only ever solves half your day.
That’s the shape OrderBookApp takes, and yes, it’s ours, so weigh the next sentence accordingly. The catch is that it’s one more place to look, and if nobody on your side keeps the statuses honest, the board goes stale the same way a spreadsheet does. Software doesn’t create discipline. It just makes the discipline cheaper to maintain.
Comparison
| Option | Cost | Setup | Effort for the supplier | Structured record | Works both directions |
|---|---|---|---|---|---|
| Email + PDF | Free | None | Low: open an attachment, reply | No | Yes, informally |
| EDI | Quote-based; setup fees may apply | Months, needs an IT partner | High unless they already run it | Yes, fully | Yes |
| Shared spreadsheet | Free | An afternoon | Medium: a login, and remembering to update | Partly | No |
| WhatsApp with a format | Free | None | Lowest of the five | No | Yes |
| Shared order book | Free tier, paid for teams | An hour | Low: one tap, no account needed | Yes | Yes, by design |
| Buyer-built portal | Quote-based at the enterprise end | An IT project | Highest: register, learn, log in monthly | Yes | No |
The portal row is there for contrast, and the “effort for the supplier” column is the one that predicts whether any of this survives contact with reality. Spend Matters found that 60% of suppliers have to log in to at least 10 portals per month. Your portal is number eleven. The Leverage blog put it more bluntly: the cost doesn’t sit with you, it sits with the supplier, and it recurs forever.
Choosing between them
Two questions get you most of the way.
First, how many suppliers do you order from regularly? One or two, and a shared spreadsheet plus a disciplined WhatsApp format is genuinely enough; don’t buy anything. Five to fifty, and the spreadsheet approach breaks down on the privacy problem and you want a single filterable list. Hundreds of order lines a week with large partners, and EDI starts paying for itself.
Second, do you also sell? A surprising number of small businesses do both: the wholesaler who buys from importers and sells to shops, the fabricator who buys steel and ships brackets. If that’s you, anything you build only for the buying side leaves the messier half of your week untouched. Orders you receive arrive as voice notes, photos of handwritten lists and “same again”, and no purchasing tool has an opinion about that.
Third question, which I said there were two of, so consider this a bonus. What happens when the order changes after you’ve sent it? Gartner has found that 50% of purchase order lines undergo changes after issuance, which means half your orders will need a second round of agreement. Options that handle a change well are worth more than options with a prettier first screen. Email handles changes badly, since the revision lives in a reply three messages down. A spreadsheet handles them silently, which is worse. A message with a format handles them fine as long as you re-send the whole order and not just the delta.
Nobody picks one of these and stays there. You’ll end up with two: a structured record on your side, and whatever channel each supplier actually answers. The mistake is expecting one tool to be both, which is exactly the mistake the portal made.
Keep reading
- Why vendor portals fail (and what your suppliers do instead) explains the cost problem that sinks most portal projects before year two.
- Portal fatigue: why your suppliers reply on WhatsApp instead is the same story told from the supplier’s side of the login screen.
- PO acknowledgement without EDI: a simple flow for small suppliers is what to send a customer who’s asking you for capability you can’t afford.