Skip to content
Often SoftwareOften Software

Product options and customisation apps

Exportify works with any product options, file upload or cart-field app because their values are saved on the order as line item properties or order attributes, and both export as columns once detected.

Exportify works with any app or theme customisation that saves what the customer chose onto the order, because Shopify stores those choices in one of two standard places and Exportify exports both:

  • Line item properties: options attached to a product in the order (engraving text, a colour or size outside variants, an uploaded file, a name and number on a jersey). Product options apps such as Infinite Options, file upload apps such as Uploadery, and themes with their own option fields all write here.
  • Order custom attributes (note or cart attributes): choices attached to the order as a whole (a delivery date, a gift message, a PO number, how the customer heard about you). Cart-page apps and theme cart fields write here.

There is nothing app-specific to configure in Exportify. If the value is on the order in the Shopify admin, Exportify can export it.

  1. Place a test order with the options filled in, so the names exist on at least one order.

  2. Refresh detected fields. In Exportify’s Settings, click Refresh Detected Custom Fields. The names appear under Detected Order Custom Attributes and Detected Line Item Custom Attributes.

  3. Add them to your template, or export with the pre-built Standard Export + Detected Custom Fields template, which includes every detected field.

See Export line item properties and custom attributes for the full walkthrough.

  • Names beginning with an underscore are hidden by Shopify in its own export and Exportify treats them the same way. Some apps store internal keys that way (for example _uploadery_1 beside the visible upload link); the visible ones are what you want.
  • If an app changes a property name in an update, refresh the detected fields and add the new name.
  • Column names in your file do not have to match the property names; rename headers in the template builder.