Share your challenges, collaborate with others, and let us hear you!

← Product Feedback & Fresh Ideas

Combine/Split order using ShipStation's API

Combine/Split order using ShipStation's API

78 votes
Vote
Sign in Sign in with ShipStation
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Omerben7 shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
under review  ·  AdminShipStation (Product Owner, ShipStation) responded  · 

Thanks for your great idea! We’ll keep this in mind but would like to see more interest from other users before we pursue this new feature. If you know any other users that are interested please send them here!

21 comments

Sign in Sign in with ShipStation
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Dakota Bartell D.B.Collectibles commented  ·   ·  Flag as inappropriate

    @Shipstation

    There have ideas with less votes that have been started with less votes than this. Please get this going. My business is growing 2-3x year over year and it's not a scalable solution to just have an employee of my mine combine orders all day.

  • Robert Jones TOTM Limited commented  ·   ·  Flag as inappropriate

    @Austin Johnson Also interested in seeing what you have done. I made something similar for a different shipping provider (Veeqo).

  • Austin Johnson One Metric LLC commented  ·   ·  Flag as inappropriate

    @colshipping Yes, I wrote my own script to do this using the ShipStation API. I will put the Javascript on GitHub if I get a chance.

    If you use the Create/Update Order API Endpoint ( https://www.shipstation.com/docs/api/orders/create-update-order/ ), you can use the main order ID in the parentId field of the new order, and create a new split off child order.

    However, ShipStation's parent/child order relationship has a couple challenges in that ShipStation still views both order "legs" as the same order. If you change certain fields like order notes in one "leg" of the order, you see these same changes in the other "leg". For my application, this is an undesired behavior.

    Thus, when I refactor some of these order splitting needs, I will most likely just create totally separate orders and not use the parent/child relationship functionality.

    I should also add that I used the Product Categories to create the "rules" that define order splitting. Basically, all products that share a category are grouped onto their own order. You could use another field from the products table, or use tags.

    Writing the code to actually remove products from the main order and put them on a child order was a bit of a challenge when I did it originally a year ago. I will likely redo this in the coming weeks.

  • colshipping commented  ·   ·  Flag as inappropriate

    I've noticed a few individuals are mentioning writing their own code for this or trying to find other alternatives, has anyone found a method that works reliably yet?

  • JSchmidt commented  ·   ·  Flag as inappropriate

    This is a big requirement now that we are automating many of our processes and without this feature, we'll be looking for another solution.

  • Jonathan Magee My Adventure to Fit commented  ·   ·  Flag as inappropriate

    I would like to see this occur - this is especially useful when doing something for preorder, and needing to split a portion of the order from the pre order portion. Very useful from a store owner's perspective and would give more control of orders without added admin

  • tdishman commented  ·   ·  Flag as inappropriate

    We could really use this feature. How many responses would it take to get this implemented?

  • CowboyBob commented  ·   ·  Flag as inappropriate

    +1 We have many weekly recurring orders that need to be combined or split. We'd love to automate this task.

  • ProductJump commented  ·   ·  Flag as inappropriate

    Absolutely. For repeat orders that happen before shipping takes place. Need this NOW.

← Previous 1

Product Feedback & Fresh Ideas: Order Management

Categories

Feedback and Knowledge Base

(thinking…)