Monitor ERP + Qliro
Everything you need to connect Monitor ERP and Qliro: 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 Qliro
- Contact Qliro for credentials
- Verify environment and account
- Store MerchantApiKey and MerchantApiSecret securely
- Paste the values 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 - 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 Qliro (19)
| Setting | What it controls | Key |
|---|---|---|
| Always Capture Fee | Decide whether the fee on a Qliro order should always be captured (shipped). | qliro_capture_always_manage_fee |
| Always Capture Shipping Fee | Decide whether the shipping fee on a Qliro order should always be captured (shipped). | qliro_capture_always_manage_shipping |
| Always Credit Fee | Decide whether the fee in a Qliro order should always be credited when a refund is made in Qliro. | qliro_refund_always_manage_fee |
| Always Credit Shipping Fee | Decide whether the shipping fee in a Qliro order should always be credited when a refund is made in Qliro. | qliro_refund_always_manage_shipping |
| Always keep Fee in Qliro Order | Decide whether a fee on the Qliro order should always be kept when the order is changed. | qliro_update_orders_always_keep_fee |
| Always keep Shipping fee in Qliro Order | Decide whether a shipping fee on the Qliro order should always be kept when the order is changed. | qliro_update_orders_always_keep_shipping |
| Api Key | Enter the API key for your Qliro account. | qliro_api_key |
| Api Secret | Enter the API secret for your Qliro account. | qliro_api_secret |
Show all 19 settings
| Setting | What it controls | Key |
|---|---|---|
| FEE article number in Fortnox | Enter the article number (SKU) used for the fee on orders in Fortnox. | qliro_erp_fee_sku |
| Identify Cancelled Orders by Status | Choose the Fortnox order status (or statuses) that means an order has been cancelled . | qliro_order_status_cancelled |
| Identify Qliro Orders by Payment Method | Choose the terms of payment (betalningsvillkor) on the Fortnox order that tells Junipeer the order was paid with Qliro. | qliro_qliro_payment_method_identifier |
| Identify Shipped Orders by Status | Choose the Fortnox order status (or statuses) that means an order has been delivered . | qliro_order_status_shipped |
| Order Items update Status | Choose the Fortnox order status (or statuses) during which changes to the order rows may still be updated in Qliro. | qliro_order_status_update_items |
| Qliro Order Reference | Choose which field on the Fortnox order holds the reference Junipeer uses to find the matching order in Qliro. | qliro_order_reference_attribute |
| Qliro Order Reference Manipulation | Clean up the order reference before Junipeer uses it to find the order in Qliro. | qliro_order_reference_manipulator |
| Qliro SKU Reference Manipulation | Clean up the SKU on each order row before Junipeer matches it with Qliro. | qliro_sku_reference_manipulator |
| Shipping article number in your ERP | Enter the article number (SKU) your ERP uses for shipping, so it can be matched to the shipping row in Qliro when crediting. | qliro_erp_shipping_sku |
| Test mode | Decide whether the connection to Qliro should run in test mode . | qliro_test_mode |
| Use merchant reference from CHECKOUT (instead of payment transaction) | Decide where the order reference on exported payout transactions comes from. | qliro_payout_use_checkout_merchant_reference |
Did this page help you?