ShipStation's new integration with Miva Connect supports new order status mappings and importing more order details. The Miva Connect integration will replace our existing Miva integration.
To use the new integration, you will set your old Miva store to inactive and create a new store connection with Miva Connect. This guide will help you plan your migration process so you don't miss any orders or ship orders more than once.
Scope of Support
While ShipStation Support can assist you with deactivating your old Miva store and connecting your new store, we recommend contacting Miva Support with questions about Miva Connect or the migration.
Additionally, installing the Miva ShipStation configuration file and creating a new API token in Miva are beyond the ShipStation scope of support.
See Miva's ShipStation integration guide for more details.
Miva Connect supports the following features that were not supported by our previous Miva integration:
-
Miva orders not yet paid or not paid in full can now import into ShipStation's Awaiting Payment status.
-
Importing discounts, identifying gift orders, and importing gift messages are now supported.
-
For Miva merchants who sell kits (where one SKU contains multiple product SKUs that make up the kit), the singular kit SKU will import with the order into ShipStation. The product SKUs will be listed in the order's item details in ShipStation.
-
Miva Order Custom Fields can be mapped to ShipStation shipment options during the store connection process. These fields are used in Miva to collect things like order notes during checkout, and they can be mapped to the following custom fields in ShipStation:
-
Additional Handling/Special Instructions
-
Deliver by Date
-
Do Not Prepay Postage
-
Gift Message
-
Has Alcohol
-
Hold Until Date
-
Insured Value
-
Non-Machinable
-
Package Type
-
Premium Program Name
-
Ready To Ship Date
-
Requested Warehouse
-
Saturday Delivery
-
Ship By Date
-
Show Postage
See our Miva Connect integration guide for steps to connect your Miva store to ShipStation.
-
Before starting your migration, we recommend preparing your ShipStation account to avoid disrupting your normal flow:
-
Any open orders in your Miva store will import into the new Miva Connect store in ShipStation, once you have completed the migration.
If any of these orders previously imported into your old store and you made changes to them in ShipStation, you will need to make those changes again. To avoid this scenario, we recommend migrating to the new store after you have closed all shipments for the day and shipment notifications have been sent.
-
The store settings in your new Miva Connect store will be set at their default settings. Take note of the store settings in your old store first, like Branding, Email and Packing Slip Templates, the Branded Returns Portal, etc., so you can update your new store connection to match.
-
If you are using ShipStation webhooks, please follow these instructions to update the webhooks to the correct new store. You may also need to unsubscribe from the webhooks and re-subscribe with the correct Store ID.
-
If you are using ShipStation’s Open API, please note you will need to update the Store ID in the calls you are making to the new store ID number post-migration.
To migrate to Miva Connect, you will first set your old Miva store connection to inactive in ShipStation.
Next, create a new store connection for Miva Connect:
-
Download the Miva Shipstation configuration file from the Miva app store at apps.miva.com/shipstation.html.
-
Go to your Miva Settings > Data Management > Import Data and Settings in XML Provisioning Format.
-
Upload the ShipStation configuration file to your Miva store by clicking Choose File and selecting shipstation_setup.xml from your file explorer.
When the file has been successfully uploaded, you will see the message: "Import of shipstation_setup.xml complete"
-
Go to your Miva Settings > Users Management > API Tokens, and click Add API Token.
-
Create a new API token for use with ShipStation, then click Save.
Take note of the following fields, as you will need to enter these in ShipStation later:
-
Endpoint URL
-
Access Token
-
Signature (Select the option Require Signature with Key)
-
-
Select your new ShipStation API Token from your list of Users, then click Functions.
-
Select the following eight functions to give permissions for this API token:
-
Module:orderworkflow:OrderList_Acknowledge
-
Module:orderworkflow:QueueOrderList_Load_Query
-
OrderCustomFields_Update
-
OrderItemList_CreateShipment
-
OrderList_Load_Query
-
OrderShipmentList_Update
-
ProductList_Load_Query
-
Store_Load
When you click Add Function, the first column will let you select if the function operates at the domain level or store level. All these functions are store level functions. You will need to select your store.
-
-
Select the Miva Connect tile.
-
Enter your Miva Store Code, JSON API Endpoint (Endpoint URL), JSON API Access Token, JSON API Signature, Order Workflow Queue Code, Currency Code, and Main Image Type Code into the corresponding fields.
-
OPTIONAL: Click Add Item under Order Custom Field Mapping to map your Miva custom fields to one of the available custom field options in ShipStation.
-
Click Connect.
Once your new Miva Connect store is connected to ShipStation, we recommend checking the following settings to help quickly resume normal operations.
-
Automation rules: Make sure that any automation rule criterion that references your old Miva store is set to the new Miva Connect store.
-
Store Settings: Update any store settings that need to be customized for Miva Connect (like Branding, Email Templates or the Branded Returns Portal).
-
You can reactivate your old Miva store connection for reporting purposes. However, you cannot use the old Miva store connection to import new orders. Set the old connection back to inactive after running reports.
Where is my old Miva store?
In Settings > Selling Channels > Store Setup, vheck the box below the list of connected stores to show inactive stores. All your inactive stores will display without a value in the Status column.