We've recently released a feature that allows you to add multiple transactions to EZ Importer. Now when you import your transaction data you can add up to 5 transactions with each import.

To add multiple transactions go to the data mapper and click the transactions tab. At the bottom of the tab you'll see a button that says "Add Transaction Row".

When you click this button you'll be able to map another set of transaction columns. After you add …

EZ Exporter just got easier to use!

We're really excited to announce that our app now has support for built-in templates, making it super-easy to get started with our app! Just select a template and a pair of Export Profile and Data Settings will be created from that template, with most (if not all) of the things you'll most likely need already configured for you. You can then modify them at any time to customize them further.

It's also a …

Shopify recently updated their Order API and it now provides more information about the discounts applied to the order on the line item level.

There's actually a field called total_discount under the line items data for a long time, but it's a bit misleading as it only applied to line item discounts when using the Shopify POS and not for web orders. With this API update, we can now pull the discount amount and discount codes that were applied to …

Grouping and aggregating data is now available in EZ Exporter!

This feature allows you to generate all kinds of summary reports to get more insights from your Shopify data. Below is just small list of the different types of reports you can now create thanks to this new feature:

• Sales by Hour, Week, Day, Month, Year, Day of Week (which days have the highest sales, for example)
• Sales by Customer, Customer Lifetime Value (CLTV), Average Order Value
• Sales by …

We've recently pushed an update to EZ Exporter to include two additional functions that can be used in the Calculated Fields: get_attribute_value() and get_total().

A couple use cases came up while talking to our customers and we thought the best way to handle them was to add these functions.

get_attribute_value(data, attribute_name, results_separator=",")

Retrieve an attribute's value from a list of attributes.

The data may look something like this:

"discount_codes": [
  {
    "code": "SPRING30",
    "amount": "30.00",
    "type": "fixed_amount"
  }
]

Examples: …