Visma.net + Dotdigital
Everything you need to connect Visma.net 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 8 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 3 minutes
Prepare Visma.net
- Open the Visma.net connector in Junipeer
- Click Connect
- Sign in with the correct Visma account
- Approve the requested access
- Return to Junipeer and verify the connection
- 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.net (43)
| Setting | What it controls | Key |
|---|---|---|
| Add Shipment Tracking in Visma | Decide whether tracking information should be added to the shipment in Visma.net. | vismanet_add_shipment_tracking |
| Add shipping fee as an Order Line | Decide whether the shipping fee should be added as an order line in Visma.net. | vismanet_add_shipping_on_order_rows |
| Attribute to use for CustomerOrder | Choose which order attribute from your webshop should be written to the CustomerOrder field on refunds in Visma.net. | vismanet_refund_customer_order_attribute |
| Choose Warehouse (For shipments) | Choose which Visma.net warehouse shipments must be in to be synced from Visma.net. | vismanet_default_warehouse_id |
| Confirm Shipment in Visma | Decide whether the shipment in Visma.net should be confirmed when shipment information is available from the other system. | vismanet_confirm_shipment |
| Countries to Skip | Choose countries whose orders should not be sent to Visma.net. | vismanet_ignore_order_countries |
| Create Order Shipment | Decide whether a shipment should be created in Visma.net directly after the order has been created. | vismanet_order_create_shipment |
| Default (Shipping fee) Article number in Visma | Enter the article number in Visma.net to use for the shipping fee order line. | vismanet_default_shipment_article_no |
Show all 43 settings
| Setting | What it controls | Key |
|---|---|---|
| Default Cash Account for Orders | Choose the cash account that orders get in Visma.net when no specific cash account is found. | vismanet_default_cash_account |
| Default Order Payment Method | Choose the payment method that orders get in Visma.net when no specific payment method is found. | vismanet_default_payment_method |
| Default Order Payment Terms | Choose the payment terms that orders get in Visma.net when no specific payment terms are found. | vismanet_default_payment_terms |
| Default Ship Via code | Choose the Ship Via code (carrier) that orders get in Visma.net when no other shipping method is found. | vismanet_default_ship_via_code |
| Default Warehouse for Order Items | Choose the Visma.net warehouse that order rows get by default. | vismanet_default_order_item_warehouse |
| Exclude Price in order rows when zero | Decide what happens with order rows that have the price 0 when orders are sent to Visma.net. | vismanet_exclude_order_rows_price_when_zero |
| Fee Write Off Reason Code | Enter the write-off reason code in Visma.net to use for fees on customer payments. | vismanet_payout_fee_write_off_reason_code |
| Include fee in amount | Decide whether payout fees should be written off separately or kept in the payment amount. | vismanet_payout_merge_amount_and_fee |
| Load Customer Data | Decide whether extra information should be loaded from the customer that the shipment belongs to. | vismanet_shipments_load_customer_attributes |
| Map (allocations) Warehouses for Order Items | Choose which Visma.net warehouse an order row gets, depending on which warehouse the item was allocated from in your webshop. | vismanet_map_order_item_warehouses |
| Map B2B Customers class, by country | Choose which customer class B2B (business) customers get in Visma.net, depending on their country. | vismanet_map_b2b_customer_class |
| Map B2C Customers class, by country | Choose which customer class B2C (consumer) customers get in Visma.net, depending on their country. | vismanet_map_b2c_customer_class |
| Map Cash Account | Choose which cash account an order gets in Visma.net, depending on the payment method used in your webshop. | vismanet_map_cash_account |
| Map Order References | Choose which order reference from your webshop is written to which reference field on the order in Visma.net. | vismanet_map_order_nr_fields |
| Map Payment Method | Connect the payment methods in your webshop with the payment methods in Visma.net. | vismanet_map_payment_method |
| Map Payment Terms | Choose which payment terms an order gets in Visma.net, depending on the payment method used in your webshop. | vismanet_map_payment_terms |
| Map Shipping methods | Connect the shipping methods in your webshop with the carriers (Ship Via) in Visma.net. | vismanet_map_shipping_methods |
| Match shipping methods by name | Decide whether shipping methods should be matched by their names. | vismanet_match_shipping_methods_by_name |
| Omit Currency | Decide whether the currency should be left out for orders of this order type. | omit_currency |
| Omit Original Order ID | Decide whether the original order ID should be left out for orders of this order type. | omit_original_order_id |
| Omit Payment Reference | Decide whether the payment reference should be left out for orders of this order type. | omit_payment_reference |
| Order Type | Choose the order type to use when the conditions of this entry match. | order_type |
| Order Type Mapping | Decide which order type an order gets in Visma.net, depending on the order data from your webshop. | vismanet_map_order_type |
| Order Type Settings | Add extra settings that apply only to orders of a specific order type. | vismanet_order_type_settings |
| Order attribute for description | Choose which order attribute from your webshop should be used as the order description in Visma.net. | vismanet_order_attribute_to_description |
| Override Customer Details in Visma | An order carries the customer's details, such as name and address. | vismanet_order_override_customer_data |
| Override Order Number Series | Decide whether the order number from the integration may override the order number series in Visma.net. | vismanet_override_order_number_series |
| Sales Order Type for Refund orders | Choose the order type that refunds get when they are created in Visma.net. | vismanet_default_return_order_type |
| Shipping fee map | Choose which Visma.net article number the shipping fee line gets, depending on the shipping method used in your webshop. | vismanet_shipment_article_no |
| Skip Companies when syncing Customers | Decide whether companies should be left out when customers are exported from Visma.net to your webshop. | vismanet_exclude_companies_from_customers |
| Use Payment Ref Field | Decide whether the payment reference number should be set in the Payment Ref field when an order is created in Visma.net. | vismanet_order_set_payment_ref_field |
| Use Sales Orders V3 | Decide whether orders should be created in Visma.net using the latest version of Visma.net's sales order interface (V3). | vismanet_use_sales_order_v3 |
| VAT included in order rows | Decide whether prices on order rows are sent to Visma.net including or excluding VAT. | vismanet_vat_included_order_rows_price |
| Visma Sales Order Type | Choose the order type that orders get when they are created in Visma.net. | vismanet_default_order_type |
| Visma Sales Person | Choose a sales person to add to the orders created in Visma.net. | vismanet_default_order_salesperson |
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 |
4. Troubleshooting
Choose what you see. Each case shows the cause and the solution.
MediumFor error codes and patterns specific to Visma.net integrations, see the Error C
Cause
For error codes and patterns specific to Visma.net integrations, see the Error Codes guide. Common Visma.net-related issues include:
Solution
Refer to the platform setup guide for resolution steps.
5. More guides
Did this page help you?