You can adopt the hub on its own. The Customer Application only makes sense on top of it.
The Hub is the mailbox your dealers connect to and the system of record for everything that moves through it. If your partners already produce EDI, the hub is all you need — it carries the documents, isolates every partner from every other, and keeps an auditable history of every transfer and acknowledgement.
The Customer Application sits in front of it and answers a different question: what if the document does not exist yet? You have product data in a spreadsheet and a dealer who needs EDI. It converts one into the other, delivers it through the hub, and shows you every stage.
Secure mailboxes, per-partner isolation, document lifecycle tracking, acknowledgement correlation, notifications and an append-only audit trail.
What the hub does →Upload a catalogue, have it validated and converted to standard EDI, delivered to the right dealer, and tracked stage by stage.
What the application does →Worth saying at the top rather than in the small print: this is not an EDI translator. It does not map documents into your ERP's format, and that is a permanent boundary rather than a future release.
What it does instead is the part most flooring manufacturers actually lack — a trustworthy, isolated, auditable way to exchange documents with a long tail of dealers, most of whom have no EDI capability of their own.
Isogent · Plano, Texas