Why email with PDF still dominates
Every company has a handful of large customers using EDI or a portal. But look at the long tail: the SME customer, the foreign supplier, the regular buyer who has followed the same workflow for ten years. They send a PDF by email. Sometimes a Word document. Sometimes a screenshot. That does not change overnight, no matter how well-designed your portal is. Email with PDF is low-friction on the sending side: no account needed, no login screen, no training. That is precisely why it persists. The downside is that someone on your side has to read that document, extract the right fields, and manually enter them into the ERP, TMS or WMS. At a hundred documents per week, that is a significant time cost.
Customer portal order entry: who is actually doing the work?
A customer portal looks like the clean solution: the customer enters their own order, you do not have to type anything. But pay attention to what actually happens. The work does not disappear, it shifts to the customer. They have to log in, learn a new screen, and re-enter their order into your system, even though they already created that order in their own system. Larger customers will not accept that. They do not want an extra step for your convenience. Smaller customers may go along with it, but only if the portal is easier than sending an email, and that is rarely the case. Portals work best when the customer relationship is structural, the volume is high, and you as the supplier have enough leverage to drive a change in behaviour. In transport and wholesale, that applies to a minority of counterparties.
API integration: the cleanest route, but not for everyone
A direct API connection between two systems is technically the best channel: structured data, no manual work, no conversion loss. But it requires development effort on both sides. Your ERP or TMS needs to offer an API, the counterparty needs to build or commission that integration, and both parties need to align on the message format. That takes time and money. For large, strategic trading partners, that investment pays off. For the rest of your customer base, it does not. On top of that, if one party pushes a system update, the connection can break. APIs are robust at scale, fragile at the margins.
Document AI as a bridge: what does it solve, and what does it not?
Document AI is not a replacement for a portal or an API. It is the practical bridge for as long as not everyone works through a structured channel, and for most companies that will remain the reality for years to come. dottle reads incoming PDFs, emails and other document formats, converts the data into structured output, and delivers it to the ERP, TMS or WMS. Without anyone having to retype anything, and without the customer needing to do anything differently than they always have. A human approves the result: exceptions are flagged, not hidden. That is a deliberate choice. Errors in orders or invoices are costly; oversight remains necessary. What document AI does not solve: if the source data is structurally poor, if a supplier sends a different format every time with no readable structure, or if the volume is too low to justify the setup time.
Decision tree: which channel fits which situation?
Use this rule of thumb to choose the right channel for each counterparty. High volume, strategic partner, both parties have an ERP with an API: choose a direct integration or EDI. Large, established customer base that you can steer behaviourally and where straightforward order entry is sufficient: consider a portal, but honestly assess willingness to adopt. Varied customer base, many SMEs, mixed document formats, no capacity for custom integrations: use document AI to process email and PDF automatically. The three channels are not mutually exclusive. The most practical approach combines them: API for the major players, document AI for the long tail of email and PDF. The portal earns its place only if you can genuinely drive customer behaviour, not as wishful thinking.