6 votesJerry Marks Revival Parts shared this idea ·
So, just to help us better understand, would this idea work best for you if it automatically printed whenever an order came in? So, say, an order comes in on Sunday at 4:00 a.m., it should print then. Or would it be better if whenever you log in to ShipStation and have it active that you would prefer to have the packing slips printed out then?
An error occurred while saving the commentJerry Marks Revival Parts commented
Our business case depends on which issue exactly you're referring to, but I'll try an explain our work flow to try and clear things up a little bit
Basically, customers place orders, they come in, and are printer automatically overnight,
Our warehouse guys come in, grab a stack off of the printer, and get to work picking and shipping the packages, which saves time as they don't need to print pick lists on a case by case basis
Ship station currently has no feature to print a specific form, or customize a packing slip when it comes in, so i was unable to accomplish this with ship station.
The other thing is, even once we made a custom solution to generate slips for these packages when they come in, we found out that we don't even have access to an API to print items via Shipstation Connect
I know shipstation has an INTERNAL API for Shipstation Connect, but it's not exposed, so we can't even use the same software that we're paying to use that's already installed on all of our computers for printing to automatically queue a print job
Which means, we've changed our process from being all inside shipstation, to something that relies on 2 other separate processes, which are on two different systems, to something that could probably be implemented quite easily on you guy's end, or even if you weren't willing to make the entire process, if you could just expose the internal shipstation connect API we could reduce the reliance on other programs and servers and it would make our stuff so much easier, of course there are alternatives like google cloud print, but why would we have two separate systems to print things remotely when you guys already have all the framework and functionality built out, but simply have chosen to not expose it?