Monitor ERP + Svea
Everything you need to connect Monitor ERP and Svea: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- 1 data flow
- Connect in about 20 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 10 minutes
Prepare Monitor ERP
- Open the Monitor integration / API setup
- Generate or retrieve the API access key
- Confirm the technical integration user if relevant
- Note the correct company or database context
- Enter the values in Junipeer
- about 10 minutes
Prepare Svea
- Contact Svea to get started
- Get the test credentials
- Store the values securely
- Paste the values into Junipeer
- Repeat for live when you are ready
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 - Orders
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 Monitor ERP (15)
| Setting | What it controls | Key |
|---|---|---|
| API URL | Enter the address of your Monitor API, for example https://host:8001 . | monitor_api_base_url |
| Company Number | Enter the number of the Monitor company to connect to, for example 001.1 . | monitor_company_number |
| Customer Levels | Choose which kinds of Monitor customers are fetched and sent on. | monitor_customer_levels |
| Default Monitor ERP Warehouse | Choose the Monitor warehouse that is treated as the default when stock is fetched from Monitor. | monitor_default_warehouse_id |
| Exclude Orders created before this date | Choose a date. Orders created before this date are not synced. | stdintegration_filter_monitor_erp_order_created_date |
| Find the Monitor Customer By | Decide how Junipeer finds the Monitor customer an order belongs to. | monitor_order_customer_lookup |
| Language Code | Enter the language code used when connecting to Monitor, for example sv . | monitor_language_code |
| Order Row Type | Choose the row type used for order lines in the Monitor order. | monitor_order_row_type |
Show all 15 settings
| Setting | What it controls | Key |
|---|---|---|
| Order Type | Optional. Choose the Monitor order type given to customer orders created in Monitor. | monitor_order_type_id |
| Password | Enter the password for the Monitor user above. | monitor_password |
| Project | Optional. Choose the Monitor project used on customer orders created in Monitor. | monitor_project_id |
| Sales Price List | Choose the Monitor price list that article prices are taken from. | monitor_article_price_list_id |
| Stock Order | Decide whether customer orders are created as stock orders in Monitor. | monitor_is_stock_order |
| Username | Enter the Monitor username Junipeer should log in with. | monitor_username |
| Warehouse | Optional. Choose the Monitor warehouse used on customer orders created in Monitor. | monitor_warehouse_id |
Settings for Svea (14)
| Setting | What it controls | Key |
|---|---|---|
| Defer Svea delivery | Decide whether InStore orders should be delivered automatically in Svea Payment Admin when the customer completes the order. | svea_order_deferred_delivery |
| Exclude Orders created before this date | Choose a date. Svea orders created before this date are not synced. | stdintegration_filter_svea_order_created_date |
| How do you want to identify your Svea orders? | Choose which Fortnox orders should be handled as Svea orders. | svea_order_identification_mode |
| Identify Svea Orders by Payment Method | Choose the terms of payment (betalningsvillkor) on the Fortnox order that tells Junipeer the order is a Svea order. | svea_payment_method_identifier |
| Instore API password | Enter your Svea InStore API password . | svea_instore_pass |
| Instore API username | Enter your Svea InStore API username . | svea_instore_user |
| SKU for empty article number | Some accounting and ERP systems don't accept an order row without an article number (SKU). | svea_empty_article_number |
| Shipping SKU | Enter the article number (SKU) that your Svea orders use for the shipping fee , so Junipeer knows which order row is the shipping fee. | svea_shipping_sku |
Show all 14 settings
| Setting | What it controls | Key |
|---|---|---|
| Svea Order Reference Manipulation | Clean up the order reference (merchant reference number) from Svea before Junipeer uses it. | svea_order_reference_manipulator |
| Svea merchant name | Enter the merchant name that is shown to the customer on Svea Checkout for InStore orders. | svea_order_merchant_name |
| Svea minutes until link expires | Enter how many minutes the Svea Checkout link for an InStore order stays valid. | svea_order_minutes_expires |
| Svea terms uri | Enter the web address of your terms and conditions page . | svea_order_terms_uri |
| Test Mode | Decide whether Junipeer talks to Svea in test mode . | svea_test_mode |
| Use Checkout ID as payout payment reference (Payment ID) | Choose which Svea reference is used as the Payment ID on payout transactions. | svea_use_checkout_id_as_payout_payment_id |
Did this page help you?