Skip to main content
Available EDI partners will be listed here over time.
EDI automates the exchange of standardised documents with your customers, typically large retail chains. Files transit through an SFTP drop: your partners place their orders there, Bonx places its dispatch advices.

Authentication: SFTP

Username and password or a private key, with the host and the agreed folders (inbound, outbound, archive, errors). See authentication methods.

​
Messages and data

​
Business behaviour

  • Articles are identified by EAN and pack size. Resolution runs in cascade: the EAN + PCB pair, then the EAN alone, then the supplier article code, and otherwise the article is created. See the EAN and pack size guide.
  • Quantities and prices are converted to packages. A line of 120 units at PCB 12 becomes 10 packages priced per package, with the total unchanged. On dispatch, the reverse conversion applies.
  • Unknown partners are created from their GLN, with a name carrying that GLN so you can rename them properly afterwards.
  • The site comes from the configuration, not from the file: the delivery points described in an EDI message are your customer’s stores, not your own sites.
  • A file is archived only once fully integrated. On an incident it stays in the inbound folder and is replayed on the next cycle, without creating duplicates. An unreadable file goes to the errors folder without blocking the others.
  • Only firm orders are processed; order changes and order responses are skipped with a warning.