Onboarding Step 03 — Setup Trade Connections. The binary split-path that routes users based on their EDI context. "I'm New to EDI" is the WebEDI entry point — the design decision that unlocked the new market segment entirely.
Four years building the design function from scratch at a Series A/B EDI infrastructure company — and unlocking an entirely new market by putting enterprise-grade tools in the hands of small businesses that had never touched EDI before.
Electronic Data Interchange — EDI — is the invisible infrastructure of retail. Every major retailer, from Walmart to Kohl's to Target, requires it. It governs how purchase orders, invoices, ship notices, and acknowledgments flow between trading partners. It is, by design, impenetrable to anyone who isn't a specialist.
When a small golf retail startup won a contract with Kohl's, they hit the wall every growing vendor hits: to fulfill the order, they needed to be EDI compliant. That typically meant a 90-day professional services engagement, a specialist team, and infrastructure that most small businesses couldn't afford or staff. They had days, not months. And they had no EDI team.
The problem wasn't that EDI was technically hard. The problem was that every tool built for EDI was designed for specialists, not for the businesses that actually needed to use it. WebEDI was the answer: a guided document creation tool that let any vendor achieve EDI compliance in minutes, with no prior knowledge required.
This is the case study of how we rebuilt Orderful's onboarding from a 90-day professional services engagement into a self-serve platform that any business could navigate — and how WebEDI opened the door to a market that traditional EDI infrastructure had always locked out.
When I joined Orderful in 2021, the company had a compelling vision — modernize EDI with an API-first platform — and a product that reflected where it had come from: a tool built by EDI engineers for EDI engineers. Onboarding required deep technical knowledge. Configuration meant navigating ISA IDs, X12 transaction sets, VAN credentials, and communication channels that most users had never heard of.
The result: time-to-revenue averaged roughly 90 days. Getting a new trading partner live meant a guided professional services engagement, extensive back-and-forth between teams, and a setup process that required Orderful staff at every step. That wasn't scalable — and it was a ceiling on growth.
There was also a market the product simply couldn't reach: small and mid-size vendors who needed EDI compliance to sell through major retailers, but had no technical team to implement it. The golf startup. The boutique apparel brand. The emerging food company that just landed its first Target order. They were being locked out.
Before touching wireframes, I needed to understand why onboarding was slow. It wasn't that users were incapable — it was that the product asked them to make decisions they didn't have the context to make. Every ambiguous field, every open configuration choice, every moment where the product said "configure this" instead of "here's the answer" added friction and delay.
The signup flow is deceptively simple. Four steps: create account, set up profile, configure trade connections, select a plan. But each step does more than collect information — it qualifies, routes, and prepares users for what comes next.
Step 02 collects business context — business type, public name, and critically, number of trading partners. That last field isn't just data collection. It's the first signal we use to route users toward the right plan and experience. A company with 200 trading partners needs a fundamentally different setup than one connecting to their first retailer.
Step 03 is the pivotal split: "I Currently Have an EDI Provider" vs. "I'm New to EDI." This single design decision opened the WebEDI market. Existing users get a migration path. New users get a guided, no-expertise-required experience. The platform stops trying to be one thing for everyone.
The core of the onboarding transformation was the post-signup account setup experience: a six-step guided checklist that walked users from zero to their first live transaction. Each step had a default path — "Use Orderful Defaults" — for users who didn't need to customize, and a configure path for those who did. Progress was tracked visibly. Documentation was linked contextually. Nothing required a support ticket.
One of the highest-leverage decisions was automating the trade request delivery. Previously, a follower (vendor) joining the platform had to manually gather their trading partner's EDI requirements — ISA IDs, communication channel details, transaction specs. We automated this entirely: when a trade request is created, all requirements are packaged and delivered automatically to the recipient, pre-populated and structured.
As customers scaled on the platform, they needed to manage not one trading partner but dozens — sometimes hundreds. The Trade Requests interface gave them full visibility across inbound and outbound requests, with scenario checklists, document relationship maps, and status tracking all accessible from a single view.
The Create Trade Request flow embedded the "Leader vs. Follower" model — a core Orderful concept — into a guided modal that non-technical users could navigate without understanding the underlying EDI architecture. Search by company name, select your role, and the platform handles the rest.
WebEDI — Order Fulfillment — is the tool that made the Kohl's deal possible. A guided interface for creating EDI transactions without technical knowledge. A vendor receives a purchase order from a retailer, fulfills it step by step, and sends back the required documents — 855 acknowledgment, 856 ship notice, 810 invoice — without writing a line of code or understanding X12 transaction sets.
The plan selection screen reflects the design thinking: WebEDI is positioned as the entry point for any business just getting started with EDI. "Up and running in minutes. No integration required." That's not marketing copy — it's a design promise we built the entire tool to keep.
"With Orderful, we have visibility and control over our EDI. It's great to finally own the keys to the kingdom and not rely on outside parties."Derek Wu — Business Applications Manager, Liquid Death
The Order Fulfillment interface shows the platform at scale: 1,109 orders active, 550 completed. Purchase orders from Walmart. Workflow status tracked across every transaction step. Validation errors surfaced inline with clear remediation paths. For a small vendor, this was infrastructure they could never have built themselves — delivered through a web interface they could use on day one.
The 856 Advance Ship Notice screen is WebEDI in its most detailed form: a structured, guided document creation interface that walks a vendor through shipping details, item quantities, package information, and transaction references. Every field is labeled. Every section is collapsible. The workflow status bar at the bottom tracks where this document sits in the broader order lifecycle.
When I joined Orderful, the design function didn't exist. I built it from scratch — the systems, the process, the cross-functional rhythms, the freelance team that expanded and contracted with the product's needs. The goal was always to make the design function invisible in the best sense: to produce a product so clear and so well-considered that onboarding felt effortless, and growth felt inevitable.