Any? 
Soooo, I’m not a big fan or FTP or other shared folders to do work - mostly because it increases your attack surface. There’s a username and password to manage, supply-chain vulnerability with OS software, ports to open, etc. 
I would take a page from the design of Epicor printing. Generate the .bt “file” and store that in a Character or _c field in a .UD table with information on about the label: what template, who generated it, workstation (or some other destination identifier), when it was created, and a status field. The status field would initially contain something like “Ready”.
Next (and you knew this was coming), I would create a function that looks for Ready records and pulls down the file over https. It’s easily scheduled for polling and you can use PowerShell or wget or whatever. The function would change the status to “Printed” and update a timestamp to “Printed”.
Better than polling would be a webhook where every time a record was written/updated with a status of “Ready” would send an event action to a site (think Azure Logic App) that would then pull and print the label. The login information and API-Key would be store in Azure Key Value. (I’m not sure if Epicor can use a managed identity to login though. )
The added bonus doing it this way is having the ability to reprint an invoice just by changing the status back to “Ready” in the UD table right from a form in Epicor.
Like printing, there would be a job that would delete “Printed” records after some given amount of time.
No usernames/passwords, no extra software, reprint capability, … Just a thought.
Mr. 