Export from Shopify Shapediver plugin when purchasing

Grasshopper ShapeDiver
,
1

Hello,

Hi,
I’m using ShapeDiver together with the Shopify plugin, and I’d like to automate the following workflow:

For each purchase of a specific product, I would like to automatically receive the corresponding Rhino (.3dm) file, reflecting the final parameter values chosen by the customer in the ShapeDiver configurator.

Could you please clarify:

  1. Whether it’s possible to automatically export and send a Rhino file per order

  2. How parameter values from the Shopify order are passed back to ShapeDiver

  3. Whether the Rhino file export can be triggered on purchase (or order confirmation)

  4. If the file can be attached to the order, sent by email, or accessed via a download link

  5. Any limitations regarding file structure, layers, or geometry types in the exported Rhino file

Additionally, I’d like to understand best practices for:

  • Versioning or naming exported files per order

  • Handling updates if a customer modifies parameters after purchase

  • Integrating this workflow into a production or fabrication pipeline

Thanks in advance for your guidance.

2
  1. For each order in your shop, you have access to the corresponding model state id, which allows you to open the configuration in App Builder again. Additionally, you can include a context parameter when opening this configuration to show a different interface. Our recommendation is to sue this workflow so you can access to a version of the App where you can trigger file exports manually, either directly or using an Email Export to send those files to yourself or your clients. You can read more about this workflow and the context parameter in our documentation. If you would still like to trigger an export or an email automatically for each order, we recommend using the free Flow plugin and setting up an automation there.
  2. I do not understand this question, please explain what your goal is.
  3. See my answer to point 1 about this question.
  4. Same as above.
  5. There are no limitations if you are exporting 3dm files, you can define layers using the attributes system for example. Read more about file exports here.
  • Versioning or naming exported files per order

If your goal is to include the order ID in exported files, this is currently not possible. However, you can include the model state ID which is uniquely associated with each order.

  • Handling updates if a customer modifies parameters after purchase

Please give more details about what you are trying to achieve in this case. What would it mean for a user to modify parameters after a purchase? Is this question about a user placing a new order and starting from their previous purchase? In that case, I refer you to the documentation above: you could include buttons to Save the configuration in your App, so that users can create a state id and save it for future usage. You could also use the Flow plugin here as well, and send emails after purchase including a link to the configuration so that users can open it again and further configure the product.

  • Integrating this workflow into a production or fabrication pipeline

It is difficult to give you help without context, but I would assume that, once again, the Flow plugin is what you could use to trigger exports and send them to another environment in your production pipeline after a purchase is done.

1 Like