EDI com o varejista

It connects your company to the large retailer through the VAN (Neogrid and similar). Their order comes in by itself every 15 minutes and becomes a sales order; the shipping notice and the invoice go back to them the same way.

Create the channel: the retailer, your company's GLN, theirs, the VAN's SFTP address, the user and password (stored encrypted; the password never comes back to the screen) and the inbound and outbound folders. No credentials yet? Choose "Simulated VAN" to rehearse.

The shipping notice only comes from a checked dispatch (boxes with SSCC matching the order). The invoice only comes from an authorised tax invoice. Both stay in the message list and go to the VAN in the next cycle; the retailer's confirmation changes the status to Confirmed.

Ask the VAN provider for the SFTP address, the user, the password or private key, and the server key fingerprint (SHA256:… or the known_hosts line). Register all of it in the channel. The server key is mandatory: confirm it with the provider and never copy the one shown on the first connection without checking. The private key is optional and replaces the password (OpenSSH or PKCS#8 format, no passphrase). If the server key does not match, the integrations hub shows "the VAN did not accept the connection".

Each order file that arrives through the VAN, or is pasted on the screen, has a size limit: 5 MB by default. Above it the file is rejected without being opened: the message shows as rejected with its size and the limit, and the rejection goes back to the retailer. Ask the retailer to split the order into smaller files. If your operation needs larger files, adjust the limit in Parameters (EDI.TETO_BYTES, in bytes).

An order with any unmapped GTIN does not come in half: it stays in "Mapping pending" with the list of GTINs. Say which variant (colour and size) each GTIN is and click "Process again"; the order comes in whole. The item's closed size pack still applies.

When editing the channel, leave the password and private key blank to keep the ones already stored. They are never shown on screen again; to change them, type the new one.

A link to this screen with a document number (the retailer's order, the UNB interchange, the UNH message or the number of the created order) shows only that document's messages. The filter appears above the list, with the "Show all" button to go back to the whole list. The retailer's receipt reply (CONTRL) shows as "Reply read".

If the VAN does not respond for more than two cycles (30 minutes), the integrations hub shows the warning. Without credentials, the channel can run in "Simulated VAN" mode to rehearse the flow without talking to anyone; the screen says it is simulated.

Right after deleting, the Undo bar shows for 15 seconds. After that, the channel is under "Channels in the recycle bin", below the channel list: click Restore and it collects again in the next cycle. The channel messages are never deleted.

The VAN must be a public internet address, given by the VAN provider. An internal network address (localhost, 10.x, 172.16 to 172.31, 192.168.x, 169.254.x) is refused: a connection there would leave Tenka and come back inside.

In the simulated exchange there is no retailer on the other side: the receipt acknowledgement and the order reply are marked as sent as soon as the pasted order is received, noting that nothing left the company. In a real exchange they go out through the outgoing folder in the 15-minute cycle.

Ask "which EDI orders have a GTIN without mapping?". The answer gives each order with the retailer’s number, the channel and the missing codes, and the way to this screen to set the variant for each code. With no held order, the answer says nothing is pending.