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.
Every major retailer — Walmart, Target, Kohl's — requires EDI compliance to do business with them. Purchase orders, invoices, ship notices, acknowledgments: all of it runs through a 40-year-old standard that was designed by specialists, for specialists. A small business that wins its first retail contract typically discovers this the hard way.
A golf startup won a Kohl's deal. To fulfill it, they needed EDI. That meant a 90-day professional services engagement, a specialist team, and infrastructure they couldn't afford or staff. They had days.
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 in 2021, Orderful had a strong API-first technical foundation and an onboarding experience built for EDI engineers. The problem: most customers weren't EDI engineers. Configuration required navigating ISA IDs, X12 transaction sets, VAN credentials — terminology most users had never encountered.
Time-to-revenue averaged 90 days. Every new trading partner relationship required Orderful staff involvement at multiple steps. That's a professional services model disguised as a SaaS product. It couldn't scale.
And there was an entire market the product couldn't touch: small vendors who needed retail EDI compliance but had no technical team. The golf startup doesn't have an EDI specialist. Neither does the boutique apparel brand that just landed its first Target order.
Onboarding was slow because the product asked users to make decisions without giving them the context to make them. Every ambiguous field, every open configuration choice, every "configure this" instead of "here's the default" was a place where a user stopped and waited for help. I mapped every one of those moments before touching wireframes.
Four steps: create account, set up profile, configure trade connections, select a plan. Simple on the surface. Each step is also qualifying and routing users for what comes next — so the platform can give them the right experience before they've asked for it.
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.
Vendors were manually chasing EDI specs from every trading partner. ISA IDs, communication channels, transaction requirements — all of it gathered by hand, per partner, every time. We automated the whole exchange. Trade request goes out, requirements go with it. What took days became one click.
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 — accessible 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.
No design function when I joined. I built it: design system, component library, research practice, cross-functional process, and a freelance team I managed throughout. $1M to $10M+ ARR during my tenure. Onboarding and activation were the primary lever. The 90-day professional services engagement became 9 days of self-serve. That's the whole story.