Skip to main content

2401 Ideas

Request shipstation API feature development(ETSY)New

I am an Etsy seller and I encountered a problem when using the Shipstation API. The process is as follows:Please see below: I send a Post request:url = "ssapi.shipstation.com/orders/markasshipped"Parameters:payload = {"orderId": 491876446,"carrierCode": "sf-express","shipDate": "2024-11-12","trackingNumber":"9300120111412091388309 ","notifyCustomer": false,"notifySalesChannel": true}Description: The order number is: 3476386026, (orderId: 491876446, orderNumber: 3476386026) is an order from the etsy channel.notifySalesChannel is true, requiring the shipstation to notify etsy of the shipment, and the shipstation requests createReceiptShipment in the etsy api. The description of createReceiptShipment is as follows: Shipstation API request results:{"orderId":491876446,"orderNumber":"3476386026"}The shipstation UI shows:Etsy backend order display:From the above description, when Shipstation notifies Etsy to ship, when requesting Etsy API (createReceiptShipment), the value of field carrier_name is other, not sf-express. When I request Shipstation API (Mark an Order as Shipped), the value of field carrierCode is sf-express, maybe Shipstation has filtered it. I would like to make a request to you. Can I pass the same value of field carrierCode to field carrier_name of Etsy API (createReceiptShipment) when requesting Shipstation API (Mark an Order as Shipped), instead of other? Are you willing to develop this requirement?My functional requirements are as follows: When requesting the Shipstation API (Mark an Order as Shipped), I hope that Shipstation will pass the same value of the field carrierCode to the field carrier_name of the Etsy API (createReceiptShipment). For example (assuming that this order is on the etsy platform): When I request the Shipstation API (Mark an Order as Shipped), the value of the field carrierCode is "sf-express". When Shipstation notifies etsy to ship, I hope to pass "sf-express" to the field carrier_name of the Etsy API (createReceiptShipment). Because currently, if the value of carrierCode does not exist in the ShipStation UI, ShipStation will pass "other" to the field carrier_name of the Etsy API (createReceiptShipment). Hope to get your help, our business really needs this function.    

Merge ShipStation Connect device recognition to main platformNew

Hello, trying to maximize efficiency in our warehouse and reduce steps and clicks, and we just moved to this shiny new shipping platform to help us. It's been working pretty great until we reach the point of selecting scales and printers, and ShipStation Connect is baffling us. I would love if it was just integrated into the base platform - make the whole software an app if you got to.On other shipping platforms, and most applications, it detects the local scale and printer on our device and autofills. No need to select from dozens of "shared" devices (if you unshare the device, it also disappears from your local list?). In ShipStation, you cannot see any of your devices without opening and logging into a separate app. Please merge these functions; work smarter not harder!I understand the device sharing might be super helpful to other organizations, but that should be an add-on feature, not the default. The result is dozens of duplicates of the same computer, same devices, just under different logins. We have dozens of hourly and seasonal workers visiting individual shipping stations, and setting up their ShipStation, ShipStation Connect, and configuring their devices every time is MADNESS. We cannot expect this level of tech savviness from this type of job. As an IT Admin I have to configure the same scales for "high capacity mode" DAILY because someone new is logging into a station they haven't used before.Unless I am missing some far easier way to mitigate these problems, this is how it was introduced to us. Please help!