Network effects

Partner network that compounds

EDI is driven by the network: the more standardized profiles you ship, the faster everyone goes live. Each catalog profile encodes required transaction sets, fields, validations, and acknowledgements. When we publish a version bump, linked partners can pull updates automatically (cron or one-click sync).

Retail — PO / Invoice / ASN (network profile)

retail · SFTP · v1.2.0

Purchase orders, invoices, advance ship notices, and functional acks for typical retail supply chains.

  • Transaction sets: 850, 855, 810, 856, 997
  • Coverage: 3 segment groups · 3 validations · 3 ack rules

Healthcare — Claims & eligibility (837 / 835 / 270)

healthcare · API · v1.0.1

Claims, remittance, and eligibility inquiry patterns common to payer-facing workflows.

  • Transaction sets: 837, 835, 270, 271, 999
  • Coverage: 3 segment groups · 2 validations · 2 ack rules

Logistics — AS2 shipments (850 / 856 / 214)

logistics · AS2 · v1.0.0

AS2-first flows with shipment status and ASN emphasis for 3PL and freight partners.

  • Transaction sets: 850, 856, 214, 997
  • Coverage: 2 segment groups · 2 validations · 3 ack rules

Auto-updates

Partners created from the catalog store partnerProfileId and partnerProfileVersion on the trading partner record. When the catalog version increases, run POST /api/partners/{id}/sync-profile or schedule GET /api/cron/partner-profiles-sync with CRON_SECRET to merge new requirements. Full JSON for each profile: /api/partners/directory.