With the launch of the all-new OrderMetrics, we have removed all of our shipping integrations that were previously available in the legacy OrderMetrics. These include:

  • Shippo

  • Shipwire

  • ShipStation

  • ShippingEasy

  • AliExpress

  • Shopify Label Sync

Why were the shipping integrations removed?

The shipping integrations in the legacy OrderMetrics were designed to fetch shipping data at the order level. This implementation, paired with unreliable API documentation from the shipping providers, was adding strain on our infrastructure; which resulted in a poor experience for users.

We chose to reduce complexity for the all-new OrderMetrics by removing shipping integrations and allowing users to manually add their overall shipping cost for a given date. However this is not the final implementation. We plan on rebuilding shipping integrations for the all-new OrderMetrics. Building these from scratch will ensure that the connections are reliable, consistent with data delivery, and always up-to-date.

We are excited to hear what shipping integrations you would add to the all-new OrderMetrics. Head over to our roadmap to submit your idea and add your vote!

How do I go about adding shipping costs in the all-new OrderMetrics?

In the all-new OrderMetrics, shipping costs are managed under “Shipping Costs”. This allows users the flexibility to enter their exact shipping expenses for any type of courier or delivery provider. While it is suggested users enter their expenses on a frequent basis, it can be done monthly as well, should it be easier to enter a total amount from a statement/invoice.

Shifting from shipping costs per order to an aggregate value removes potential error in linking expenses to each order. More importantly, decisions made on shipping costs and their effect on financial performance, are typically done on an average order basis (not on an order-by-order basis) to help you make sure you are marking up your products with enough margin - which is what we have done! Displaying your shipping total and average order metrics.

To Add a Shipping Cost, click on "Add Cost".

Please note that shipping costs are not attributed to an individual order. We suggest adding your total shipping cost each day. Every time you receive a shipping invoice, please add it to keep on top of these expenses. If you'd prefer to update these monthly, no problem! Simply add your total shipping cost for the month and OrderMetrics will automatically take care of applying that to that month's metrics.

Note: In the all-new OrderMetrics, newly created shipping costs are automatically split across each day of the month. For example, if you create a shipping cost of $1,000 on Jan 17, we will split this $1,000 across each of the 31 days in January. So your shipping cost for Jan 17 will be $32.25, not $1,000.

Also, new shipping costs you create will be adjusted in your metrics at the next daily sync. For example, if you create a shipping cost at 5 pm. local time, it will be factored into your metrics at 12:00 am. local time next day (when the daily sync occurs).

But what happens to all the shipping data I had in the legacy OrderMetrics?

If you had shipping data in the legacy OrderMetrics, we will bring it over to the all-new OrderMetrics as an aggregate for each day. Just like the new shipping costs you may create in the all-new OrderMetrics, the historical shipping costs from the legacy OrderMetrics will not be attributed at the order level. Instead, when you migrate, we take the daily shipping costs total from the legacy OrderMetrics and create a new shipping cost in the all-new OrderMetrics for each date.

This data will show up under Data > Shipping Costs, automatically sorted by most recent date. See example below.

Please note that we only migrate shipping data from the legacy OrderMetrics up until the date you migrate. So if you migrated on Feb 25, we will import the legacy OrderMetrics shipping costs up until Feb 25. Moving forward, you would need to manually add shipping costs in the all-new OrderMetrics as described above.

Did this answer your question?