Visma Spiris + Dotdigital
Everything you need to connect Visma Spiris and Dotdigital: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- 1 data flow
- Connect in about 10 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 5 minutes
Prepare Visma Spiris
- Click Connect to Visma eEkonomi
- Log in to Visma
- Choose the company
- Allow access
- about 5 minutes
Prepare Dotdigital
- Open API users in Dotdigital
- Create a new API user
- Leave the generated username unchanged
- Set the password and enable the user
- Save and copy the credentials
- Paste the credentials into Junipeer
Connect and test
Enter the details in Junipeer, switch on the flows you need and test with one order before you go live.
Getting started with Junipeer
2. How the data flows
What Junipeer can move between the two systems. The arrow shows which way the data goes.
Junipeer - Customers
3. Settings
The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.
You don't need to read them all
In Junipeer every setting has a ? that opens the same explanation next to the form, right when you need it. With the Junipeer MCP your AI assistant can also propose the settings from your own data.
How the Junipeer MCP worksSettings for Visma Spiris (15)
| Setting | What it controls | Key |
|---|---|---|
| Add shipping fee as an Order Line | Decide whether the shipping fee should be added as an order line in Visma. | visma_add_shipping_on_order_rows |
| Article Label/Group to sync | Choose which products in Visma are synced to your webshop. | visma_article_label_to_sync |
| Create missing Products | All products on an order must exist in Visma before the order can be created. | visma_order_create_missing_products |
| Default (Shipping fee) Article number in Visma | Enter the Visma article number to use for the shipping fee line on orders. | visma_default_shipment_article_no |
| Default Currency on Visma products | Enter the currency code used on your products in Visma, for example SEK , EUR or USD . | visma_default_currency |
| Default Delivery Method | Choose the delivery method to use in Visma when no mapped delivery method is found. | visma_default_delivery_method_code |
| Default Terms of Payment in Visma | Choose the terms of payment that Junipeer sets on customers in Visma. | visma_default_payment_terms |
| Default Unit | Choose the unit that products get when Junipeer creates missing products in Visma. | visma_default_unit |
Show all 15 settings
| Setting | What it controls | Key |
|---|---|---|
| Include non Stock Items from Visma | Decide whether articles marked as non stock items in Visma should be included when stock and quantities are synced to your webshop. | visma_include_non_stock_items |
| Map Shipping methods | Connect the shipping methods in your webshop with the delivery methods in Visma. | visma_map_shipping_methods |
| Map Vat rates | Connect VAT rates with the VAT rates in Visma. | visma_map_vat |
| Match shipping methods by name | Decide whether shipping methods should be matched by name. | visma_match_shipping_methods_by_name |
| Shipping fee map | Use a different Visma article number for the shipping fee depending on the shipping method. | visma_shipment_article_no |
| Update Visma Customers | Decide whether customers that already exist in Visma should be updated. | visma_update_customers |
| Update customer information in Visma | Decide whether the customer in Visma should be updated each time one of their orders is sent to Visma. | visma_update_customer_when_order_is_synced |
Settings for Dotdigital (13)
| Setting | What it controls | Key |
|---|---|---|
| Consent Attribute Fallback | Choose what happens when the customer attribute doesn't contain consent information . | dotdigital_consent_from_attribute_fallback |
| Consent Attribute Field | Enter the name of the customer attribute that holds the consent text. | dotdigital_consent_from_attribute_field |
| Consent Text | Enter the consent text that is attached to a contact when it is created or updated in Dotdigital. | dotdigital_consent_text |
| Consent URL | Enter the web address (URL) where the customer gave their consent. | dotdigital_consent_url |
| Consent from Customer Attribute | Read the consent text from a customer attribute instead of using the fixed Consent Text . | dotdigital_consent_from_attribute_enabled |
| Contact Identifier | Choose how contacts are identified in Dotdigital. | dotdigital_contact_identifier |
| Default Contact List | Choose a Dotdigital list that contacts are added to by default. | dotdigital_default_list |
| List Attribute Fallback | Choose what happens when the customer attribute doesn't contain a list ID . | dotdigital_list_from_attribute_fallback |
Show all 13 settings
| Setting | What it controls | Key |
|---|---|---|
| List Attribute Field | Enter the name of the customer attribute that holds the Dotdigital list ID(s). | dotdigital_list_from_attribute_field |
| List from Customer Attribute | Read Dotdigital list IDs from a customer attribute , instead of (or in addition to) the list settings. | dotdigital_list_from_attribute_enabled |
| Map Country to Contact List | Add contacts to a specific Dotdigital list based on their billing country . | dotdigital_list_by_country |
| Map Customer Attributes to Data Fields (Store) | Write customer attributes to Dotdigital data fields when contacts are saved. | dotdigital_map_attributes_store |
| Map Customer Fields to Data Fields (Store) | Choose which customer fields are written to Dotdigital data fields when contacts are saved. | dotdigital_map_data_fields_store |
Did this page help you?