Skip to main content

2401 Ideas

Support gift wrap and gift message in BigCommerce on packing slipNew

Bigcommerce has a built-in Gift Wrap solution, and this data is not utilized by Shipstation.A Shipstation customer service tech shared with me the output of the API call that Shipstation gets from BigCommerce when importing a new order. In that JSON, there's a products object (line 83 of my file). Within that object, wrapping_name and wrapping_message parameters (lines 111 and 116) are both sent to Shipstation.This is the gift wrap option (such as "standard", "premium", etc) and gift message (such as "Happy birthday, mom") selected by the customer in the store for that specific product.Having the ability to assign wrapping_name and wrapping_message to a Field Replacement in the Packing Slip Editor and utilize it in the Order Items section of the Packing Slip template would solve many problems. Ideally this would just be part of the [Item Options] field, or it could be a separate field, either way, this is an incredible oversight.Currently there is no ability to map this data into Custom Fields either.I was told this was impossible because Shipstation cannot access wrapping_name and wrapping_message, but according to BigCommerce, this is untrue and the data **is** supplied to Shipstation in the JSON—as confirmed by the file shared by Shipstation's customer service. If Shipstation's processing discards this information, this should be reworked, but there is no technical reason from BigCommerce's side for this not to work.Asking Bigcommerce to come up with a solution is unacceptable because Shipstation **has** the product-level gift wrap data within the order's JSON. It is simply being ignored.

Feature Request: Shopify Integration - DimensionsNew

Shopify natively allows the administrator to set up what dimensions will be used in shipping. However, when using ShipStation integration to receive calculated rates, SS does not take the dimensions data and instead just applies a 1x1x1 to provide Shopify the rates. This returns inaccurate rates in some circumstances where dimensional weight is a factor. The dimensional data is is there on Shopify, but through a conversation in support chat with both Shopify and SS I learned that ShipStation is not currently set up to handle that data. It would be great if that connection could be made. This makes a great deal of difference when talking about Dimension Weight and its impact on 2nd day air / next day air service levels. The band-aid solution is to go into SS settings for the selling channel and set a % modifier to adjust the price that SS sends to Shopify. I personally ran some tests and used data sets to come up with a good % adjustment for my store; this solution was pretty accurate with a slight margin for error. But I find the lack of this feature disappointing. The idea of integrating ShipStation with Shopify and enabling Calculated Rates is to get accurate rates. Which, they are accurate for lots of circumstances... just not all. And a major loss of accuracy is due to 3 simple data points: L, W, H. Seems if this data connection is already setup to pass information back and forth, couldn't those be part of it as well? The goal is to get accurate rates, not sure why they were ever left off.

Combined order numbers in reports bugNew

Here's an example where I have two orders combined. One order has one item and the other two items. I can search for either order number in the Orders tab and find the combined order, which is great.If I use the Order Detail report, Orders raw data report, or even export the data from the Orders tab, I get the order numbers from the second order overwritten by the first in the combined order. The same happens when retrieving the data from the REST API.Here's an example of the same orders from above exported as data that I've loaded into a spreadsheet.Those last two items came from order 7595037 but their order number has been overwritten with 7595032. I consider this a bug because the data is simply incorrect. Those line items did not come from that order number.I understand how ShipStation uses the first order number to represent all when combining orders. Combining is a tricky thing to solve and that compromise gets the job done.However, it doesn't make sense when doing reports of orders or that list line items. These are not shipment reports, they are order reports. As such, the order numbers should be the originals from the orders.My use case is that I export from the raw data reports and match that to data from our other systems for accounting purposes. The way this is handled makes it impossible to match orders that have been combined.We tried to work around the problem by using the REST API to pull data but there doesn't seem to be a way to get at the data there either.Related ideas:Combine Shipment / Don't Combine Orders — This idea from several years ago is marked as completed because the search feature now can find individual order numbers in a combined order. The completion didn't address the customer expectations or ramifications that others expanded upon in the comments.Bug in combined-orders export — This idea is similar to mine but doesn't go into a lot of explanation. I decided to create a new one to offer more detail. This idea is also several months old but still has a status of "new", which may indicate it hasn't been looked at yet.Linking in others who may be interested and want to vote this up or comment:@info703, @jason56, @howard, @baysuperstore, @kristi1, @mirabelweb, @Art95