Flxpoint Help Center
All DocsContact support

Miva as a Channel

July 20, 2026

Summary

Miva connects as a channel supporting Link Listings, Sync Listings, Publish Listings, Get Orders, and Sync Orders. Setup is credential-heavy (Domain, Folder Structure, API Token, Signature Key, Store ID), and the API token must be created with a required timestamp and a specific set of enabled functions or the integration will not have permission to run.

Link Listings
Links existing Miva products to Flxpoint using the product_type custom field.
Sync Listings
Updates price and quantity on your linked Miva products.
Publish Listings
Publishes new products to Miva, including images via FTP.
Get Orders
Imports new orders placed on your Miva store into Flxpoint.
Sync Orders
Sends shipment tracking to Miva and updates fulfillment status.

Add a Miva channel, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter your Domain, Folder Structure, API Token, Signature Key, and Store ID, then Test ConnectionSave Connection.

DomainRequired
Your Miva store's domain.
Folder StructureRequired
The Miva store's folder structure path.
API TokenRequired
Your Miva API Token, created with Require Timestamp and the required functions enabled.
Signature KeyRequired
Your Miva API Signature Key.
Store IDRequired
Your Miva Store ID.
The API Token must have Require Timestamp enabled (120 seconds recommended) and the required functions added — for example Provision_Store, OrderList_Load_Query, ProductList_Load_Query — or the integration will not have permission to run. For extended setup guidance, contact support@flxpoint.com.

API token needs timestamp and functions

When creating the Miva API token, enable Require Timestamp (120 seconds recommended) and add the required functions (for example Provision_Store, OrderList_Load_Query, ProductList_Load_Query). Missing functions or timestamp leave the integration without permission to run.

product_type custom field for linking

To link and update existing Miva products, create the product_type custom field and set each product as parent, variant, or simple. Miva has no native parent/variant structure; if you do not need one, set all products to simple.

Image FTP subfolder

Images publish via FTP under /htdocs/mm5/graphics. If you did not create the is-images subfolder, set Image FTP Subfolder to graphics, not is-images.

Publish field limitations

UPC, MPN, product dimensions (Height, Length, Width), and Brand/Manufacturer are not available on Miva and will not publish.


FieldMaps To — Notes
product_type (custom field)Simple / Variant / Parent. Required. Miva has no native parent/variant structure — this custom field tells Flxpoint how to treat each product when linking.
Product CodeListing Variant → External Listing ID. Miva's product code, matched to link the item.
SKUListing Variant → SKU. Required. Matched against your Flxpoint variant SKU.
FieldMaps To — Notes
External Listing IDMiva Product Code. Required. Identifies which Miva product/variant receives the update.
FieldMaps To — Notes
External Listing IDNo mapping is available.
product_type (custom field)Simple / Variant / Parent. Required. Set per product on publish so Miva structures it correctly.
FieldMaps To — Notes
Miva Order IDOrder Invoice → Invoice Number. Miva's internal order ID, used as the invoice number in Flxpoint.
Order SubtotalNo mapping is available.
FieldMaps To — Notes
Order Item → SKUMiva Line Item. Required. Matches the Flxpoint order item to its corresponding Miva order line by SKU.
Shipment → Tracking / Ship DateMiva Shipment. Sent to Miva to mark the order line shipped.

Listings will not publish if your Time Stamp is not set
Enable Require Timestamp (120 seconds recommended) on the Miva API token, and confirm the required API functions are added under User > API Token > Add Functions.
Product shows as Broken Link after being deleted on the store
If a product is deleted on Miva without using Flxpoint, it stays Linked until the next sync, then becomes a Broken Link. Unlink and relink the item in your listings to fix it.

Why will my listings not publish to Miva?
The usual causes are the API token: listings will not publish if the Time Stamp is not set on the token, and the integration cannot run if the required API functions were not enabled when the token was created. Recreate the token with Require Timestamp on and the full function list added.
© 2026 Flxpoint. All rights reserved.